I think it's the opposite. Most people aren't that egotistical. We all feel quite small relative to history. But I think OP is highlighting that even history is quite short. Ancient Rome, which feels like a very long time ago, is actually only 80 generations ago. If "life's short", then 80 lives is short too.

Defining a threat model means to qualify what sort of attacker you expect to face and what they are assumed to be capable of

Which is exactly what OP is talking about. 5 years ago if you were only trying to defend against script kiddies, using containers was good enough. But now you have to consider that script kiddies might find container escapes.

There's a world of possibilities between "public facing server" and "turn the internet off". Like using a VPN or mTLS. Or only connecting when you are at home.

However it sounds like you aren't worried about the increased threat landscape, or at least aren't willing to compromise on your current level of convenience. That is a fair answer to OP's question.

FYI if you are talking about HTML and CSS fingerprinting, I have never seen them used in the wild, and they are trivially detectable (for example a bunch of hidden :hover elements on the page), so Tor Browser would add defenses if they did start appearing in the wild.

That's a good point. If you are using a physical server you own, hopefully you set it up locally first. If you are using a VPS, hopefully you configured it with key authentication from the get go. Otherwise, you'd need to find a way to identify that the box you ssh-ed into is indeed the one you expect. Luckily, if it's your first time logging in, then you probably don't have any data in the server either, so there's nothing to steal if the hackers get your password. So just enter your password, see if it's the right box, and if not then reset it and try from a different tor circuit.

DNS requires consensus (on who owns which name). So if by "voting peer system" you are talking about decentralized consensus, then blockchain is one of the only systems of such kind.

If you don't want blockchain, then there's no real choice other than a centralized system like CAs.

how clusters decide which members are reliable and which should be deemed faulty.

I believe you're talking about RAFT. That requires trusting all nodes, so it's not any different from how CAs already work. After all, the issue at hand is a compromised CA.

It sounds like this case is actively being investigated by legal authorities, and whether or not Destiny knowingly possessed CSAM is still not determined.

I think the responsible thing for the internet to do is to wait until clearer facts come out, instead of casting judgement early and making the situation way more messy.

Related discussion on hacker news: https://news.ycombinator.com/item?id=50172041

The demo video has been going around Twitter today and apparently the proof of concept is privately being shared around too. The video shows pasting something in the URL and then gaining a shell on the server. It looks completely catastrophic.

I think the best course of action is to just shut your server down before the patch goes live and then bring it back after you have patched.

video here: https://twitter.com/k_firsov/status/2112641845926989944

(Look for a Nitter instance if you don't want to use twitter)

Wasn't the Gamer's Nexus video on LG spy TVs, saying that the telemetry traffic is protected by SSL and thus they couldn't figure out exactly what was sent? Would they be able to use the leaked keys to decrypt the traffic?

Thanks, I wasn't sure if it mattered that the leaked keys in this case were for intermediate certs and not root certs (afaik)

reposting what I commented in another thread:

SSH MitM attacks are very easy to pull off. To secure yourself, use key authentication instead of passwords, and don't ignore the warning that SSH will give you saying "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED".

If you are using something like Tails, you will need to make sure to persist the ssh hosts key file (~/.ssh/known_hosts), or else you will not not be warned when a MitM attack is being performed.

More discussion here: https://news.ycombinator.com/item?id=50166257

Fingerprinting can usually identify you uniquely. So even if only two people in the world were using NoScript, it would still be more private than getting fingerprinted.

Edit: btw I'm talking about Javascript fingerprinting. Other methods like HTML and CSS are far less effective and rarely seen in the wild.

I'm too lazy to read the court docs but I'll just say this:

IF what you're saying is true about the case being about a revenge porn case involving a (pretend) 19-year old girl, and the above commenters are claiming it as CSAM or sexting involving minors, then this is gross misinformation and you should not be downvoted so hard for calling it out.

Pray tell

engagement bait probably

And people wonder why so many devs use Electron. It may be slow and a RAM hog but hey it works.

If you use Tor + NoScript, you won't be unique. You'll blend in with the other Tor + NoScript users, of which there's probably hundreds

How so? Just because the store was able to procure one good fruit means nothing about the quality of the others.

That's fair, but this thread is also full of people questioning the courts. If regular citizens can't be trusted to judge, and courts also can't be trusted to judge, who is to judge? (If we trusted all victims of any crime, you can see how that could be easily abused.)