Comment on

• TheTomas@social.toot9.de ⁨4⁩ ⁨weeks⁩ ago

  @atomicpoet @fediversenews Well. try to switch instances from Mastodon to Threads and see. And as far as I know in Threads you cannot see answers from Mastodon or other federated services. There is aswell a 5 Min-Grace-Period time until posts are pushed to Fediverse and many more minor and major issues.

  source

  • rachel@norfolk.social ⁨4⁩ ⁨weeks⁩ ago

    @TheTomas @atomicpoet @fediversenews that there are issues to resolve in a brand new service isn’t exactly surprising. That doesn’t mean they are not part of the Fediverse

    source
  • maegul@hachyderm.io ⁨4⁩ ⁨weeks⁩ ago

    @TheTomas @atomicpoet @fediversenews

    What's interesting to me, as someone who's generally critical of the state of the fedi, is that I think atomicpoet is right, it is a part of the fediverse, but I think TheTomas's general point is also important, which is whether there should be a base threshold of inter-functionality to be considered a part of the fediverse.

    Because merely receiving posts isn't far beyond RSS and the fedi, AFAICT, likes to (& should) think of itself as more than that too.

    source

    • TheTomas@social.toot9.de ⁨4⁩ ⁨weeks⁩ ago

      @maegul @atomicpoet @fediversenews

      The answer is simple: ActivityPub. How is the current state of Meta in supporting this W3C Standard?

      source
    • TheTomas@social.toot9.de ⁨4⁩ ⁨weeks⁩ ago

      @maegul @atomicpoet @fediversenews

      I guess I represent a generation that experienced Microsofts' EEE very well in the 90ies. Threads is nothing like that. With it's mass of Mio accounts I consider Thread as a threat.

      https://de.wikipedia.org/wiki/Embrace,_Extend_and_Extinguish

      source

      • mikedev@fediversity.site ⁨4⁩ ⁨weeks⁩ ago

        The important thing is that people have the ability to federate (or not) with whomever they want. Having that choice is a giant step from not having any choice. I'm a browser war veteran and I'm treating Threads with caution -- and always have a plan 'B'. Incidentally I developed this plan 'B' because of EEE tactics pursued by Mastodon, not Meta.
        
        Fighting a closed community by closing your community means they've already won. I've been working on the fediverse a very long time. We have weapons and tactics you aren't even aware of.
        
        Cheers.

        source
      • atomicpoet@atomicpoet.org ⁨4⁩ ⁨weeks⁩ ago

        @TheTomas @maegul @fediversenews I hate Outlook and think it’s from the bowels of hell. And yet, I would never say it has nothing to do with email. I doubt you would say otherwise either.

        source
    • atomicpoet@atomicpoet.org ⁨4⁩ ⁨weeks⁩ ago

      @maegul @TheTomas @fediversenews Threads ain’t glorified RSS either because Threads users count likes and boosts from the rest of the Fediverse.

      Comments to Threads isn’t being received yet, but we already know that’s coming.

      Now I don’t believe that any software should be obligated to receive comments – and I’ve believed that even before Threads joined the Fediverse. One of my consistent complaints about the Fediverse has been lack of comment controls, and how it’s near-impossible to reject replies. So far, the only server software that has good comment controls is Streams by @mikedev. Almost all other software doesn’t even have it as an option.

      To me, the one and only base threshold of inter-functionality is some sort of adoption federation, preferably ActivityPub. But even ActivityPub is negotiable to me.

      source
  • atomicpoet@atomicpoet.org ⁨4⁩ ⁨weeks⁩ ago

    @TheTomas @fediversenews Why would I switch instances from Mastodon when I’m not on Mastodon?

    Regarding responses from Mastodon to Threads, we already know that federation with Threads is in beta, and that functionality is coming later. Nevertheless, not a dealbreaker for me.

    As for a 5 minute grace period, so what? There’s lots of “minor and major issues” with all Fediverse software, including Mastodon.

    source