re: A long analysis of FOSS fans
We talk about this pattern in my family as "the asshole problem". If you are too tolerant of assholes in a space, good people start to leave and the assholes invite their friends, until at some point your space is overwhelmingly assholes and you likely lost the power to fix it.
US pol, election
@Ent they were against *direct democracy*, and favored a *republican democracy* instead. My point it's like you're saying "they wanted a TIGER not a FELINE", when it's more "they wanted a tiger, not a lion"
US pol, election
@Ent The US *is* a democracy. The kind of democracy it is: federal republic
@rysiek I'm all for a simplified default experience, but I miss when designers offered a straightforward path to the advanced features instead of completely hiding/disabling them
Always proud of the work @Veracode@twitter.com does on the State of Software Security report. Volume 11 is no exception: https://info.veracode.com/report-state-of-software-security-open-source-edition.html
(If you don't want to give out your contact for access, hit me up and I'll happily get you a copy)
If you use 3rd party network filters (like VPN clients or firewalls) on macOS, hold off on Big Sur. Pretty big hole that Apple's apps use and malware can use to bypass such tools using the new network filter system.
And this is why phishing is worth attackers' investment (HT WeldPond): https://twitter.com/tazwake/status/1326169429449854978
“Got to see my favourite type of Incident Ticket today.
User got suspicious email, reported it because when they followed the link it went to a sign in page but 'none of their corporate credentials worked'
For added value, service desk closed ticket cos it wasn't a supported site”
@suetanvil @varx @technomancy the youtube-dl project could file a counter-claim, and GitHub has to then promptly restore the content. But a counter-claim is basically saying "I'm right; sue me or STFU", and I don't blame the maintainers for not wanting to take on the RIAA's deep pockets
Anger at GitHub/Microsoft over this situation, though, is misplaced
@suetanvil @varx @technomancy that is what GitHub is literally legally required to do under the DMCA. They don't have standing to push back. The way the DMCA is written, if someone makes a copyright claim about something you host, you MUST take it down promptly. You don't have the option to push back
Asking MS to "push back" on a DMCA claim is asking them to break the law
Applied AppSec Research @ Veracode ; I don't speak for them here. Part-time coffee and Arduino nerd.
A Mastodon instance for info/cyber security-minded people.