

It will make for a very uncomfortable to read PDF.


It will make for a very uncomfortable to read PDF.


And then all this effort was ruled illegal and the collection never saw the light of day. Thanks, copyright mafia.


I think you’re severely underestimating the effort of digitizing it. Usually the way that’s done is to break or saw off the spine and scan every page individually using a scanner, which is obviously a destructive process. Unless it’s an exceedingly rare book it probably is not worth the effort.
Matrix.org is really slow, but I’m on a smaller home server and things are generally fast enough. While it doesn’t make your point any less true (there are still times things are far too slow), you might want to try finding a smaller home server if you currently use matrix.org.


It’s a little strange how these numbers are relatively far off from what the Steam Hardware Survey suggests. On there, Linux is 3.2% of the userbase and Bazzite is 5.5% of that, so Bazzite is about 0.176% of the total userbase. Steam has about 70 million daily active users, so Bazzite’s share of that would be about 120 000.


Inspired by this post I spent a couple of hours today trying to set this up on my toy server, only to immediately run into what seems to be a bug where <video> tags loading a simple WebM video from right next to index.html broke because the media response got Anubis’s HTML bot check instead of media.
I suppose my use-case was just too complicated.


Abandoning streaming services only to become a serf of another commercial subscription service seems like such a bizarre move that I really don’t understand how Plex users even exist.


Why would you bother going through all that trouble if there is a way to software cheat undetectably? This is a rhetorical question.
Yeah. “Feature parity or get out”, like dude we’re long past feature parity.
Wayland supports so much more stuff than X11 does, and what does X11 have that Wayland doesn’t? X forwarding? Just use a modern remote desktop solution, all X forwarding was doing in “modern” times (read: the 21st century) was streaming pixels anyway, just less efficiently than modern remote desktop.
Thank you Mr ChatGPT

Fairphone also lets you change out the battery very easily, so it’s not that big of a deal if it degrades. You might save the world 20% of a battery’s worth of e-waste by micromanaging your charging, which won’t really make a difference.


Even if it’s 8 physical qubits to 1 logical qubit, 6100 qubits would get you 762 logical cubits.
All I’m saying is that the technology seems to be on a trajectory of the number of qubits improving by an order of magnitude every few years, and as such it’s plausible that in another 5-10 years it could have the necessary thousands of logical qubits to start doing useful computations. Mere 5 years ago the most physical qubits in a quantum computer was still measured in the tens rather than the hundreds, and 10 years ago I’m pretty sure they hadn’t even broken ten.


We can only hope that Bitcoin gets pwned by quantum computers. It would be absolutely glorious.


There was a paper recently about a stable 6100-qubit system, so the trajectory is plausible. If 1399 qubits is needed for 2048-bit Shor’s, this would already meet that by a wide margin – though obviously this is a research system that AFAIK cannot do actual computations.
The reason people say that Arch is unstable is that you are expected to read the news on the website before every update or else your system is liable to be broken – and sometimes it will break in spite of that. Oh, and the expectation is that you’ll be updating multiple times per week, and if you don’t, you will soon be in a situation where to install any package you must update your entire system.
Most other distros place no such expectations on the user.


That subtitle isn’t real
My understanding is that it is fixable by just implementing a couple of APIs, but Artix barely has the resources to fix their own init system, so they aren’t able to support such compatibility.
No you haven’t. The security is the Jellyfin login prompt, then Jellyfin itself, then the Jellyfin container, and if you’re really paranoid, that container won’t be in your LAN.
If you’re not intending to use complicated RAID setups, just go with btrfs. There is no reason to bother with zfs given your specs and needs.
Do not go with ext4. Unlike both btrfs and zfs, ext4 does not do data checksumming, meaning it cannot detect bit rot (and obviously cannot fix it either). You’ll also be missing out on other modern features, like compression and copy-on-write and all the benefits that entails. Once you start using snapshots for incremental backups using btrfs send (or its zfs equivalent), you’ll never want to go back. Recommended script: snap-sync.
I can’t help but wonder, shouldn’t this all be possible on Linux without needing to install a hacked hypervisor? At most you would need a kernel patch, but since Denuvo operates through Wine, maybe an entirely userland solution would be possible too.