Just go through F-Droid or Flathub and look at the long list of apps that haven’t been updated in years.

“not updated in years” didn’t used to be considered a bad thing. Why is it one now?

If something works well for me as it is and runs locally in a way that doesn’t open itself up to remote exploits, I don’t necessarily need it to keep changing all the time. Even if it would be nice if it had more features, the software works fine for me as it is. I don’t need those updates now or this year.

The only true “need” is that it doesn’t stop working for me when the various platforms or compilers change. I used to use a Python2 program, and I could keep using it for about a decade after its last update, but eventually I did need to move past it because Python3 had long since replaced it and distros stopped shipping Python2. A year or two of no updates it’s nothing.

If the only problem is that you can’t use dynamic linking (or otherwise make relinking possible), you still can legally use LGPL libraries. As long as you license the project using that library as GPL or LGPL as well.

However, those platforms tend to be a problem for GPL in other ways. GPL has long been known to conflict with Apple’s App Store and similar services, for example, because the GPL forbids imposing extra limits that restrict user freedom and those stores have a terms of service that does exactly that.

Of all possible names, they’re really using “Core 2 Duo”? I feel like anyone who has been following tech long enough would immediately think of the Intel processor when hearing that name.

If it was a community addition why would it matter? And why would they remove the codecs.

You don’t have to be a corporation to be held liable for legal issues with hosting codecs. Just need to be big enough for lawyers to see you as an attractive target and in a country where codec patent issues apply. There’s a very good reason why the servers for deb-multimedia (Debian’s multimedia repo), RPM Fusion (Fedora’s multimedia repo), VLC’s site, and others are all hosted in France and do not offer US-based mirrors. France is a safe haven for foss media codecs because its law does not consider software patentable, unlike the US and even most other EU nations.

Fedora’s main repos are hosted in the US. Even if they weren’t, the ability for any normal user around the world to host and use mirrors is a very important part of an open community-friendly distro, and the existence of patented codecs in that repo would open any mirrors up to liability. Debian has the same exact issue, and both distros settled on the same solution: point users to a separate repo that is hosted in France which contains extra packages for patent-encumbered codecs.

I stopped using Arch a long time ago for this same reason. Either Fedora (or derivatives like Nobara) or an atomic/immutable distro (like Bazzite, Silverblue, Kinoite) is probably the way to go.

I used to feel like Ubuntu was a good option for this, but it no longer is: too often they try to push undesirable changes that need manual tweaking to fix after release upgrades. Debian Stable is generally good for low-maintenance use but doesn’t keep up as well with newer hardware or newer updates to video drivers and mesa, which makes it suboptimal for typical gaming use. Debian Testing can be prone to break things in updates (in my experience, worse than Arch does).

I saw another comment recommend Rocky/RHEL, but note that their kernel doesn’t support btrfs. Since you mentioned a root snapshot, I expect you probably use it.

I was only talking about high core count and high (relatively speaking) single-core performance. The DeepComputing Framework board is neither. Its JH7110 is only 4 cores and a rather old processor, which seems like an odd choice for a product releasing in 2025. At least the software support is great since distros have been working with VisionFive 2 and Milk-V Mars for years.

It’s also the only currently-available Framework 13 board with fewer than 6 cores, though core count isn’t remotely comparable between architectures. At this price ($209 for lone board with 8GB RAM, $799 for full laptop) I’d prefer to see something at the very least comparable to SpacemiT K1, which has 8 cores and vector support, and is on the Banana Pi BPI-F3 (8GB version is $95).

I’m only aware of one RISC-V system where I can say the core count is there: the Milk-V Pioneer board and its 64-core SG2042 processor from two years ago. It’s comparable in price to a 64-core ARM Ampere CPU+motherboard (USD$1500 for the board), which seems somewhat reasonable when not considering the performance of each core. Hopefully the C930 core described in this article leads to more systems that aim for multi-core performance.

Most RISC-V development boards are only 4 cores or fewer, with just a few popping up in the last year with 8 cores and nothing higher besides the SG2042. The best single-core RISC-V performance so far is on the SiFive P550 but it’s only 4 cores and comes on a development board that costs USD$500 (plus another $150 for tariffs if shipping to the US). You could easily get a 12-core AMD CPU and motherboard combo for less than that.

Jerboa has the same lead developers and is part of the same GitHub organization as the Lemmy server and web UI.

The logo for Lemmy itself is the head of a rodent, supposedly a lemming. Most instances use that logo or a variation of it in their web UI. Jerboa and other apps in turn tend to use a rodent in the logo.

