Rack width includes the rails/ears. That’s where the extra inch you’re referring to comes from. The actual size of equipment you can slide between the rails and inside the rack, not including ears, is about 17.75" for 19" racks and about 8.75" for 10" racks. That is indeed half the width. Or at least within 0.125", but I don’t know how accurate these numbers really are.

MicroATX very much cannot fit in this 10" rack.

Equipment that is “half-rack” or “half-width rackmount” tends to be primarily intended to mount two devices side by side on the same row of a 19" rack, but also can often be mounted in a 10" rack by attaching ears to both sides.

This form factor isn’t actually new. This article is just about someone consolidating resources related to its current market options into simple documentation.

One major perk to this size is that it’s small enough that the vast majority of 3D printers can make plastic mounting brackets for it, making it a lot easier for people (who happen to have access to a 3D printer) to use small low-power gear that isn’t designed for rack mount.

So it’s most popular for people who want to run a few Pi systems, similar small SBCs, or mini PCs similar in size to a Mac Mini, or who want to throw network gear they already own that isn’t designed for racking into a rack. Even ITX systems don’t really seem like a great fit for this in my opinion, though it’s at least possible to fit them.

Although swapfiles shouldn’t be in snapshots (or otherwise Copy-On-Write), that doesn’t mean you can’t have them in btrfs. You can create a non-COW file in a separate btrfs subvolume that you don’t enable automatic snapshots for and use that for swap. btrfs-progs even has a btrfs filesystem mkswapfile convenience command for allocating a NOCOW file suitable for swap use, though you still need to make sure to put it in a subvolume that you don’t make snapshots for.

You probably don’t want to put swap in an unencrypted partition if you’re encrypting your root filesystem. Swap is liable to write sensitive data to disk, especially if you use hibernate.

some games that looked old (like Animal Crossing)

There’s a good reason for that one: the first animal crossing game was originally made for Nintendo 64, though that version was only released in Japan. GameCube got a port of it and that port (plus some extra features) is what released in English.

The detail that stands out the most about this is its screen resolution: 720x480 is both a perfect 3x integer scale of GBA’s 240x160 and a good 1x fit (with small black bars) for NTSC video.

GBA games scale particularly poorly on most of their other devices’ screens. On 640x480, the closest integer scale is 2x which makes the image fill only 50% of the screen area, otherwise you can use 2.667x scaling to fill the width (11% of height being letterboxing) at the expense of blurriness from non-integer scaling.

The last time Anbernic released a screen well-suited for GBA games was four years ago with RG351P/RG351M. Their 480x320 screens are a great 2x fit for GBA but an awful fit for every other system. 720x480 is a lot better for NTSC content while still being integer scale for GBA.

Unfortunately the lack of analog sticks ruins the compatibility improvements it’d otherwise have over RG351 thanks to the screen and newer CPU. Best to see this as like a GBA that can also play SNES games and not much else. I’d rather have a system that includes the inputs it needs than one that imitates a classic system’s design.

Most of the “Is open source software safe?” section of this post seems to advocate for what’s conventionally called Security Through Obscurity, which is widely considered very ineffective at preventing exploitation and at best a minor hurdle.

There are a lot of differences between Android and iOS in terms of security, attack surface, and exploitation, but attributing that to open vs closed-source completely misunderstands the entire subject. For just two of the countless reasons: Many of the worst vulnerabilities that affect Android devices are in closed-source proprietary Qualcomm firmware. A platform being open in the sense of allowing users to install any application they want to (like Windows and Android to a limited extent) or closed off to prevent installation of unapproved software (iOS, PlayStation, Toyota cars, TiVo, etc.) is completely separate from whether that platform is open-source or not. GPLv3 has license terms that try to tie the two concepts but I chose examples that don’t use it at all. Also, iOS has public kernel source code.

Although by a different organization in a different continent, enshittification was also selected as word of the year for 2023 by the American Dialect Society.

There should have been a simple way to label them for usage that was baked into the standard.

There is. USB IF provides an assortment of logos and guidelines for ports and cables to clearly mark data speed (like “10Gbps”), power output (like “100W” or “5A”), whether the port is used for charging (battery icon), etc. But most manufacturers choose not to actually use them for ports.

Cables I’ve seen usually are a bit better about labeling. I have some from Anker and ugreen that say "SS”, “10Gbps”, or “100W”. If they don’t label the power it’s probably 3A and if they don’t label the data speed it’s usually USB 2.0, though I have seen a couple cables that support 3.0 and don’t label it.

I’ve been using single-disk btrfs for my rootfs on every system for almost a decade. Great for snapshots while still being an in-tree driver. I also like being able to use subvolumes to treat / and /home (maybe others) similar to separate filesystems without actually being different partitions.

I had used it for my NAS array too, with btrfs raid1 (on top of luks), but migrated that over to ZFS a couple years ago because I wanted to get more usable storage space for the same money. btrfs raid5 is widely reported to be flawed and seemed to be in purgatory of never being fixed, so I moved to raidz1 instead.

One thing I miss is heterogenous arrays: with btrfs I can gradually upgrade my storage one disk at a time (without rewriting the filesystem) and it uses all of my space. For example, two 12TB drives, two 8TB drives, and one 4TB drive adds up to 44TB and raid1 cuts that in half to 22TB effective space. ZFS doesn’t do that. Before I could migrate to ZFS I had to commit to buying a bunch of new drives (5x12TB not counting the backup array) so that every drive is the same size and I felt confident it would be enough space to last me a long time since growing it after the fact is a burden.

