• merlin@open-source.social
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    I’m new to the whole fediverse thing, so how would you create a barrier to entry apart from individual instances not federating with instances they see as abusive?

    • ImaginaryFox@kbin.social
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      1 year ago

      Signing up for threads is a lot easier than it is to sign up for usual lemmy or kbin instances. If they have an Instagram account then it’s already automated.

      If they want to interact here they’d have to create an account for a place like this instead of being able to use their thread account. Which is probably what is meant by barrier to entry. They can’t go and use their meta instance. I’m assuming they can’t view content from the equivalent of their all, and would have to view it by going directly to the link. So just stuck in lurker mode.

      • merlin@open-source.social
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Gotcha. I’ve just now seen that threads doesn’t support activitypub. I thought that the entire idea was to integrate with platforms like these, but oh well what did I expect :D

        Still curious to see if they actually implement it and how it’s going to turn out for them.

    • PabloDiscobar@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      The barrier is picking a tool, then picking an instance, then accepting that the crowd is somewhere else. threads makes this automatic for you. Even “knowing” that there is another tool is a barrier.