There's what, about 100 of us still, I imagine most are blocking the ads too.
For a long time slashdot was blocking them for me, as some sort of legacy reward. That stopped, but the ads have been unobtrusive so I left it unblocked. Last week I started seeing an ad that stayed on the screen when scrolling. I was about to start blocking, but that ad has disappeared. So for now this is one of the few sites I don't block.
Do these people really think they're hiding Directive 4 from us?
We are only a year out from the murder of a health-insurance executive, so the police are more on edge than usual.
Then we need to threaten such things much more often, so that the cops will eventually get used to it, and relax.
Debian never tried to kill me through my computer. I'd appreciate it if my car manufacturer made their car as safe as my computer.
Fuck it, I just want a Debian car. Then I won't need to extract bloody vengeance from beyond the grave, as my zombie revenant tracks down the CEO of Subaru, and the rotting flesh of my hands tightens around his throat as payment for the time a popup distracted me.
Some people are busting out "definitions" of "End to End Encryption" but people were already using that as in informal descriptive term long before your formalized technical jargon was made up. Nobody should be surprised if there are mismatches. Have faith in our faithlessness.
I personally view the term as an attempt to call semi-bullshit on SMTP and IMAP over SSL/TLS. In the "old" (though not very old) days, if you sent a plaintext email (no PGP!), some people would say "oh, it's encrypted anyway, because the connection is encrypted between your workstation and the SMTP server, the connection from there to some SMTP relay is encrypted, the connection from there to the final SMTP server is encrypted, and the recipient's connection to the IMAP server is encrypted."
To which plenty of people, like me, complained "But it's still plaintext at every stop where it's stored along the way! You should use PGP, because then, regardless of the connection security, or lack of security on all the connections, it is encrypted end to end. Never trust the network, baby!"
Keep in mind that even when I say that, this is without any regard for key security! When I say E2E encrypted, it is implied that the key exchange may have been done poorly/incorrectly, mainly because few people really get to be sure they're not being MitMed when they use PGP. You can exchange keys correctly, but it's enough of a PITA that, in the wild, you rarely get to. You usually just look up their key on some keyserver and hope for the best. Ahem. And I say "usually" as if even that happens often. [eyeroll]
Indeed, every time I hear about some new secure messaging app/protocol, the first thing I wonder is "how do they do key exchange?" and I'm generally mistrusting of it, by default. And sometimes, I'm unpleasantly unsurprised, err I mean, cynically confirmed.
But anyway, if my E2E definition matches yours, great! And if it doesn't, well, that's ok and it's why we descend into the dorky details, so that we can be sure we're both talking about the same thing.
They also didn't start delving into DEI madness in 2010...neglecting the engineering to chase the "diversity" ghost
We would certainly be at a disadvantage if Russia was able to copy rockets that constantly blew up shortly after launch.
How many hours of an Asian font designer'(s) time can you buy for $20k? It'd be funny, if it turns out that firing the font company pays off in less than a year.
16.5 feet in the Twilight Zone = 1 Rod Serling