ace

I dunno, that looks exactly like something you'd expect to see an Analyst/Therapist - an analrapist if you will - use.

Gotten myself both a large-screen Kobo Elipsa 2E, which does wonders with KOReader. Haven't used the pen much though, since that's not what I got the device for.

Also got myself an Xteink X4 and loaded it with the crosspoint firmware, which does amazingly for some casual reading on the go.

Been using Yggdrasil for quite a while at this point, both for encrypted service communication and also as unbreakable VPN links to various places where I don't want to have to mess about with NAT traversal.

It's been nice to be able to just drop it onto my router, add an ALFIS DNS entry, and have all my devices just work with Yggdrasil with no additional configuration.

I tend to go for House, DnB, or Electro Swing when coding. Something upbeat and with a steady rhythm.

No, the Rust standard library only contains functions useful for standard Rust, not POSIX/Linux user-space -specific functionality from libc.

Because it's a rust implementation of coreutils, and not a rust implementation of coreutils and libc?

Well, Valve did a randomization of the order queue. So your account value really shouldn't matter

I'm holding off on Fluxer until they decide how they're going to implement federation, since the designs they've communicated publicly so far have all seemed like they prioritize siloing and putting excessive load on self-hosted nodes.
Their first proposed solution would've required each self-hosted server to be able to handle every user on every other server in the network - a proposal which they've since scrubbed from their page.
The latest proposal I can find at least speaks about aggregating connections through the users server, so it's not as insane (Only requiring each self-hosted server to be able to handle requests from every other server on the network). But it still forbids intelligent caching, and instead seems to consider recommending the use of cloudflare to reduce the load from their design to be a good solution.

I made an NFC/QR code card for my wifi details at home, and that also includes the details written in clear text on the card, since some devices simply don't do QR (or NFC in my case).

Someone pulled some DRAM cost graphs, and with the >500% increase that's happened, the Deck did have to rise at least $200 to remain viable.

We really can't have nice things, first crypto and now AI insanity is really doing its best to remove computing as an affordable hobby.

It doesn't really solve my use-case, since we do a combination of direct stream when possible, as well as local sync/cache but only for transcoding purposes. As well as local users only, with the federated sharing taking care of permissions, so that we don't transfer user information between eachother.

Jellyswarrm is certainly a lot closer than other solutions people have suggested though.