A new project launching today aims to capitalize on the momentum seen within the fediverse, also known as the open social web, which describes interconnected social networking services powered by the ActivityPub protocol. Co-founded by the co-author and current editor of ActivityPub, Evan Prodromou, a new nonprofit organization called the Social Web Foundation will focus on expanding the fediverse, improving ActivityPub and the user experience, informing policymakers, and educating people about the fediverse and how they can participate.

  • MorallyCoffee@lemmy.ml
    link
    fedilink
    arrow-up
    41
    arrow-down
    2
    ·
    1 month ago

    “The fact that Threads has joined the space has made it really interesting for other companies,” Prodromou says. “Threads is bringing a really big audience, as well as big names — like @POTUS is on the fediverse … So that makes this process a lot more interesting for other organizations — both for publishers who want to reach those audiences, as well as for existing social networks who want to have those influencers and celebrities available to their users.”

    So this is just about piggy-backing on Threads, not any real support for the principles of open software.

    • MrSoup@lemmy.zip
      link
      fedilink
      arrow-up
      20
      ·
      1 month ago

      That’s the most famous ActivityPub social just because people don’t know what federation is and that Threads implements it (disabled by default).

      All IRL people who know Threads whom I asked what made Threads different from Twitter didn’t know about this feature.

      • MorallyCoffee@lemmy.ml
        link
        fedilink
        arrow-up
        21
        ·
        1 month ago

        It’s like people can’t get interested in anything unless it has the Big Tech stamp of approval. 🙄

        • floofloof@lemmy.ca
          link
          fedilink
          English
          arrow-up
          12
          ·
          edit-2
          1 month ago

          It’s just about marketing. People don’t know about what they don’t hear about, and the wealthier companies can make sure people hear about them. There’s no budget for that with regular Fediverse sites.

          • refalo@programming.dev
            link
            fedilink
            arrow-up
            4
            arrow-down
            2
            ·
            1 month ago

            People don’t know about what they don’t hear about

            Some people take the initiative to learn things on their own though. I suppose we’re not their target audience however.

          • The Doctor@beehaw.org
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 month ago

            And make sure they hear about it in such a way that it seems interesting. The fediverse doesn’t use any basic marketing plan techniques, and enough people are conditioned to them (after a lifetime of growing up surrounded by advertising on television and in their spaces) that anything which doesn’t fit that template scoots right by.

        • MrSoup@lemmy.zip
          link
          fedilink
          arrow-up
          9
          ·
          1 month ago

          In their favor I can say that none of them are tech savvy and they got to know Threads just because Meta put Threads links and icons all over Instagram (which those people use).

      • warm@kbin.earth
        link
        fedilink
        arrow-up
        6
        ·
        1 month ago

        Wouldn’t be too bad if they just host threads and abide by ActivityPub without getting hands on, but they clearly want to shape it how they want.

        • Dizzy Devil Ducky@lemm.ee
          link
          fedilink
          English
          arrow-up
          4
          ·
          1 month ago

          I have a feeling this could very well end up in similar fashion to g*gle talk and IRC. Let’s hope it doesn’t, but I don’t have enough faith in large companies not trying to completely destroy the Fediverse for profit.

    • oxjox@lemmy.ml
      link
      fedilink
      English
      arrow-up
      7
      ·
      1 month ago

      I would like to see more investment in informative media. Social media has been one of the best sources to get information about local events, news, and alerts.

      Speaking from an American’s perspective, I would like to see federated networks organized similarly to the United States. There should be one main federal instance, then a sub instance for states, eventually down to micro instances for neighborhoods or zip codes.

      My complaint about “corporate social media” has been its need to make money from advertising driven by engagement. This means I miss tons of posted information by family, friends, businesses, bands, restaurants, record shops, farmers markets, city council members, police departments, reporters, etc.

      I still want to connect with these users but getting them on board with the fediverse is an uphill battle if they’re only in it for the memes. Creating a platform that makes some tangible sense to people, I think, would drive more adoption. If you want to connect with your city, join cityname.state.US.verse. This wouldn’t exclude the creation of other networks like I dunno… nestle.corp.verse or tiktok.social.verse.

  • refalo@programming.dev
    link
    fedilink
    arrow-up
    3
    ·
    1 month ago

    I’m really surprised servers have not started by default limiting and/or vetting who can federate with them. I know many Lemmy instances block many other instances from federating with them, but only after learning about what a lot of their content is. To me this practice kinda creates a very fragmented “which wind would you like to piss into” problem.

      • The Doctor@beehaw.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        Google pulled it off with GChat. All told, those of us who run our own XMPP servers aren’t even a rounding error when compared to everybody who uses Google Chat, FB Chat, Slack…

        Interoperate with it. Add proprietary extensions faster than other implementations can keep up with (at least two orders of mag). Render software that isn’t yours unusable by suddenly cutting over to something else internally; let connection attempts continue for a while to frustrate users while simultaneously releasing your own. Then cut away all points where legacy connection attempts could be done.