It's amazing how clueless people are. In this case, the person is clueless about both Section 230 and Libertarians. Section 230 doesn't say what this person thinks, and there's no way Libertarians support the "speech" policies this person wants.
Everybody suggesting a change to Section 230 doesn't understand Section 230. It's weird how common this is. It's because they don't care what it currently says -- only what it might make it say in the future.
And the thing they want it to say in the future is something something suppress speech they don't like and something something promote speech they do like.
Libertarians believe in two separate things:
#1 speech, even by those you disagree with, is a good thing and shouldn't be censored, not even by private actors
#2 private actors should be free to censor speech they don't like, even when they are bad people for doing so
It's a hard thing to understand because non-Libertarians feel if something "should" happen then government "should" make it happen. Libertarians believe lots of things should happen, but government shouldn't be involved.
So Libertarians feel Twitter and Facebook should stop their censorship, but at the same time, would vehemently oppose any law that would try to make this happen, including whatever nonsense people believe about Section 230.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
I decided yesterday to spend this weekend writing a regular-expression library in C. How's your weekend going?
I want multiple pattern matching for lex grammar parsing, packet parsing, intrusion-detection, and IoC recognition. None of the libraries out there do a good job for this.
The "regular" in "regular-expression" means parsing them is real easy, just read characters left to right. It's actually easier to write code to implement them than it is to use them.
For decades, we've been preaching "cybersecurity is not just about the perimeter", yet every time our community is tested, we fall back to "it's just the perimeter". We've been lying this entire time.
The #1 reason ransomware has such a devastating impact is because we put all our security eggs in the Active Directory basket, then the hacker gets Domain Admin, and the game is over.
No it wouldn't, because there aren't any good cybersecurity metrics.
"Standardization" implies people are doing it, but in different ways. With cybersecurity metrics, people effectively aren't doing it. What metrics people do track are largely hocus-pocus handwaving.
By the way, my tweet above is easily falsifiable: all you have to do is tell me one statistic that would be meaningful for a government body to track, that would give policymakers or business leaders meaningful insight into the state of cybersecurity.
Or, think of my tweet as a challenge, because if you can show me useful things that Bureau of Cyberstatistics might track, then I'd be an ally strongly promoting the idea.
Ah, memories! I was giving a talk at PasswordCon on "Password Misconceptions" or something similar. A previous speaker was "caught" unlocking their screen before their presentation with a short password. Everyone knows short passwords are weak.
So when it was my turn, I did the same, because I'm a jerk (I quickly edited my talk to add a slide).
The audience saw me connect my laptop to the projector, saw the lock screen appear, and saw me type a short password [******] to unlock my computer to start the presentation.
They laughed at me for my weak, insecure password. How could somebody be talking about password security and have such a weak password on their laptop??
This is normal NYTimes fair: "My provider of anti-science medical quackery called chiropractics holds anti-science medical quackery opinions about vaccines. Is this unethical?"