![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Actually, no, this seems to work on a very different principle.
Actually, no, this seems to work on a very different principle.
Not really. It seems to use a very different technology from termux.
I like the idea, but I really hate that they’ve hardcoded the provider.
I’m somewhat skeptical. What if LetsEncrypt decided to misbehave tomorrow? Would the browsers have the guts to shut it down and break all sites using it?
It seems to me like a MITM hacker can just redirect all requests to a Blockchain node towards their malicious node.
Actually, that’s not quite as clear.
The conventional wisdom used to be, (normal) porn makes people more likely to commit sexual abuse (in general). Then scientists decided to look into that. Slowly, over time, they’ve become more and more convinced that (normal) porn availability in fact reduces sexual assault.
I don’t see an obvious reason why it should be different in case of CP, now that it can be generated.
Good point. I’d try to grep for something like [Bb3][Ee3]g[Ii1][nη]\w+<and so on>
but I just know I’ll miss something
Oh, in that case we don’t need to read either - just run a simple grep!
Finally, presumably if anyone added some malicious code in a their program, it would be sneaky and not obvious from quickly reading the code.
On the one hand, doas is simpler. Less code means less bugs, and lower chance someone manages to hack it and gain admin rights. On the other hand, sudo is more popular, and so has a lot more people double-checking its security. Ultimately, I don’t think it matters - when someone unauthorized gains admin rights, usually it’s not due to bug in sudo or doas, but other problems.
AI that can auto generate all those command line arguments I keep forgetting? Sure.
Closed source terminal that requires account? No way.
What social contract? When sites regularly have a robots.txt
that says “only Google may crawl”, and are effectively helping enforce a monolopy, that’s not a social contract I’d ever agree to.
We had Ansible, containers, ZFS and BTRFS that provided all the required immutability needed already but someone decided that is is time to transform proven development techniques
Just so you know, NixOS is older than all of these, actually. And for that matter, no less flexible.
I’m just guessing, but you can try brackets around xclip -o | wl-copy
in the long command.
Exactly! Many of the criteria included aren’t all that good for new users, and neither are the suggestions. It’s not really a good resource for experienced users either.
Well, when you get from 3 to 2000 in only a few years, the vast majority of these versions will be unusable. No wonder they had to drop everything after 11…
That said, you can use a third party service only for sending, but receive mail on your self-hosted server.
Stop asking for pseuso-privacy features. The Fediverse is public by nature. Any “measures” to control access to the public posts on it are just lying to users.
Server owners should be able to control who can access their servers - but that is NOT - and should NOT be - treated as a privacy feature.
I don’t know where this myth came from, but you don’t have a right to erase your public posts from there internet under GDPR. See, for example, https://law.stackexchange.com/questions/32361/does-a-user-have-the-right-to-request-their-forum-posts-deleted
If anything, you might have such rights under copyright law, if your posts cover the threshold for copyright. In that case, you can ask server admins to delete them, and they will have to comply. But the request has to reach them (if they’re defederated, the delete button won’t teach them, and you’ll have to contact them separately).
However, it also uses halium and libhybris. That means you can’t just install your favourite distro and upstream tools. Everything that needs GPU acceleration needs to be patched for libhybris. For example, that means no upstream wlroots - and the latest patched version I think is 0.12 or so.