Despite understandable misgivings with ATProto due to its corporate origins and its architecture lending itself to centralization, it’s still open source. Moreover, it serves a different purpose compared to ActivityPub, in that it specifically aims to enable and support larger scale social networks.

In a way, ATProto could be complementary to ActivityPub, but for this to be the case, there needs to be more shared understanding between both communities. People working on both recognize the faults in existing social media, and aim to address them in different ways.

ATProto provides an opportunity to break down big social media enclosures with data portability and a similar vibe to big social media, but with more individual empowerment to adjust what they see. The latter point is a commonality with ActivityPub, but ActivityPub provides a different angle of breaking the big social media enclosures.

Where ATProto serves the interests of those into big social media vibes, ActivityPub serves the interests of those into small social media vibes. In other words, ATProto scales up, where ActivityPub scales down.

ActivityPub is arguably a better protocol for both individual and “small” group empowerment, as it can enable otherwise less active, small platforms to connect and ensure there’s always some level of activity to encourage people to come back. Think of old forums that, on their own, gradually faded out as people stopped visiting and posting for more active online communities. ActivityPub can serve as a buffer against that, to some degree.

Together, both protocols could provide a better, open social web, and perhaps effectively topple big social media enclosures. After all, who wouldn’t like to see the web without Meta/Facebook and Twitter/X?


TL;DR: ATProto/ActivityPub have a common foe in big social media enclosures like Meta/Facebook and Twitter/X and would be better served working together to erode their influence.

    • Kichae@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      7 days ago

      many ActivityPub folks don’t want to federate with big companies anyway

      This really shouldn’t be a consideration. ActivityPub is a public standard for this kind of communication between websites, and the protocol really needs to be agnostic about which websites one is interested in using it to connect with. “I don’t want Amazon using HTTP along side my indie blog” is a nonsensical statement, and so it “I don’t want Facebook using ActivityPub”.

      • Skull giver@popplesburger.hilciferous.nl
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        7 days ago

        I agree and I personally think the whole preemptive Threads ban is stupid in general, but at least one major bridge has had to be turned off because people on the Mastodon/ActivityPub side of things got angry. I don’t mean the people behind ActivityPub of course, I’m sure they were chuffed their protocol got buy-in from a major player.

        If anything, large corporations using open standards is better, even in situations like Google Talk where Facebook and Google dominated the protocol for a while; at least the protocol is useful for regular people.

    • ProdigalFrog@slrpnk.net
      link
      fedilink
      English
      arrow-up
      2
      ·
      7 days ago

      The Bluesky firehose throughput is massive and any home ActivityPub instance that tried to enter the network would easily be overwhelmed just loading the basic home page feed.

      AKAIK, activitypub (on mastodon) only requests and receives content from individual users that have been followed by someone on the local instance, it wouldn’t load all of bluesky at once, it would just need to have an up to date database of bluesky’s users so they are easily searchable. With that model, even crappy PC’s can interact with the mega servers.

      Plus, many ActivityPub folks don’t want to federate with big companies anyway.

      With the OP’s point of ATProto being open-source, I assume the thrust of the argument is that at done point there would be a community hosted instance, which were it compatible, I think most activitypub se rvers would gladly federate with.

      I don’t think ActivityPub is made for large servers

      Ideally there doesn’t need to be any, as the conglomeration of all smaller instances should be able to act as a large server. Unfortunately as it currently stands, the UI of most fediverse software makes interacting with that wider pool more difficult than it needs to be, and thus punishes smaller Mastodon servers with more difficult discovery of interesting topics or people to follow. But I think that can be overcome simply with better UI design.

      AP works well for following friends and family, it’s kind of terrible for the tailored topic based social media feed most people want out of social media apps these days.

      Again, I think that’s a UI problem. I don’t use mastodon myself because of it, as I find it difficult to find people that interest me. However, Lemmy’s use of Topics, and more critically, the existence of Lemmyverse.net which searches across all instances, make finding interesting things possible regardless of the size of your home instance. It’s criminal that that functionality is not a native feature in the standard lemmy Ui, and I’m not aware of anything similar for mastodon.

        • Kichae@lemmy.ca
          link
          fedilink
          English
          arrow-up
          2
          ·
          7 days ago

          Yes, but that’s how you end up with the “I don’t have anyone to follow” situation that people left Mastodon for during the first wave of the Twitter collapse.

          The vast majority of people landed on the largest severs, where there was a ton of chatter in both the Local and Global feeds. They couldn’t find anyone because they were accustomed to using search to find connections, and Mastodon’s search is so tightly locked down that it’s borderline impossible to find who or what you’re looking for. The idea of checking other feeds didn’t even seem to occur to many people – something that I, as an avid “what’s that button do?” user, find totally bizarre, but seems to be rather standard for most people interacting with new things.

          If the default view had been Local or something, the story could have been very different.

          • Skull giver@popplesburger.hilciferous.nl
            link
            fedilink
            English
            arrow-up
            2
            ·
            7 days ago

            The problems that plagues Mastodon at the time have all been fixed as far as I know, but it’s too late now. Other, more difficult problems remain, like the inconsistencies between server on how many likes/comments a post has and the inevitable perception that you need to create an account on every server to follow people because the follow button doesn’t work by itself even if you’re logged into your account in another tab.

            People don’t join a social media platform to go on an adventure and see what every button does. They came looking for a new Twitter rather than a new experience and Mastodon, and kind of still is, a bad Twitter. It’s a great Mastodon, but that’s just not what most people were after.