This is a follow-up from my previous thread.

The thread discussed the question of why people tend to choose proprietary microblogging platfroms (i.e. Bluesky or Threads) over the free and open source microblogging platform, Mastodon.

The reasons, summarised by @[email protected] are:

  1. marketing
  2. not having to pick the instance when registering
  3. people who have experienced Mastodon’s hermetic culture discouraging others from joining
  4. algorithms helping discover people and content to follow
  5. marketing

and I’m saying that as a firm Mastodon user and believer.

Now that we know why people move to proprietary microblogging platforms, we can also produce methods to counter this.

How do we get “normies” to adopt the Fediverse?

  • distant plant@microblog.lakora.us
    link
    fedilink
    arrow-up
    1
    ·
    3 months ago

    I’d like less focus on the network and more on individual servers, with their own names, policies, and reputations. Then users aren’t thinking about whether to join one huge network - they’re thinking about whether that server is the kind of place they want to be. (https://wandering.shop is a good example of an instance that is explicitly going for certain vibes.)

    It would allow individual pre-existing communities to create their own spaces, ones which would prioritize those communities’ experiences and needs over their connection to the rest of the fediverse. I’m imagining something like Dreamwidth or Fur Affinity or the many old-fashioned forums out there, just with the ability to follow users or navigate to topics on other instances if you know their names or URLs. I’m really not worried about discoverability outside the instance - to me, the instance is the platform, and anything outside of it is just an additional thing I can get to if I want it.

    That being said, I think this approach is probably incompatible with trying to create a general-purpose social media site that also attracts a large number of users, at least not without a hefty marketing budget.

    @[email protected] @[email protected]