Conversation

Notices

1. Embed this notice
   Micah Lee (micahflee@infosec.exchange)'s status on Friday, 02-Jun-2023 01:37:51 JST Micah Lee

   My first article about Bluesky! I answer questions like: "What prevents another Elon Musk from buying Bluesky PBLLC and destroying it 10 years down the line?" https://theintercept.com/2023/06/01/bluesky-owner-twitter-elon-musk/

   • Embed this notice
     Eugen Rochko (gargron@mastodon.social)'s status on Friday, 02-Jun-2023 01:37:49 JST Eugen Rochko

     in reply to

     • かき@GNUsocialJP

     @micahflee Out of curiosity, have you compared Mastodon's up-to-date onboarding flow with Bluesky's for this article?

   • Embed this notice
     Eugen Rochko (gargron@mastodon.social)'s status on Friday, 02-Jun-2023 02:00:58 JST Eugen Rochko

     in reply to

     • かき@GNUsocialJP

     @micahflee Isn't a big "Join mastodon.social" on the welcome screen basically equivalent in simplicity? 🤔

   • Embed this notice
     Micah Lee (micahflee@infosec.exchange)'s status on Friday, 02-Jun-2023 02:00:59 JST Micah Lee

     in reply to

     • Eugen Rochko

     @Gargron yes! I tried it out and it's really nice. I mean obv Bluesky still has only one instance so it's not the same, but I think Mastodon's new onboarding flow is great

   • Embed this notice
     feld (feld@bikeshed.party)'s status on Friday, 02-Jun-2023 02:46:30 JST feld

     in reply to

     • beforewisdom :vegan: :tofu:🦣
     • timberwraith
     How do you get raw access to that "repo"? If that exists it should be trivial to make a backup/archival tool of your content in the same format required to redeploy it to a new server.
     
     I have not seen an example of this yet.
   • Embed this notice
     Micah Lee (micahflee@infosec.exchange)'s status on Friday, 02-Jun-2023 02:46:31 JST Micah Lee

     in reply to

     • beforewisdom :vegan: :tofu:🦣
     • timberwraith

     @beforewisdom @timberwraith

     Nope, atproto protects against this. See https://atproto.com/guides/overview#account-portability

     Basically, a user and all their post history are stored in a "repo", similar to git repos, where every post is signed, and each user has a recovery key. Users can switch servers (e.g. pushing their repo to gitlab instead of github) without cooperation from the original server.

     There's nothing a Bluesky PBLLC engineer can do to turn this functionality off. It's how the protocol is designed.

   • Embed this notice
     beforewisdom :vegan: :tofu:🦣 (beforewisdom@veganism.social)'s status on Friday, 02-Jun-2023 02:46:32 JST beforewisdom :vegan: :tofu:🦣

     in reply to

     • timberwraith

     @micahflee
     @timberwraith

     Isn't this naive?.

     One request to engineering to write some code to prevent people from moving their account data to another social network.

     "So hypothetically, if a billionaire one day buys Bluesky PBLLC and ruins it, it won’t matter. Anyone who doesn’t like how Bluesky Social is run can simply switch to a rival service without losing their post history or their followers. "

   • Embed this notice
     Micah Lee (micahflee@infosec.exchange)'s status on Friday, 02-Jun-2023 02:57:06 JST Micah Lee

     in reply to

     • feld
     • beforewisdom :vegan: :tofu:🦣
     • timberwraith

     @feld @timberwraith @beforewisdom heh, I've actually already written a script to scrape repos from atproto. Here's the quickstart guide https://atproto.com/community/quick-start

     feld likes this.