Conversation

Notices

1. Embed this notice
   Elias Mårtenson (loke@functional.cafe)'s status on Saturday, 15-Jul-2023 00:24:33 JST Elias Mårtenson

   • Thomas 🔭🕹️

   @thomasfuchs imagine if they were using a federated protocol. Then they could have moved to a different instance.

   • Embed this notice
     Ben Ramsey (ramsey@phpc.social)'s status on Saturday, 15-Jul-2023 00:32:01 JST Ben Ramsey

     • Thomas 🔭🕹️

     @thomasfuchs How many people work on Bluesky? I would estimate no more than 10-15, if that. Three people are on the board. Each employee is an equal owner (according to what I’ve read in their FAQs). I don’t want anyone to dogpile on ICs, but I think they’re all “leadership.”

   • Embed this notice
     Jack Baty (jbaty@social.lol)'s status on Saturday, 15-Jul-2023 00:48:16 JST Jack Baty

     • Thomas 🔭🕹️

     @thomasfuchs I'm a little confused because your initial post seems to claim that (for this specific problem, at least) there's a "easily available" technical fix for the username issue. That doesn't sound the same as a "social problem that can't be fixed with technology". Granted, it was a pretty glaring oversight, but I'll wait before piling on. Public silence from the (small) team doesn't really tell us much yet and I think it's unwise to presume anything based on that.

   • Embed this notice
     Marie M. (adhdmarie@mastodon.ie)'s status on Saturday, 15-Jul-2023 00:48:55 JST Marie M.

     • Thomas 🔭🕹️

     @thomasfuchs It's worse than that. From what I understand, black, trans and other minoritized users were given tons of invites so they could build up the community over there. Meanwhile their calls for safety and moderation were largely ignored. Blocking was only finally instituted in response to an incident involving a big-name Twitter user.