this post was submitted on 07 Jul 2023
49 points (76.3% liked)
Lemmy.world Support
3210 readers
2 users here now
Lemmy.world Support
Welcome to the official Lemmy.world Support community! Post your issues or questions about Lemmy.world here.
This community is for issues related to the Lemmy World instance only. For Lemmy software requests or bug reports, please go to the Lemmy github page.
This community is subject to the rules defined here for lemmy.world.
You can also DM https://lemmy.world/u/lwreport or email [email protected] (PGP Supported) if you need to reach our directly to the admin team.
Follow us for server news 🐘
Outages 🔥
https://status.lemmy.world
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That article is FUD. Apple hurt XMPP just as much by never joining it and offering a messaging system within their own ecosystem so folks had no reason to create a second account. XMPP would have been harmed by competition just as much if Google didn't join it. It was competition that killed it. Not that they had joined.
The article isn't FUD. FUD is a propaganda tactic. This is a recounting of events from the perspective of an insider. Just because it may give cause to have uncertainty or doubt or hell, even fear, doesn't mean it is a propaganda piece. And especially knowing how tech giants behave towards any and all competition this is really just a textbook retelling of one of the many events that fall into this same pattern.
It's FUD because it's objectively not the reason XMPP failed.
It may not be the only reason but it surely is a part of the issue. Few articles are going to cover the whole of it.
Google wasn't competing with XMPP and XMPP would still be where it is today without Google's "interference." Google was losing chat market share to Apple and Blackberry. That's why it's history of chat applications is a mess. It kept throwing new stuff at the wall and hoping it stuck. They literally migrated to a new chat application again just a couple years ago.
Plus, it doesn't address this topic at all. If Threads joins the fediverse, they join the fediverse. Defederating them before we even know what will happen or if they'll even affect this instance doesn't help fight this. A bunch of people telling others they need to leave any instance who doesn't confirm will do actively more harm than Threads might possibly maybe do in the future.
I agree we shouldn't be pushing people to leave the instance. I don't think that solves the issue. But I still don't think Meta should be federated with. Both due to their content and exhibited behaviors on their platforms. Extending any invite towards that entity will end poorly.
Describe in any level of detail instead of literal FUD (you're simply using vague notions), what can happen if defederation occurs after seeing what happens instead of before. What cannot be prevented by defederation after the fact. And let's bare in mind Threads' developer already talked about being multi-instance. We don't even know if it will even federate with Lemmy/Kbin for that matter.
You're drumming up fear, uncertainty, and doubt about something that may not even remotely be a problem. We don't need to create some Lemmy version of Fox News here.
You really need to find the difference between holding uncertainty and doubt about a group that has strong evidence against them based on past behavior and the FUD propaganda technique. They are not the same and throwing them around like they are is not productive to this discussion.
You need to explain how what you're doing is any different. You are creating fear, uncertainty, and doubt about an event that 1) may never even occur and 2) you offer no actual evidence anything bad will happen. You can't even articulate what a bad thing might be.