nyanpasu64

The eggshell looks like a century egg, but as mentioned by the comment the contents may have decomposed if the mud wasn't alkaline like the century egg production process.

Frankly I'm scared by governments and corporations going "papers, please" for people to be allowed to access the Internet. On top of endangering privacy by tying pseudonymous online interactions to real-life ID and biometrics, attempts to block under-18 people from finding information or interacting online will only amplify how society regards them as not having rights. This will isolate people (especially gay and trans teens) living with abusive parents from finding support networks, and prevent them from learning (by talking to friends in different situations) that being beaten or emotionally put down by parents is abusive and traumatizing.

I know all too well that when you grow up you're psychologically wired to assume that the way the parents treated you is normal, and if they harmed you then you deserve to be hurt. I've made friends with and assisted many teens and young adults in unsafe living situations (and talked to people who grew up in fundamentalist religions and cults), and they're dependent on online support networks to recognize and cope with abuse, get advice, and seek help in dangerous situations.

Nitpick: ATSC 1.0 only offers broadcast in 720p or 1080i... of course with overscan and all, nobody actually notices the resolution of TV.

I noticed the article uses the Polyvers font (complete with bold capitals in the headings), which I haven't seen on the Internet. Wonder what that is.

EDIT: It seems to coexist with U001, which is "An Univers-like typeface that comes with GhostPDL made by URW++."

> Hyraxes have highly charged myoglobin, which has been inferred to reflect an aquatic ancestry.[20]

Sea grass is a monocot but belongs to a different order (Alismatales) than true grass (Poales).

What's the chemical exposure from laptop repair? The biggest thing that comes to mind is flux smoke, which needs a fan or ideally a fume extractor to keep out of your face. Modern devices use lead-free solder, though I understand solder is mostly a concern for scrapping electronics for gold rather than repairing it (unless you don't wash your hands after soldering). I've gotten nasty effects from isopropyl/acetone vapors and super glue/epoxy too.

EDIT: Are they salvaging components from e-waste, or diving in dumpsters with non-computer waste as well?

I suppose it does make sense that a "make curl look like a browser" program would get sponsored by "bypass bot detection" services...

The photos show soldering to Li-ion battery terminals. Doesn't that cause internal heat damage as opposed to spot welding?

One time I tried drying a water-soaked smartphone in alcohol, but the alcohol got under the LCD screen and made it look blotchy permanently. The phone still worked but I stopped using it.

Meanwhile the Xbox 360 kamikaze hack actually involved drilling a chip...

Is it worth implementing sub-cubic matrix multiplication algorithms like Strassen etc. for 4096x4096?

I think foot zoom is the primary reason for faces looking weird (big noses) in smartphone selfies, while "a photograph occupying less of your FOV than the camera was capturing" is why people at the edge of a photo look distorted.

My theory is that most perceived perspective errors arise when a photograph captured with a wide field of view is shown in a narrower one; a perspective-"distorted" image looks more realistic if you put your nose up to the screen so the photograph fills more of your field of view (enlarging the center and eventually squashing the edges). And tricks like Panini projection and Piranesi's arches are ways of making features at the edge of the screen "take up" the correct amount of viewing angle (without bending straight lines) when the painting takes up less of your vision than the original scene.

If you get clever with things you can define actions with a single "apply_swap()" method which applies an edit and saves the old state (on the first call and subsequent odd calls), and reverts the edit and saves the new state (on the second call and subsequent even calls). This avoids having to write separate implementations for adding/removing items and redo/undo, and allows applying edits on a real-time thread with zero memory allocations (after constructing an edit action).

When I read contribution graph I assumed it would be a revision history graph of commits and authors.

This works if you know what each callee performs, which you frequently don't when you're visiting a new codebase (it may have an unknown function you have to read to know, functionality not relevant to your problem, or you may have to analyze two or more functions in the context of each other to understand a bug).

> In addition, before the integration into Chromium, we ran a wide set of pixel comparisons in Skia, comparing FreeType rendering to Skrifa and Skia rendering to ensure the pixel differences are absolutely minimal, in all required rendering modes (across different antialiasing and hinting modes).

