There is nothing there about FUTO forcing them to stop focusing on anonymization. I’d be careful to draw such conjecture. Besides, this is one reductive take from one party of a contentious split.
- 0 Posts
- 19 Comments
Joined 13 days ago
Cake day: January 6th, 2026
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
You could try https://winuxos.org/ and see if he notices any difference. What could possibly go wrong? ;)
Great day to you too
SimpleScreenRecorder never failed me. Does what it says.
You could also try Kazam.
7·3 days agoPhone. And Location 🙃
One example of how permissions UI on Android is too coarse. Arguably mocking location is a questionable use but this pattern crops up everywhere. I think users must have more fine-grained control over what apps can access regardless of what devs put in their mainfests. It’s reasonable that a user wants an app to have access to GPS coordinates and network access but not cell or wifi info.
In general GrapheneOS gives more flexibility and power to the user than stock but I’m not sure if they go far enough to support what you want to do.
This is still crypto, yo
Possibly oversimplifying and didn’t have a proper read yet: If you trust the hardware and supply-chain security of Intel but not the operational security of Cloudflare or AWS, this would allow you to exchange messages with the LLM without TLS-encryption-stripping infrastructure operators being able to read the messages in cleartext.
This is a form of Confidential Computing based on Trusted Execution Environments. IMO the real compelling use of TEEs is Verifiable Computing. If you have three servers all with chips and TEEs from different vendors, you can run the same execution on all of them and compare results, which should always agree. You will be safe from the compromise of any single one of them. For Confidential Computing, any single one being compromised means the communication is compromised. The random nature of LLM applications makes Verifiable Computing non-trivial and I’m not sure what the state-of-art is there.
And yes it does look like it has overhead.
This seems impossible from a scalability perspective, as even small LLMs require huge quantities of RAM and compute. Did I miss something fundamental here?
Well isn’t it the other way around? If the per-user resources are high, the additional sublinear overhead of isolating gets relatively smaller. It costs more to run 1000 VMs with 32MB RAM each vs 2 VMs with 16GB RAM each.
However I guess this might get in the way of batching and sharing resources between users? Is this mentioned?
Discord
</3
4·5 days agoIf you feel overwhelmed by this, an easy rule of thumb is sticking to distro packages of a trusted dist. Ideally ones with long track record, centralized packaging and tiered rollouts.
Roughly,
-
High community trust: Debian, SUSE, Fedora, Ubuntu
-
Depends on the package but at least everything is transparent with some form of process, contributors vetted, and a centralized namespace: Arch, Alpine, Nixpkgs
-
Anything and anyone goes, you are one typo away from malware but hey, at least things get taken down when folks complain: AUR, GitHub, NPM, DockerHub, adding third-party ppa/copr
-
IDGAF:
curl | sh
-
Of course.
As Arch becomes mainstream and more of an attractive target for attackers I think we will get more of the same thing happening regularly in NPM: Legitimate popular packages getting compromised because a maintainer got infected or phished.
As well as botting of votes and comments.
https://www.theregister.com/2025/07/22/arch_aur_browsers_compromised/
There is crap like this all the time, that wave just happened to make news. Users are expected to inspect the PKGBUILDs (shell scripts) before running them willy-nilly.
You do as you wish but please don’t normalize dangerous behaviour.
Friends don’t tell friends to “Just
curl shiny.tool/install | sh” or “Justgit cloneanddocker-compose up”.
If you check it with Tor Browser in a clean VM, you are not leaking much more than the plate number as such (which I wouldn’t say has the same sensitivity as a password) and the time of lookup. Obviously not safe to use this from your normal smartphone or home IP.
Note the date. This blog post is a few months old. I was expecting new drama on the latest episode of Who Hosted Whom (and does that make them fascist (and does that matter)) until new events but i guess it’s just reruns this week.
On nginx, most of the upstream work on new features is in Nginx Plus, not benefitting free nginx. Several nginx devs have been disagreeing with the way this has been done and the way the project is being managed and left to work on forks. People who agree with the OP sentiment should look into freenginx and angie.
https://www.phoronix.com/news/Nginx-Forked-To-Freenginx
https://mailman.nginx.org/pipermail/nginx-devel/2024-February/K5IC6VYO2PB7N4HRP2FUQIBIBCGP4WAU.html
Some things that happen when I go to duckduckgo.com that also go against that:
- Harvesting the third-party cookies it can (example: github.com)
- Attempting to enumerate browser extensions
- Attempting to enumerate crypto wallet addresses from extension wallets like MetaMask
It’s extremely nosy. They used to do canvas fingerprinting until browsers started prompting about it.
IDK about the claim of directly selling searches to IG and likely it’s a bit more convoluted than that (or OP has malware) but it’s a more believable idea than that of DDG actually being respectful of user privacy. There is absolutely no legitimate reason for DDG to gather this data for the purpose of providing their search service, yet they do.
You are not helping!
(But also not wrong)
I haven’t dug into them deeper but Fossify have what seems to be decent basic options for all of the base Android apps: Phone, SMS, keyboard, camera, etc.
Just replacing all the stock apps with the Fossify suite looks like it could be an easy privacy win for someone stuck on a device with locked bootloader and dodgy stock apps from vendor or Google.
Hex Launcher: https://f-droid.org/packages/com.mrmannwood.hexlauncher
Pie Launcher: https://f-droid.org/packages/de.markusfisch.android.pielauncher
Similar approach in both of these
Why does this keep making the rounds three months later? There is plenty of public commentary both from back then and more recently if you do a quick search. Everything has been said. Let this rest already.