Vincent @ Vincent @kbin.social

Posts

33

Comments

131

Joined

2 yr. ago

Tip: gebruik reader mode om het artikel te lezen.

I stuck with Toolbox for a long time because it was default, but then I wanted to be able to easily recreate my boxes with the same set of packages when e.g. they broke for some reason, or because the distro they were built on released a new major version. Distrobox supports that with its assemble command, so I switched. Otherwise it's not too different really, for a casual user like me, and if I hadn't needed assemble, Toolbox would've been just fine.

(Except that I keep forgetting whether Toolbox or Toolbx is the correct spelling now.)

Not OP, but for me, the main benefit is how uneventful major distro upgrades are. Yesterday I updated to Fedora 39, and it was so anticlimactic to reboot and then be like: is it over? But that was really all there was to it.

It’s Official: Cars Are the Worst Product Category We Have Ever Reviewed for Privacy — Mozilla

Haha exactly, by that calculation $1 a year would cover you and two others. Get that family onboard :)

Signal had 40 million active users in 2021. With 14 million in infra cost, that comes to .35 per user/year. Total expenses are about 33 million, so about .825 per user/year. All in all that seems very reasonable.

https://news.ycombinator.com/item?id=38291950

So it should be pretty easy to cover your own costs and maybe that of a couple of friends to make the transaction fees worth it :)

They were kinda forced to, having to choose between two evils: https://community.signalusers.org/t/signal-blog-removing-sms-support-from-signal-android-very-soon/47954/57

No I don't, though maybe if all my guests smoked I might? It's somewhat arbitrary anyway, you do some things to make their stay pleasant, and you don't do others if they're too much work for too little (of your guests') payoff.

You could make it a BMBH (Bring My Beer Home).

I don't drink coffee, but I still have it in case my guests want some. It's just nice.

Ik ben heel benieuwd hoe de auteur zelf zijn gedrag aan heeft gepast na het schrijven van dit stuk. Ik neem aan dat hij iets vergelijkbaars van ons allemaal verwacht?

I'm very excited about how the Linux community generally seems to be moving towards various approaches to immutable systems - all of them having in common that system updates are going to be a lot less likely to break. The future is looking good!

Ah yes, people are indeed known for always reading long readmes and fully grasping the consequences of their actions, especially if those occur long after said actions :P

Great work by Sonny and Tobias. Really happy to hear that more effort will be invested into accessibility, as I feel it's really been lagging over the past couple of years.

Yes, but as soon as it is accessible via the GUI, more and more people will start getting blurred Google Docs (and similar weird issues) without knowing how that happened - because that's already happening even with people who know enough to make changes in about:config.

I mean, you're just saying that if you don't dial it up to eleven, but just to nine, then you'll hit less breakage. Which, sure, but that's kinda my point: a usable browser needs to strike a balance, and that's exactly what Firefox is trying to do - which is really something different from "needing a 180-degree turn". Firefox by default is stopping way more tracking than e.g. Chrome, and guides users to installing e.g. uBO.

Also note that most breakage isn't immediately obvious. For example, if you turn on privacy.resistFingerprinting, then Google Docs will become blurred. However, by the time you see that, you won't be able to link that to the flipped config. This is the kind of breakage that many "hardening guides" cause, and by that, they eventually lead people to switch to Chrome, which is the opposite of what they're supposed to achieve.

And sure, Librewolf draws the line at a slightly different place than Firefox does. But the main difference is not sending data like hardware capabilities, crash stats, etc. to Mozilla - which don't threaten democracy or result in hyper-targeted ads, but do enable Mozilla to optimise the code for real-world use.

Wat goed nieuws mag ook wel eens :)

A Mozilla dependent on Google seeing value in Firefox sending searches their way is at minimum as good as one in which Mozilla doesn't exist and everybody uses Chromium-based browsers, by definition - and in practice, way better.

But yes, more non-Blink engines in use in general would also be a better world. Alas, that, too, isn't the world we live in.

Same for translations btw, Firefox didn't have built-in translations for a while because Mozilla had to painstakingly work on a research project to figure out how to do translation locally, on your machine, without sharing the page you're looking at with an external server.

Spell-check doesn't send things to a server in Firefox - that's Chrome (and only with a particular setting, IIRC).