We ♥️ privacy. Join us in our mission to protect everyone's private data: https://tutanota.com/ 😃✊
I will keep my Twitter and Mastodon DM inboxes open and I will be happy to discuss with all of you as usual, but if you have sensitive info to share don't use them
@fs0c131y welcome aboard
A collection of various awesome lists for hackers, pentesters and security researchers - Hack-with-Github/Awesome-Hacking
I’m still not sure about that. When I first started to code, I wouldn’t have understood the need for source control. Not until I got to 1000+ lines and coded myself into a corner I couldn’t find my way back out of, ending up abandoning the project... then I would have understood.
"In schools you have a well structured study plan and a textbook to learn from." - I disagree again 😁
Ok, with this context it's a bit more viable. Still, I'd rather have coding and git taught simultaneously. "Here's your code and here's how you make sure future-you doesn't hate you." And yes, RTFM should be a basic skill.
I disagree. If you're new to coding you've got enough on your plate already. Teaching Git pre-emptively without any coding experience puts abstract processes and concepts like repos etc completely out of context.
1. Learn to code for a bit until you have a basic understanding how coding works
2. Start VCSing your code (within 2 months after starting to code)
@ebourgess every time i tried to teach puppet, i had to spend at least two days on git
makes for a short week to learn about puppet
@ebourgess This is actionable for me because I just picked up a class at the local university
"Meaningful consent" implies more than a clause in the user agreement that says "we can update this at any time." It requires engagement with the userbase at large - and thus guarantees conflict, and compromise.
Maybe Apple would still have disabled this framework. Maybe not. What I do know, with high confidence, is that they didn't ask anyone outside the company if it was okay to do so, or explain what it would mean.
The latest Safari update permanently disables the framework uBlock Origin (and, incidentally, 1Password version 6 and lower) relies on. There will no longer be a uBlock version for Safari.
A while ago, someone on Twitter raised the point that users are rightfully gunshy about software updates because developers often use them to make unilateral and unwelcome changes. The question "did your users meaningfully consent to this change" goes unasked, let alone unanswered.
I want better.