• 1 Post
  • 18 Comments
Joined 1 year ago
cake
Cake day: August 8th, 2023

help-circle









  • If you want your timeline to be just a chronological timeline, you can also subscribe to that feed and delete all others. Bluesky isn’t Threads, no one is forcing any algorithm on you that you don’t want, this is part of the decentralized nature of Bluesky.

    Also, I don’t think there is a clear line between “algorithmic” and “non-algorithmic” social media. If you use Mastodon with the Mammoth app and its “For You” feed, is it algorithmic or non-algorithmic? If I sort my Lemmy timeline by “hot”, do I not use an algorithm?




  • I’m very curious how this will all shake out. I can understand all of you who want to block Threads and the only two instances that I am on myself are going to do exactly that, but it seems tremendously likely that the flagship instance of the fediverse, mastodon.social, will federate and it will have a massive impact on not just the culture, but also on the codebase. For example I wonder what services will go for feature parity and add features like voice notes which Threads added recently. Oh and culture-wise, with POTUS joining Threads, big institutions like the White House will suddenly appear on the fediverse.

    Still holding out hope that a bunch of new users and new ideas will rejuvenate the fediverse, in any case 2024 should be a big year for it.





  • You are correct, however I want to point out they have stated they want to hand over the governance of the protocol to a standards organization like the Internet Engineering Task Force:

    Development of atproto to date has been driven by a single company, Bluesky PBC. Once the network opens to federation, protocol changes and improvements will still be necessary, but will impact multiple organizations, communities, and individuals, each with separate priorities and development interests. If the protocol is successful, there certainly will be disagreements and competitive tensions at play. Having a single company controlling the protocol will not work long-term.

    The plan is to bring development and governance of the protocol itself to an established standards body around the time the network opens to federation. Our current hope is to bring this work to the IETF, likely as a new working group, which would probably be a multi-year process. If the IETF does not work out as a home, we will try again with other bodies. While existing work can be proposed exactly “as-is", it is common to have some evolution and breaking changes come out of the standardization processes.

    Source