MaiionChat Instance Update & Stance on Meta's Threads.net

Knowing that "Facebook Admits It Was Used to Incite Violence", "Facebook Spreads Fake News Faster Than Any Other Social Website", and that at least "10 Other Facebook Experiments On Users" were conducted, MaiionChat will block Threads due to the company's history violating MaiionChat's instance rules 3 and 5. We are here because we are trying to make and support something better.

In addition to the reasons above, privacy is very important to us here. We believe that Facebook/Meta, Instagram, and now Threads among other tech giants, have questionable privacy practices. In light of the permissions requested by Facebook discussed from this post and the personal data that may be collected by Threads, MaiionChat believes there is sufficient information available to deduce that Threads plans to violate instance rule 2. As far as this article is concerned, an "invasion of privacy" can be classified as a type of harassment.

On another point, we believe there is good reason to be concerned about the harms Embrace, extend, and extinguish could do to the Fediverse. Threads is currently on the Embrace stage:

“Soon, you’ll be able to follow and interact with people on other fediverse platforms, such as Mastodon. They can also find people on Threads using full usernames, such as @mosseri@threads.net.” Mosseri also noted that the team building Threads wasn’t able to complete the work to support fediverse at launch. “We’re committed to building support for ActivityPub, the protocol behind Mastodon, into this app. We weren’t able to finish it for launch given a number of complications that come along with a decentralized network, but it’s coming,” he said. -Source

To conclude before this gets any longer, MaiionChat will join the list of Lemmy and Mastodon instances blocking Threads.


On a more personal note, I would like to thank the Lemmy developers and contributors for making all of this possible. I wish to report that this instance is now running on v0.18.1. Details of this release can be found here: https://github.com/LemmyNet/lemmy/releases. I would also like to apologize for the down time earlier this afternoon if it interfered with anyone using this instance.