This needs to be locally hostable and auditable to be interesting.
2,504 karma · joined December 20, 2023
This needs to be locally hostable and auditable to be interesting.
Aside: This reminds me that pro-CCP astroturfing has been increasingly prevalent and visible on the fediverse recently...
https://sizeof.cat/post/web-browser-telemetry-2025-edition/
As for webapps breaking in Librewolf, IME those can be fixed by selectively unblocking canvas (or whatever) for the site in question.
The supposed local-only features like translations will download at least model updates and configuration, which leaks metadata.
Waterfox, Librewolf and Mullvad Browser are worth considering.
People would be better served by not expecting anything different from Microsoft. As you say yourself, this is how they roll.
> The only learning to take away is never ever use anything from the big tech companies
Do you even believe in this yourself? Not being dependent on them would be a good start.
Exactly. Would be nicer if they did their own features somewhat right (including interfaces for configuration and disabling approachable for non-engineers) before they scope-creep the entire desktop.
https://www.aljazeera.com/news/2025/9/6/us-navy-seals-killed...
Not even. If you actually try you will discover at the last step (after full KYC, signing some dubious agreements, and linking an existing TG account) that the Fragment "market" is actually fully centralized and has not been open for new buyers-users for a good while. No secondary markets out there (maybe not even possible on their network) afaik.
I'd personally prefer my employer to not track the religions of its employees and then feed that to whatever people and software they have doing scheduling. I'd be more surprised (not pleasantly) if they did that than if I got scheduled for work on solstice.
Tax on electricity is already a thing. That can be adjusted and even be made progressive. Extra for fossils and so on.
If you are still on yarn v1 I suggest being consistent with '--ignore-scripts --frozen-lockfile' and run any necessary lifecycle scripts for dependencies yourself. There is @lavamoat/allow-scripts to manage this if your project warrants it.
If you are on newer yarn versions I strongly encourage to migrate off to either pnpm or npm.
Certainly with the right investments we'll get there within the next 5 years if you ask Musk and Altman. While a time machine might sound uncertain in that timefram, I'm sure AI will figure it out for us.
Are we just concerning/limiting ourselves with local workflow on a single workstation?
Pretty significant catch if interoperability is a concern at all. Whitespace is easy enough to handle but how do dict keys get ordered? Are unquoted numbers with high precision output as-is or truncated to floats/JS Numbers? Is scientific notation ever used and if so when?