After Nearly 10 Years of Building Mastodon, Eugen Rochko Steps Into Advisory Role
General Discussion
1
Posts
1
Posters
13
Views
-
After Nearly 10 Years of Building Mastodon, Eugen Rochko Steps Into Advisory Role
Mastodon's creator steps back from CEO role, transfers assets to non-profit organization.
https://blog.joinmastodon.org/2025/11/my-next-chapter-with-mastodon/
Gli ultimi otto messaggi ricevuti dalla Federazione
-
A working group might be able to come up with other, non-software strategies for dealing with this shit. Perhaps relying on new features in the software that don't actually ID anyone but could attach the status of having BEEN IDed or just let in and I'll take responsibility.
But it takes actually thinking about and studying a problem to come up with answers like that. You can't just shove your head up your ass and then yell at it.
-
@nitrml @fbinin @ret @mellifluousbox Should be noted that if we all actually did manage to get sentenced to prison we'd either break the system or end up in warehouses in the desert surrounded by overheated assholes in cammo.
Either way, problem solved.
-
@mellifluousbox It has to be thought about. Sometime soon people may have to decide if they're going to implement age verification or shut down their servers. If they're to be provided any answers, be they implemented options or a documented reason why this is just done, then the effort to come up with them needs to start before they're needed.
-
Also, you should give yourself a break and use the miscellany context.
-
@nitrml how do you think they’ll implement age verification on mastodon dot social? Special fork? No. It’ll be baked into the software, which will create a precedent for this to be implemented everywhere.
-
@gbargoud they’re free to make their own decisions about whether they comply or not. The instance I’m using right now is in violation of UK law. Probably Saudi law, Iranian law, Chinese law, etc etc… there’s no winning this.
-
@raphael @liaizon @smallcircles @django ha! There are a lot of Djangos involved in the social API.
-
@ret you claim things ("no need for a working group") and when told that they need to assess their organization for these risks (not the software! Their organization!) you start talking about the software. If you dont care what they do regarding dot social, then this whole thing shouldnt be relevant to you.
Except if they do something to the software itself. That would impact other servers, and that would be a different discussion. But thats not where any of this is right now.
