![](https://lem.serkozh.me/pictrs/image/6488e3d7-6db4-47f4-9645-8159b532517e.jpeg)
![](https://lemmy.ml/pictrs/image/c0ed0a36-2496-4b4d-ac77-7d2fd7f2b5b7.png)
ok, my age is NULL
ok, my age is NULL
I’m pretty sure that Lynx does not
It doesn’t make a lot of sense for LetsEncrypt to spend time adding support for such certs, since both a domain name and a cert from another CA are cheaper than buying an IPv4 block
certificates can only be obtained for domain names
That is not true, nothing prevents it on the technical side, and even some trusted CAs sell them under certain conditions
you can also accomplish that by turning off city’s electrical grid
On a similar scale, but with consequences like zeroing out savings and maxing out credit cards of several dozens of millions of people or violence for political views/sexual preferences/etc on the same scale. Basically, something that will make a large number of people learn about the importance of privacy the hard way.
I wonder how a recipe to make baked beans ended up in Copilot’s training sample
You can’t read documentation if there is no documentation
Not until there is a massive data breach that leads to very serious and obvious real world consequences
This comment is posted through my personal private instance :)
I tried building lemoa with simple cargo build
, and it says it needs libadwaita 🤔
You can self-host GitHub too, but a license for GitHub Enterprise Server costs a lot of money
A friendly reminder that after more than 3 years since libadwaita’s announcement it still doesn’t provide a way to make it look less horrible and out of place anywhere outside of GNOME’s walled garden
It is very unlikely that someone is gonna bother creating malware for Linux unless it’s a targeted attack
GitHub and GitLab are both public US companies, they are gonna happily comply with any DMCA request they receive
Forget about Reddit. The shittier it gets, the better for us. It will also help keep aggressive haters out of Lemmy by accumulating them outside.
BitTorrent v1 does not hash the files, it hashes chunks (pieces), and they can span multiple files
I wonder what is the last rule there…
Inaccurate, this error fits on one screen
Windows: “We dropped support for that thing you bought brand new 5 years ago”
Linux: “We are considering dropping support for something that has existed for longer than you had”