I'm hoping (but not sure) Skrifa will support hinting (though I'm not sure how it interacts with fontconfig). I noticed your screenshot uses full hinting (a subjective choice I currently don't use on my machines), presumably with integer glyph positioning/advance which isn't scale-independent (neither is Windows GDI), though this is quite a nonstandard configuration IMO.

As I understand this issue affected Homebrew and CocoaPods: https://github.com/CocoaPods/CocoaPods/issues/4989#issuecomm...

> Apparently, most of the initial clones are shallow, meaning that not the whole history is fetched, but just the top commit. But then subsequent fetches don't use the --depth=1 option. Ironically, this practice can be much more expensive than full fetches/clones, especially over the long term. It is usually preferable to pay the price of a full clone once, then incrementally fetch into the repository, because then Git is better able to negotiate the minimum set of changes that have to be transferred to bring the clone up to date.

There's Piped but that keeps running into "IOS player response is not valid" error. (I don't know if my Invidious instance works either, I shut it down because of errors.)

If you require end users (and possibly libraries? IDK) to manually specify every transitive dependency of a dependency (but not hard-code/vendor it), this should act as a forcing function to reduce transitive dependency explosion in libraries (because it would degrade user experience). I'm not sure if users should have to update every dependency by hand (this discourages updates which can cause security bugs to persist, but automatic updates makes supply-chain attacks easier; AUR helpers generally diff PKGBUILDs before committing them, which partly protects against PKGBUILD but not source attacks, and even distros did not protect against the xz attack).

Another factor is that updating C++ compilers/stdlib tends to break older libraries; I'm not sure if this is any less the case in Rust (unclear? I mostly get trouble with C dependencies) or Python (old Numpy does not supply wheels for newer Python, and ruamel.yaml has some errors on newer Python: https://sourceforge.net/p/ruamel-yaml/tickets/476/).

Is the mitigation something that has to be installed on every system boot and only protects against microcode exploits later on that boot?

I'd recommend following the steps at https://invent.kde.org/plasma/powerdevil/-/blob/master/READM... to disable brightness control. You can switch to X11 too, but for some reason I get screen tearing and blocky incomplete updates I haven't looked for a workaround yet.

  systemctl --user edit plasma-powerdevil.service
  [Service]
  Environment="POWERDEVIL_NO_DDCUTIL=1"

EDIT: I tried switching to Wayland on Arc and am getting stuttery mouse cursor movement at around 36 FPS. I wonder what's wrong...

In my experience the KDE desktop lets you set monitor brightness from the UI... and on Wayland it happens even if you don't ask it to (https://bugs.kde.org/show_bug.cgi?id=494497). You can turn it off by "setting the `POWERDEVIL_NO_DDCUTIL=1` environment variable in PowerDevil as described in its README file: https://invent.kde.org/plasma/powerdevil/-/blob/master/READM..."

VGA/DVI/HDMI ports have an I2C interface (though DP tunnels I2C over AUX), which is normally used to read EDID information from monitors and control brightness, but on Linux (not Windows) you can control it as a general-purpose I2C bus, dump and even rewrite EEPROMs placed on the monitor bus. In theory you could even hook up a Nunchuk or Classic Controller to a display output (with level shifters if you want to run the Nunchuk at 5V off a 3.3V bus), and write a Linux driver to communicate with the peripheral and expose it as a game controller.

How do you know a program is free of data races?

I would try both nvidia-suspend enabled and disabled; https://forums.developer.nvidia.com/t/fixed-suspend-resume-i... suggests turning it off, but I'd try with it both on and off.

Yiikes, on my B550M DS3H, previously when I woke my PC from sleep immediately after it slept (eg. by pressing the keyboard or case power button), it would "wake" after 0.5 seconds asleep and turn on the power light but not respond to user input, and not even shut down if I held the power button for 4 seconds! I had to pull power at the wall. This behavior occurred on both Windows and Linux, and was fixed at some point in a BIOS update.

All the non-scalped B580s were out of stock by the time I decided to buy a GPU :( Thanks for the moral support!

As I understand, KWin does call glGetGraphicsResetStatusARB(), and on Nvidia GPUs, sleep-wake (or opening apps if it crashed the GPU) would cause KDE to detect a graphics reset and print "Desktop effects were restarted due to a graphics reset" (https://github.com/KDE/kwin/blob/10c04995c1f9f82ddbd6610e5e0...). I haven't used Nvidia GPUs in years and don't know if this is still an issue. I think many apps don't check for graphics resets?

I'm not sure if residency is relevant here; the Microsoft link indicates that eviction makes memory inaccessible from the GPU to make room for other memory, which explains why Linux uses the same name for "backing up" VRAM before sleep (through the same underlying mechanism).