• 1 Post
  • 19 Comments
Joined 3 years ago
cake
Cake day: June 11th, 2023

help-circle
  • I’d argue the opposite. If we want to restrict access of kids under 14 to social media for example, then the parents should just be able to tell the device/browser, that they should inform the websites that the user is under 14. not the exact birthday, not even the year, just <14, <16, maybe <18, so that the website can adjust accordingly. That would be way less invasive then having everyone show their ID on account creation.



  • I was surprised about this ratio (and the fact that it seems to work for them), too. I could imagine that a large percentage of lurkers and a maybe more reasonable community than other platforms could be helping factors?

    My mastodon account is on a kind of small instance, and I’d love to be able to report posts directly to the originating instance, without also reporting it to “my” admin. I just don’t wasn’t then to waste their time locally blocking a clear spam account, that should (and usually will be) removed by the originating instance in a couple hours.
















  • I mean, this is a light-hearted meme, no offense to the people actually fixing things.

    But at a company like GitHub the first status update should be and probably is created semi-automatic (just approved by a human). Afterwards they should follow a process to assign an incident communication lead, who takes over all communication so that the rest of the team can work on fixing the incident.

    @GitHub: Hire me for more incident response tips from the backseat! :P