Personally, I want nothing to do with them and I’m not willing to give them the benefit of the doubt. I moved to the Fediverse to get away from all these corpos.

  • Jure Repinc@lemmy.ml
    link
    fedilink
    arrow-up
    14
    arrow-down
    1
    ·
    edit-2
    1 year ago

    Judging from their past and all the bad actions they have done in the past, bad for democracy, privacy, minorities and marginalised people and how openly they have a far/extreme-right bias. Well I feel extremely negative about them joining in. They were also part of destruction of another open/federated protocol in the past: they played big part in destroying XMPP/Jabber messaging. So I am afraid they will do their usual embrace, extend, and extinguish thing and their surveillance capitalist thing and yeah. no good. Best to block their instances outright.

  • JoeKrogan@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    They will datamine all federated users They will set up a CDN for uploads on their platform that will track you like v.meta.com or i.meta.com.

    They will probably train LLMs off the data. They will sell the data to advertisers or data brokers. They will most likely have ads or pay to boost.

    They will diverge from the standard once they have the majority of users like google does with chrome and the web.

    • duncesplayed@lemmy.one
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      They will set up a CDN for uploads on their platform that will track you like v.meta.com or i.meta.com.

      This is the only thing they couldn’t already do. They’ve probably already been datamining Fediverse users. No need to set up an instance for that.

      I agree with the v.meta.com and i.meta.com. We’ll have to establish some good alternatives by then so people don’t use them just because they work so well.

  • reksas@sopuli.xyz
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    we shouldnt let them in. they would have done decentralized service years ago if there was money in it for them. They either want us to stop or try to seize control in only way that can -> by worming in.

    We must have zero-tolerance for corporations or we might as well just give up.

  • WolfhoundRO@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    They’re trojan horse. We can’t stop them from creating their own servers, but we can choose to defederate them. Up with the Anti-Meta Defederation Pact

  • ataraxia937@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Even if they were somehow not evil, the sheer volume would technologically destroy any instance that tried to federate with them.

  • Zuberi@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I say we just don’t allow them on most kbin/lemmy instances. Let the people decide what info is bullshit or not.

  • ren (a they/them)@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Facebook et al has had a horrible track record of creating a new app/service and getting people on board. Their 3 successes are Facebook, Whatsapp (bought), and IG (bought). Every time they’ve launched an app outside of these, they failed (IGTV anyone?).

    The Fediverse is open.

    They can create Threads on activity pub and hope that they can create a server that competes with Twitter. Go for it, who cares. You can choose to follow people there or not, or join or not, or be on a server that defederates from it or not.

    That’s the beauty of it.

    Meta’s userbase is diverse. It has good and bad players. No need to broadstrokes it. If people join the Fediverse via Threads, many will discover Mastodon, Lemmy, Kbin, Calckey etc over time. Discovery & community!

    So, like… in conclusion or whatever… everyone needs to chill. IMO.

  • averagedrunk@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    It’s an easy fix. If an instance you’re a part of federates with them then just move to a new instance.

    Hopefully this will put instance blocking on the top of the list.