![User's banner](/_next/image?url=https%3A%2F%2Flem.monster%2Fpictrs%2Fimage%2F85fcaa86-845c-4b27-b9ec-0e26b144db56.jpeg&w=2048&q=75)
![Avatar](/_next/image?url=https%3A%2F%2Flem.monster%2Fpictrs%2Fimage%2Fa7a0071d-1c14-4eeb-901f-9c26935bf517.png&w=3840&q=75)
![Avatar](/_next/image?url=%2Flemmy-icon-96x96.webp&w=3840&q=75)
Bilb!
All things are possible through Christ!
[https://clickhole.com/the-ability-to-play-as-bowser-has-made-our-society-more-1825123963/](Bowser Culture) strikes again
It doesn’t seem at all plausible to me that meta threads will pull users away from mastodon/pleroma/misskey/etc. though. If they “extend” the federation protocol to the point they become incompatible with the rest of these implementations, they will just go away and we’re back to where we were before they started federating.
For what it’s worth, I agree with your reading, and nobody has described what I consider to be a plausible scenario for how exactly “embrace, extend, extinguish” would actually work here.
I don’t think Meta should be given the benefit of the doubt or anything and people may have differing opinions about the likely user base for Threads, but I don’t think this is any real concern to the fediverse in general.
If you think the aforementioned celebrities/influencers/news orgs/etc. are going to choose the fediverse instead of Threads or (I think more likely) BlueSky, that might make sense. I don’t see that happening though. What might instead happen is something like this:
Potential fediverse user: “I heard that Facebook’s new twitter competitor can work with these existing sites. So I can make an account on one of those and follow Celebrity X and Politician Y without making a Meta account.”
Potential fediverse admin: “Well yeah, but you can’t follow them from my instance. Or any of these other instances. You see, back in the 90s there was this concept called embrace, extend extinguish…”
No longer a potential fediverse user: “Oh, I guess I’ll just make a Meta/Bluesky account instead then.”
Hiding threads is a recently added feature in the wefwef client, and I agree that it should be added to lemmy-ui. I think this would be the relevant issue: https://github.com/LemmyNet/lemmy-ui/issues/384