deleted by creator

This argument is even more ridiculous than it seems. During the copyright office hearing for this exemption request (back in April), the people arguing in favor of libraries talked about the measures they have in place. They don’t just let people download a ROM to use in any emulator they please. It’s not even one of those browser-based emulators where you can pull the ROM data out of your browser cache if you know how. It’s a video stream of an emulator running on a server managed by the library, with plenty enough latency to make it very clearly a worse gaming experience.

It’s far easier to find ROMs of these games elsewhere than it is to contact a librarian and ask for access to a protected collection, so there’d be no reason to redistribute the files even if they were offered, which they aren’t.

On top of that, this exemption request was explicitly limited to old games that have been long unavailable on the market in any form, which seems like an insane limitation to put on libraries, places that have always held collections of books both new and old.

All of that is still not enough to sate the US Copyright Office, the ESA, AACS, or DVD CSS. Those three were the organizations that fought against this.

Newer than C99? Both the Linux kernel and systemd build with gnu11. I’d call those pretty relevant.

C23 is still far too new (still a draft) for any major projects that care about compiler compatibility.

The Y axis here is not an absolute international political compass. It measures which political party each person favors, and judging by that country’s local standards categorizes that party as either left or right.

A rising number in the US chart means a larger number of people prefer democrats over republicans. It doesn’t mean that people’s stances are necessarily moving further left. Similarly, it’s no coincidence that the inflection point where UK numbers rise by a lot correspond to Brexit: the party seen as responsible for the unpopular change lost a lot of support, but that doesn’t mean the population has so sharply moved drastically more progressive in such a short time.

Anbernic devices in particular are known to ship with an SD card that’s preloaded with a fairly large game library. I own a RG351M which did indeed include a cheap card loaded with both the OS and a collection of games by Nintendo, Sega, and many others, plus some strange rom hacks. I immediately swapped that card out for a better one with a better CFW and my own files.

Most other notable names in the emulation handhelds space like Retroid, Ayn, and Ayaneo expect users to be able to provide their own files instead, which I’d say makes more sense.

My best guess: whatever they’re filing now was so exhaustively researched that it took months to prepare the strongest case they’re able to make, possibly delayed by the lawyers working on several other cases. Plus waiting until sales have dried up can maximize damages.

Another possibility is that Nintendo/TPC is planning to make some big Pokémon announcements soon and wants to target this shortly before their own new games to reduce competition. Palworld might seem like more of a threat to the execs now that Pokémon is nearing a major release than it was in the middle of a long drought for the series.

USB-C video is usually DisplayPort Alt Mode, which uses a completely different data rate and protocol from USB.

Even using old 2016 hardware, a computer and USB-C cable that both only support 5 Gbps USB (such as USB 3.1 Gen 1) can often easily transmit an uncompressed 4K 60Hz video stream over that cable, using about 15.7Gbps of DisplayPort 1.2 bandwidth. Could go far higher than that with DP 2.0.

Some less common video-over-USB devices/docks use DisplayLink instead, which is indeed contained within USB packets and bound by the USB data rate, but it uses lossy compression so those uncompressed numbers aren’t directly comparable.

For that portable monitor, you should just need a cable with USB-C plugs on both ends which supports USB 3.0+ (could be branded as SuperSpeed, 5Gbps, etc). Nothing more complicated than that.

The baseline for a cable with USB-C on both ends should be PD up to 60W (3A) and data transfers at USB 2.0 (480Mbps) speeds.

Most cables stick with that baseline because it’s enough to charge phones and most people won’t use USB-C cables for anything else. Omitting the extra capabilities lets cables be not only cheaper but also longer and thinner.

DisplayPort support uses the same extra data pins that are needed for USB 3.0 data transfers, so in terms of cable support they should be equivalent. There also exist higher-power cables rated for 100W or 240W but there’s no way a portable monitor would need that.

A related issue I still see very often, even with files newly created just this year, is when trying to extract zip files on my Linux systems that contain non-ASCII filenames and that were created on Windows systems, especially ones with apparently non-English locales like Japanese. Need to trial and error the locale I give to unzip and sometimes hack together fixed names with iconv until the mojibake seems to fix itself.

The whole point of copyright in the first place, is to encourage creative expression, so we can have human culture and shit.

I feel like that purpose has already been undermined by various changes to copyright law since its inception, such as DMCA and lengthening copyright term from 14 years to 95. Freedom to remix existing works is an important part of creative expression which current law stifles for any original work that releases in one person’s lifespan. (Even Disney knew this: the animated Pinocchio movie wouldn’t exist if copyright could last more than 56 years then)

Either way, giving bots the ‘right’ to remix things that were just made less than a year ago while depriving humans the right to release anything too similar to a 94 year old work seems ridiculous on both ends.

a variable-length integer encoding that somewhat resembles what they do in UTF-8. It means for strings < 128 chrs, the length is a single byte. Longer than that and more bytes get used as necessary.

What you used might be similar to unsigned LEB128, which is used in DWARF, Webassembly, Android’s DEX format, and protobuf. Essentially encodes 7 bits of the number in each byte, with the high bit being 1 in any byte except the last one representing the number.

Though unlike UTF-8 the number’s length isn’t encoded in the first byte but instead implied by the final byte. Arguably making the number’s encoding similar to a terminated string.