introduction, long toot
#introduction time! Just gonna adjust the one I've used elsewhere.
* more or less stock model white cis male 40-something FOSS-friendly geek in Seattle WA USA
* New to hackers.town, but been on using Mastodon for a bit. Like a lot of folks I mainly visit when other social networks annoy more than usual
"Samsung made a Giphy page of comeback GIFs to send people who diss green bubbles" by Ashley Carman https://www.theverge.com/2019/8/21/20826812/samsung-giphy-gifs-instagram-meme-makers-blue-green
I remain fascinated that this is a thing. The linked podcast episode is worth listening to.
🌶️ : Im going to stop buying into the industry narrative about ad blockers. They are not ad blockers, they are content blockers. The content I am choosing to control happens to come from advertising networks that have proven to be vectors for malware infections and misbehaviour for years. I'm not blocking ads, I'm not stealing from you, I'm protecting my systems just like I would with an anti-virus program.
Recommended reading list for programmers by Alan Kay. Some interesting choices in there. I imagine a lot of these are older than most of our community.
"Experienced programmers and computer scientists, what are some really old (or even nearly forgotten) books you think every new programmer should read?"
Nearly done with this #drawing
<long time reader, first time subtooter...>
I know that sounds catty, and it kind of is. However, comma, security systems that make it easy to screw up and get into an insecure configuration with no appreciable degredation of performance are inherently dangerous.
Silently failing-insecure (or failing open) is dangerous.
Not tall. Occasionally crafty geek in Seattle. he/him
A bunch of technomancers in the fediverse. Keep it fairly clean please. This arcology is for all who wash up upon it's digital shore.