ALright, thanks for the recommendation :) And yeah, “weird” and “metal” are good descriptions. Additionally, the backstory we got in S1 was definitely “fire”.

I liked the first 80% of the first season, and stopped watching halfway into S02E01. Is it worth continuing? Do we get any answers? Are they satisfying?

Alright, thanks for the info, that’s good to know. Trying to make the jump becomes more enticing every day.

Thanks for sharing! Sounds about as good/bad as I was expecting. How’s the browser experience? Also, are there any features/tweaks you are aware of that you could not get through Nix, that the more “commercial” Linux device manufacturers have developed for their devices?

Holy crap! A NixOS-on-phone user in the wild! You are rocking my dream setup. How’s your experience been with it? Is it remotely daily drivable for phone things?

What does this have to do with Privacy?

Some might say interconnecting everything could be a legitimate goal. Nonetheless, some people started to report about huge amounts of data and metadata being sent to Matrix central servers.

Curious that this claim is without source in the original.

I also have porblems with their claims about bridges. Bridges are Band-Aids to allow you to communicate with people not on Matrix, not a dark masterplan to build a central spionage hub.

By default, a homeserver trusts matrix.org in questions of federation and identity of other servers. You have to get that trust from somewhere. You are free to choose another source for that.

(For example, my homeserver isn’t federated at all, and has that trusted server removed; it doesn’t communicate with anyone. Also it’s not synapse, but that’s besides the point.)

That’s great.

Please beware that DNS over TLS is transport protection; the dns server itself of course still sees and knows everything.

How exactly does Free, non-open-source software prevent that?

Fühl ich, Bruder.

Baby steps: I wish it was mandated that any software receiving even a penny in public funding must be open source down to the last byte.

You are probably half-joking, but… yeah.

I fucking hate this timeline. Actually, scratch that, that is way to placid and abstract.

I hate the assholes in charge. Fuck all of them. Luigi did nothing wrong.

My blood glucose monitor is not on the play store. So one dy next year I’ll wake up and no longer be able to get that data…?

… are entirely possible, even if rarely the right choice.

Or a CLI with clap.

Curious what you are talking about. Multi-threaded sharing of memory for example is also easy with rust, it just doesn’t let you wrote and read at the same time, and so on.

Yeah. Once you get used to the (verbose, but by no means unergonomic!) syntax, you’ll probably never be happy with another language again. Job-wise, I am currently mostly using Go, and while also a nice language, I miss the confidence and security I took for granted with rust.

Not to mention just how goddamn expressive rust can be. Let bindings like if ok/err, else return? Assign from a match on Some(Ok(x))? Filter, map, and friends on any iterator? Oh my GOD the error handling with the question mark iterator? 100% confidence that if it compiles, no error, possible null value, or case is unhandled.

And all this WHILE giving you the amazing security benefits!

Ah, damn, caught me proselytizing again.

• if your skill is so great that you would never cause the kinds of bugs the rust compiler is designed to prevent, then it will never keep you from compiling, and therefore your complaint is unnecessary and you can happily use rust
• if you do encounter these error messages, then you are apparently not skilled enough to not use rust, and should use rust

In summary: use rust.

Think about it like this:

• with ansible, you are responsible for making sure that executing the described steps in the described order leads to the desired result

• with nix, you describe what you want your system to look like, and then figuring out how to get there is nix’s problem (or rather, is obvious to nix thanks to nixpkgs)