I trust F-Droid. I don't trust millions of developers. I don't have time everytime I need an app to go investigate, especially now with quick LLM scam app developer

Developers are not geniuses at every aspect of security or app deployment. They can sell their projects. Get compromised. Or can get tricked like the xz exploit

Having an app store making any effort to prevent or correct problems, especially as transparent as F-Droid, is better

Wireguard app dev wanting to bypass the store and push an executable to your phone every day is ridiculous. No user of app/package manager expects it to be bypassed

F-Droid has arguably produced more value than GrapheneOS for open source community, independent ROM users, and android in general

Was in a bigger city in the weekend, and they don't have many benches. But it was nice in a way because people just sat anywhere every stair case step, every curb, grass patches, next to a tree, train station floor,...

Where there was a bench 5 people would sit, where there wasn't 15 did

Of course it was a pleasant weather otherwise...

Your comment sounds like half LLM slop, half confusion

Even so, I would still let them download double that, if they reduced the RAM consumption in half

It would be better a systemwide download? Of course

Maybe manually point to a local endpoint with one of the multiple 100s of GBs of models that I already downloaded? Even better

Don't even know what the model is for... but as things are, one of the alternatives would probably be send high amounts of user data to google which is worse. I would personally pay to have a 4GB download and keep my data/privacy

So this is an odd take from a "privacy guy"

I have used OsmAnd for maybe 10y. And it has been surprisingly good

Several countries. Works offline. Saves the journey taken

Not the best at finding places sometimes. Food places and ratings still has to be google or trip avisor, but those are very relative too. Wherever you go the key e some preparation anyway

For direction I think it is rock solid

This reads something between cluless/malicious and genius. Crosses several red lights with a car, smashes the car, rebuilds the car with AI, tells people to cross red lights

Keeps repeating btrfs check --repair . This command is dangerous and warned anywhere as a last resort: if you try to execute it you get a warning; the documentation has a warning; any guide from google tell you not to run it unless all else fails; chatgpt/lechat do not metion it, or note it as last resort. So not sure why he keeps repeating it without any note

> Use these tools ONLY if btrfs check --repair segfaults, enters an infinite loop, or leaves the filesystem in worse shape than before.

> Timeline of events ... First repair attempts. btrfs check --repair

The guy is recommending people brick their volumes permanently as first resort without any warning

Between using a dup profile and this I would not be surprised a btrfs dev just disregarding all as slop

> Pool only mounts with rescue=all,ro, fails to mount RW

Also this is important, the data was not lost. Even though read-only

I don't think I would run this code. Still it would be interesting a btrs dev to have look and comment if there is any value in the code generated. As it would be definitely interesting being able to repair more issues in the pool safely inplace

> "...oh, they had women and non white people on board..."

That is from the article