I’ve looked through the available info and everything adds up. Yes, it seems that activists managed to archive at least 30TB of #Parler data. It’s now safe to use the past tense when speaking about Parler. Even ignoring the technical difficulties, there is no coming back from that.
Hi #Twitter, this “browser” is the current Thunderbird release, a mail and RSS client. Its capabilities are no different from Firefox 78. How about you detect Gecko rather than detecting Firefox?
Better yet, do feature detection instead of UA sniffing: https://developer.mozilla.org/en-US/docs/Web/HTTP/Browser_detection_using_the_user_agent
Wonderful how #Exim team fully recognizes that the use_shell option is a massive security footgun. So they warn users. In a separate document, not linked from the option’s documentation. Never mind not explaining which characters are ok, so users are bound to get it wrong.
That’s a weird one – the below is an exact copy of Firefox’ about:neterror page, but it’s apparently being served by #Cloudflare (?) as a 404 page. It’s even using browser’s own scripts and styles which is rather dangerous since these could change. I fail to see the point…
Update: today #Giggle’s @firstname.lastname@example.org published a new statement. It’s a good first step, though for my taste it’s a bit thin on reflection of her own role in this mess. What’s still missing however is some statement on the privacy issues. Will these be fixed as well eventually?
The bad news: @email@example.com threatens to sue the researchers unless they let her approve the publication first. They kindly decline, as they should. And she shares that communication publicly as well, somehow assuming that it puts her in a better light?
Somehow, the email communication still happened, the right person received the report and confirmed it. So a bit later today @firstname.lastname@example.org started sharing the image below – without retracting any of her claims, somehow assuming that this reinforces her points.
So today she proceeded by once again attacking the researchers and criticizing journalists who were asking her about the security vulnerability, restating that it didn't exist.
And she claims that @DI_Security@twitter.com researchers publicly called her a transphobe. Not sure what this is about, I could only find a tweet by @email@example.com who appears to have no relation to the researchers. Judging by the way @firstname.lastname@example.org responded she thinks otherwise.
She says that they should have emailed technical department directly – yet from a brief look I cannot find the corresponding email address anywhere. From experience, emailing technical support about vulnerabilities is a bad idea. So Twitter is a valid way to approach a company.
Software developer and security researcher, browser extensions expert. He/him
Other Mastodon account for non-technical topics: https://social.tchncs.de/@WPalant
A Mastodon instance for info/cyber security-minded people.