𝕯𝖎𝖕𝖘𝖍𝖎𝖙

Troll honeypot, apparently.

Suggested blocks:

  • @lemm.ee:
    • @ByteWizard (troll)
    • @Texas_Hangover (troll)
  • @lemmy.world:
    • @neflubaguzzi (troll)
    • @fkn (troll mod)
    • @jopepa (troll)
    • @yggstyle
    • @EdibleFriend (troll)
  • @lemmy.blahaj.zone:
    • @nublug (troll)
    • @StoneGender (troll)
  • 0 Posts
  • 5 Comments
Joined 1 year ago
cake
Cake day: August 2nd, 2023

help-circle



  • AFAIK, Meta cannot modify algorithms in lemmy code / created in networks inside lemmy instances (if that’s s thing) unless meta starts running those instances themselves. No doubt, using meta’s instance and client will let meta do what it wants to do.

    I think the harder problem here is meta isn’t a curated collection of 300+ instances we can block when we don’t like the instance (e.g., instances != facebook communities). Meta is just going to come online with a large instance with millions of users. It’s kind of hard to judge all of meta users at once, as an instance provider. So, I guess instances who don’t want meta, don’t get meta. Fair.

    I agree with all the misconceptions you’ve cleared up, and you’ve also made a great case for why people would want to join a smaller private instance instead of facebook. I guess I just don’t see the present threat to the fediverse with meta (aside from instances being bombarded with trash that needs to be defederated from that instance). There’s absolutely an existential threat, but the beauty of open source is that as long as there are devs willing to work on it, it can still exist - meta cannot buy the current version of lemmy we are all using and prevent it from being run, for example.