251–260 of 317 posts
Earlier quoted context omitted.
There is an easy solution: don't log into facebook. Anyone you want to talk to on there has a phone.
Are many folks on HN using Facebook? To me, most tech savvy folks I know left it a decade ago. All the FB users I know are 60+
Earlier quoted context omitted.
I meant for CLI tasks. Just "adduser" and "sudo -u bash".
And when you want to share some but not all files with that one user but not other users you created for similar purposes? And when you want the outputs of that user back to your main user? And when you want that user to access some shared credentials for external services, but not all? It’s not the account setup that’s hard, it’s the workflow of spreading a single real-world across multiple accounts.
Can't ACLs (Access Control Lists) handle at least some of that?
Earlier quoted context omitted.
Docker is old tech, yes, doesn't mean every dev in the world uses it. They don't. Jails/zones are even older (hell a chroot). Did developers all use those before due to them being 'old tech'. No.
Any reasonably big project uses docker because it's a very simple way to have the exact environment in both production and in dev. Also it is helpful for keeping things isolated. In all projects I've worked for the las ten years for several major companies, docker has been a requirement.
"Just 30% of developers say they use containers in any part of their workflow." https://www.docker.com/blog/2025-docker-state-of-app-dev/
So, yea. Large companies, yes, for sure. But that's not 100% - is it.
Earlier quoted context omitted.
It has always been very easy to create separate users on Linux and certainly for tasks where you need to switch between contexts. Linux is a unix, so has always been multi-user and sharing any data between processes is facilitated in all manner of ways. So context could be shared over files or unix-domain sockets or shared memory or tcp or udp sockets or via message passing or … a bunch of other ways. That has been t…
Separate user accounts are irrelevant when any one user has sudo and can therefore change binaries for everyone.
Earlier quoted context omitted.
Still wild to name a sandboxing software after one of the most infamous Soviet Gulags in history.
It's wilder to accuse someone of naming the container version of the lima sandboxing software after a gulag. These type of moral outrage comments take an extreme amount of effort to debunk compared to writing them. 1. There is no gulag called Colima, it doesn't exist. 2. There was a gulag near a river called Kolyma 3. The pronounciation and spelling of Kolyma and Colima are completely different, in fact Colima is an…
I was curious if the adjacent tool name (Lima) had anything to do with the capital of Peru, but I guess not.
This is why I feel prompt injection is going to continue to be an issue. Fantastic that “Hi we are Cloudflare, give us your personal data” works. Either we stunt the models to the point where they are not useful, or we allow things like this to seep in and create one of the most insecure concepts the internet (and maybe tech as a whole) has ever seen: a robot that can be tricked.
Earlier quoted context omitted.
I meant for CLI tasks. Just "adduser" and "sudo -u bash".
And when you want to share some but not all files with that one user but not other users you created for similar purposes? And when you want the outputs of that user back to your main user? And when you want that user to access some shared credentials for external services, but not all? It’s not the account setup that’s hard, it’s the workflow of spreading a single real-world across multiple accounts.
Use GLM-5.2 on ZDR inference provider like sference.com
What?
I'm getting negative reaction for providing an obvious solution. Anthropic stores all your prompts as well and uses it for training.