If you have a rooted Android device or a jailbroken Kindle device, yes, you can still use Calibre DeDRM and KFX Input plugins on the kindle ebooks downloaded on them. It just takes a bit more setup with getting the key you need.

Unfortunately, DMCA takes an extreme stance when it comes to anti-circumvention. Even personal backup doesn’t have a strong legitimacy case under it, especially not when it comes to the tools that enable it.

Very related to this, LockpickRCM is a tool whose entire purpose is to extract your own Switch keys for the titles you own, and in turn is far more useful for people who want personal backups than those who are pirating the games. Still got a DMCA takedown two years ago, and though it never went to court it’s extremely unlikely any court would have ruled in their favor if it did.

For what it’s worth, the “Download & transfer via USB” feature was applying DRM locked to the key of the specific Kindle device you select, giving you a file that’s incompatible with other devices even if they’re kindles linked to the same Amazon account. For many publishers it also gives files with drastically lower image quality than the Kindle app: about one-fourth to one-third the file size. For a couple examples, a 368MB KFX manga volume has a 125MB AZW3 file and an 8.0MB KFX light novel has a 2.2MB AZW3 file. Those smaller AZW3 files are also similar in size to DRMed EPUB files of the same books from other markets like Kobo and Google Play, so I expect it’s a deliberate choice to limit the quality of formats that are more trivial to strip DRM from.

The best way I’ve found to make personal backups of owned Kindle content is to use a rooted Android device to download everything through the Kindle app, copy the KFX files to a computer, extract the key in a root shell, and then use DeDRM tools on those files with that key.

A quick and dirty shell command I’ve used for that purpose is egrep -ao 'dsn[0-9a-f]{32}' /data/data/com.amazon.kindle/databases/map_data_storage.db. The key is 32 hex characters.

Having a rooted Android device in the first place is the biggest hurdle for being able to do that. This new jailbreak should make it possible to do something similar with e-ink kindles instead.

Don’t assume Qualcomm’s general hostility to user control and freedom is representative of all non-x86 systems.

This system isn’t like that at all. It’s usable with mainline Linux and mainline U-Boot and has no proprietary driver blobs. Granted, RISC-V has some more progress to make in terms of boot image standardization, and this board in particular uses an old SoC from three years ago (JH7110) which predates a lot of improvements that have been happening to various intercompatibility-focused RISC-V standards.

For some of the most recent ARM systems (notably excluding Qualcomm junk), I can write a single installation image for a Linux distro of my choice to a USB drive and then boot that single USB drive through UEFI on several completely different systems by completely different vendors. Ampere, Nvidia, and more. ARM’s SystemReady spec results in exactly the same user-friendly process you’re used to on x86.

The RISC-V ecosystem isn’t there yet though its very recent RISC-V BRS (Boot and Runtime Services) spec promises to bring that for near-future hardware. But this DeepComputing board doesn’t have that and doesn’t have some other features (vector instructions, RVA22/23, etc) that are very likely to become the minimum requirements for several RISC-V Linux distros in the not too distant future.

I think the messaging is clear this time: Steam Deck is the defacto and flagship SteamOS device that represents the platform, and it has a strong established mindshare already, while other options are now available as well. It had a headstart of three years that gave it plenty of time to shine, and the handheld form-factor still stands out as something the competition (Windows) treats as an afterthought at best with poor UX.

The Steam Machines effort tried to position Alienware Alpha as its focus but the press coverage including all of the other options at the same time confused people. Steam Machines also had awful timing and pricing, with the Alienware being outdated hardware whose Windows version had already been out for a year for the same price or lower by the time the SteamOS version released, and the SteamOS version offering absolutely no advantage in pricing, power, features, or UX for most gamers. All of those factors are different this time. Plus game compatibility was much worse than it is now.

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.

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.

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.

For years I’ve been using KeepassXC on desktop and Keepass2Android on mobile. Rather than sync the kdbx file between my devices, I have each device access it through the network. Either via sftp, smb, or nfs, but regardless I need to connect to my home’s VPN to access it when away from home since I don’t directly expose those things to the outside world.

I used to also keep a second copy of the website-tied passwords in Firefox Sync, but recently tried migrating that to Proton Pass because I thought the PIN feature might help, then ultimately decided to move away from that too and start using the KeepassXC-Browser plugin instead. I considered Bitwarden too but haven’t tried it out yet, was somewhat deterred by seeing people say its UI seems very outdated.