Should sh.itjust.works preemptively defederate from Threads?

Threads is the not-so-new reddit-like twitter-like public forum platform by Meta, the same commercial company behind internet behemoths like Facebook, Instagram and Whatsapp. They’re working on ActivityPub integration so that they can bridge (federate?) with the fediverse. As far as I know, the focus is on Mastodon instances, but in the future that could include Lemmy instances too.

Some have raised the question, worried about the future of the fediverse or even claiming that it goes against its definition.

What do you think should be done?

EDIT: correction

EDIT.2: The Vote is on! Go make your voice heard. You have until Friday the 29th.

Fediverse instances’ status on federation with Threads

  • ruplicantOP
    link
    fedilink
    arrow-up
    12
    ·
    edit-2
    1 year ago

    What do you see as the risks to the larger fediverse in having Meta federated?

    for me the main risk would be the loss of freedom, as in the open way it is developed. if threads is openly weaved to the fediverse, their closed development methodology will dictate it’s future by virtue of its monopoly and the way for that future will not be defined by the interests of the larger community - as it generally is now with the fediverse’s platforms and apps open standards

    a second important risk is the quality of the conversation will likely drop abruplty. the dominance of the userbase will be too big too fast. i’d like for e.g. Lemmy to grow and keep on growing (not that i care that much about it) but i think this would not be the way to do it

    What benefit does Meta hope to see?

    the benefit any company seeks with any new product or implementation: to increase it’s bottom-line, AKA money

    how? one way is using everything that’s going on in the fediverse as ‘content’ for their users - who they’d be “milking” for said bottom-line. and that content’s upkeep, that would bring them said profit, would not cost them a thing

    EDIT: grammar