#metameta — Public Fediverse posts on home.social

J’aime, je n’aime pas. Roland Barthes, the French sociologist famously listed his likes and dislikes then discussed how pointless they are to anyone else.

He writes: “Here begins the intimidation of the body, which obliges others to endure me liberally, to remain silent and polite confronted by pleasures or rejections which they do not share.”

Some of mine.
I don’t like: crowds, emojis (but I gave in), finding dead mice in the library (even with garnish) …

I like: lemons, cappuccino, croissant on Saturdays, moss en masse, peonies, lupin, clouds on a sunny day, rain that bounces off the ground, hiking in new snow, air so crisp you can see your breath, notes typed on a manual typewriter, fact checking, habaneros, midnight, black pencil doodles, plain text editors, Snøhetta designs, Amanda Gorman, Mini Coopers, cats, Khatia Buniatishvili at a piano, and 김진산 (Jinsan Kim) on acoustic guitar.

Roland Barthes’:
“I don’t like: white Pomeranians …”

#july #quotes #rolandbarthesquote #jeaime #metameta #lists

Christine Sætre-esque @csaetre · 2025-06-29 · 14:13 UTC

J’aime, je n’aime pas. Roland Barthes, the French sociologist famously listed his likes and dislikes then discussed how pointless they are to anyone else.

He writes: “Here begins the intimidation of the body, which obliges others to endure me liberally, to remain silent and polite confronted by pleasures or rejections which they do not share.”

Some of mine.
I don’t like: crowds, emojis (but I gave in), finding dead mice in the library (even with garnish) …

I like: lemons, cappuccino, croissant on Saturdays, moss en masse, peonies, lupin, clouds on a sunny day, rain that bounces off the ground, hiking in new snow, air so crisp you can see your breath, notes typed on a manual typewriter, fact checking, habaneros, midnight, black pencil doodles, plain text editors, Snøhetta designs, Amanda Gorman, Mini Coopers, cats, Khatia Buniatishvili at a piano, and 김진산 (Jinsan Kim) on acoustic guitar.

Roland Barthes’:
“I don’t like: white Pomeranians …”

#july #quotes #rolandbarthesquote #jeaime #metameta #lists

#metameta #lists #july #quotes #rolandbarthesquote #jeaime

Jupiter Rowland @[email protected] · 2024-01-27 · 09:37 UTC

@haagch

"Walled garden metaverse" sounds like an oxymoron. If it runs entirely on the servers of one company and has no public API or any way to interact with users from outside a proprietary ecosystem, then what's really "metaverse" about it?

Well, everyone and their dog believes that Zuckerberg's virtual worlds platform is officially named "The Metaverse". ("Metaverse" and "The Metaverse" are registered trademarks of Meta Platforms, Inc. All rights reserved.") And both mainstream media and tech media spew out the same non-sense. The only exceptions are tech media specialising in virtual worlds.

Also, as I've already written, Second Life started to officially refer to itself as a "metaverse" in 2022 as a "Hey, we're still here, too, and we're still relevant" publicity stunt. And Second Life has always been a commercial walled garden.

Its API is only public insofar as it was reverse-engineered from the source code of the official viewer after the latter was made open-source in 2006. And that's only a viewer API, a client API, that's used to develop third-party viewers. "Compatibility" with other virtual worlds? Well, there's OpenSim which was then built against the other side of the same API and the already existing third-party Second Life viewers and launched in 2007. But while it uses largely the same API and the same formats and the same standards, and while it's decentralised and federated within itself, it can't connect to Second Life. Even the 2008 "Six Lindens manage to teleport from Second Life to OpenSim" publicity stunt was bogus and faked.

I think I might write an article about the latter.

#Long #LongPost #CWLong #CWLongPost #VirtualWorlds #Meta #MetaMeta #Horizons #Secondlife #Metaverse

#virtualworlds #cwlongpost #secondlife #metaverse #longpost #metameta

Jupiter Rowland @[email protected] · 2024-01-27 · 09:37 UTC

@haagch

"Walled garden metaverse" sounds like an oxymoron. If it runs entirely on the servers of one company and has no public API or any way to interact with users from outside a proprietary ecosystem, then what's really "metaverse" about it?

Well, everyone and their dog believes that Zuckerberg's virtual worlds platform is officially named "The Metaverse". ("Metaverse" and "The Metaverse" are registered trademarks of Meta Platforms, Inc. All rights reserved.") And both mainstream media and tech media spew out the same non-sense. The only exceptions are tech media specialising in virtual worlds.

Also, as I've already written, Second Life started to officially refer to itself as a "metaverse" in 2022 as a "Hey, we're still here, too, and we're still relevant" publicity stunt. And Second Life has always been a commercial walled garden.

Its API is only public insofar as it was reverse-engineered from the source code of the official viewer after the latter was made open-source in 2006. And that's only a viewer API, a client API, that's used to develop third-party viewers. "Compatibility" with other virtual worlds? Well, there's OpenSim which was then built against the other side of the same API and the already existing third-party Second Life viewers and launched in 2007. But while it uses largely the same API and the same formats and the same standards, and while it's decentralised and federated within itself, it can't connect to Second Life. Even the 2008 "Six Lindens manage to teleport from Second Life to OpenSim" publicity stunt was bogus and faked.

I think I might write an article about the latter.

#Long #LongPost #CWLong #CWLongPost #VirtualWorlds #Meta #MetaMeta #Horizons #Secondlife #Metaverse

#virtualworlds #cwlongpost #secondlife #metaverse #longpost #metameta

Jupiter Rowland @[email protected] · 2024-01-26 · 23:19 UTC

CW: An incomplete but quite representative list of metaverses; CW: long (over 2,500 characters), mild swearing, Meta/Facebook project mentioned

"The Metaverse". Actually named Horizons. Get that into your heads, dammit. And yes, I'm talking about Meta's worlds.
Cryptobros' attempted get-rich-quick schemes that imply that "the Metaverse" inevitably requires a blockchain, a cryptocurrency (usually either Dogecoin or Etherium or something running on Etherium's blockchain) and expensive NFTs for everything including land. Not seldomly buggy as hell because in-world experience doesn't earn the world owners any money.
More or less failed attempts by other huge gigacorporations to launch their own monolithic walled garden metaverses for as many use-cases as imaginable. Failed because they came too late.
The industrial metaverse which is still only a vague idea and probably another buzzword like "the cloud" and "the blockchain".
Second Life which has slapped the term "metaverse" onto itself in 2022, trying to stay relevant in spite of stagnating user numbers and showing the world it's still around. This actually had even less of an effect than the comparisons between Horizons' simplistic avatars and Second Life's near-photo-realistic avatars and its 20th birthday PR campaign last year.
Roblox, VRchat, Minecraft etc. They don't even need to refer to themselves as "metaverses" because they're so popular with kids that not much more publicity is necessary.
OpenSimulator which is as decentralised as Decentraland implies to be but isn't. It has been using the term "metaverse" regularly since 2007, the year it was launched. But as it doesn't make a fuss about it, nobody outside its own community knows.
ThirdRoom which was one of the first FLOSS virtual worlds to work in a standard Web browser rather than requiring a specialised client. Its future is unclear because all three devs are on an indefinite hiatus.
Vircadia, a HighFidelity fork, and Overte, a Vircadia fork, both trying to build the decentralised next-generation open-source metaverses with some interesting ideas, but neither having a significant community, and both being every bit as obscure and unknown as OpenSim.
The proposed decentralised, standardised, open metaverse for everyone. Which might not even come because the virtual worlds hype of 2020 is over for obvious reasons, and whoever else would be interested in it is probably busy in other virtual worlds already.

#Long #LongPost #CWLong #CWLongPost #VirtualWorlds #Meta #MetaMeta #Horizons #SecondLife #OpenSimulator #Decentraland #Roblox #VRchat #ThirdRoom #Vircadia #Overte #TheMetaverse #Metaverse

#virtualworlds #opensimulator #decentraland #themetaverse #cwlongpost #secondlife

Jupiter Rowland @[email protected] · 2024-01-26 · 23:19 UTC

CW: An incomplete but quite representative list of metaverses; CW: long (over 2,500 characters), mild swearing, Meta/Facebook project mentioned

"The Metaverse". Actually named Horizons. Get that into your heads, dammit. And yes, I'm talking about Meta's worlds.
Cryptobros' attempted get-rich-quick schemes that imply that "the Metaverse" inevitably requires a blockchain, a cryptocurrency (usually either Dogecoin or Etherium or something running on Etherium's blockchain) and expensive NFTs for everything including land. Not seldomly buggy as hell because in-world experience doesn't earn the world owners any money.
More or less failed attempts by other huge gigacorporations to launch their own monolithic walled garden metaverses for as many use-cases as imaginable. Failed because they came too late.
The industrial metaverse which is still only a vague idea and probably another buzzword like "the cloud" and "the blockchain".
Second Life which has slapped the term "metaverse" onto itself in 2022, trying to stay relevant in spite of stagnating user numbers and showing the world it's still around. This actually had even less of an effect than the comparisons between Horizons' simplistic avatars and Second Life's near-photo-realistic avatars and its 20th birthday PR campaign last year.
Roblox, VRchat, Minecraft etc. They don't even need to refer to themselves as "metaverses" because they're so popular with kids that not much more publicity is necessary.
OpenSimulator which is as decentralised as Decentraland implies to be but isn't. It has been using the term "metaverse" regularly since 2007, the year it was launched. But as it doesn't make a fuss about it, nobody outside its own community knows.
ThirdRoom which was one of the first FLOSS virtual worlds to work in a standard Web browser rather than requiring a specialised client. Its future is unclear because all three devs are on an indefinite hiatus.
Vircadia, a HighFidelity fork, and Overte, a Vircadia fork, both trying to build the decentralised next-generation open-source metaverses with some interesting ideas, but neither having a significant community, and both being every bit as obscure and unknown as OpenSim.
The proposed decentralised, standardised, open metaverse for everyone. Which might not even come because the virtual worlds hype of 2020 is over for obvious reasons, and whoever else would be interested in it is probably busy in other virtual worlds already.

#Long #LongPost #CWLong #CWLongPost #VirtualWorlds #Meta #MetaMeta #Horizons #SecondLife #OpenSimulator #Decentraland #Roblox #VRchat #ThirdRoom #Vircadia #Overte #TheMetaverse #Metaverse

#virtualworlds #opensimulator #decentraland #themetaverse #cwlongpost #secondlife

Jupiter Rowland @[email protected] · 2023-12-27 · 08:35 UTC

@Vijay Prema A large part of this is EU politics.

Meta wanted to harvest as many former Twitter users as possible, that's the reason why Threads exists.

The reason why Threads has implemented ActivityPub is mainly EU politics and EU laws. In America, IT corporations have free reign. But the EU requires at least newly-started online services to be interoperable with others, full stop, end of discussion.

When Threads was launched, it was completely banned in the EU. Totally inaccessible. You know when the ban was lifted? It was lifted when Threads started federating. Even with that little federation, Threads sufficiently fulfilled the requirements to operate in the EU. For now.

And why the Fediverse? Why ActivityPub? Because a) established with lots of users already, b) open standard with no license fees to pay, c) not controlled by another corporation, and d) they had heard of it.

I mean, they could just as well have implemented Bluesky's protocol, but Bluesky is corporate and doesn't want to federate with anything non-Bluesky. They could have implemented the Diaspora* protocol, but Diaspora* isn't interested in external federation either, so they'd have to crack and reverse-enginner Diaspora*'s inner workings just like Friendica did a dozen years ago. They could have implemented OStatus, but hardly anybody uses that anymore. They could have implemented Zot or Nomad, but they don't know that either exists, not to mention that they would have had to bow to the will of one individual protocol developer who would not let them one-sidedly meddle with his protocol against his will.

That's why ActivityPub.

#Long #LongPost #CWLong #CWLongPost #Meta #CWMeta #Threads #MetaMeta #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #EUPol #CWEUPol

#cwfediversemeta #fediversemeta #cwlongpost #cwfedimeta #longpost #metameta

Jupiter Rowland @[email protected] · 2023-12-27 · 08:35 UTC

@Vijay Prema A large part of this is EU politics.

Meta wanted to harvest as many former Twitter users as possible, that's the reason why Threads exists.

The reason why Threads has implemented ActivityPub is mainly EU politics and EU laws. In America, IT corporations have free reign. But the EU requires at least newly-started online services to be interoperable with others, full stop, end of discussion.

When Threads was launched, it was completely banned in the EU. Totally inaccessible. You know when the ban was lifted? It was lifted when Threads started federating. Even with that little federation, Threads sufficiently fulfilled the requirements to operate in the EU. For now.

And why the Fediverse? Why ActivityPub? Because a) established with lots of users already, b) open standard with no license fees to pay, c) not controlled by another corporation, and d) they had heard of it.

I mean, they could just as well have implemented Bluesky's protocol, but Bluesky is corporate and doesn't want to federate with anything non-Bluesky. They could have implemented the Diaspora* protocol, but Diaspora* isn't interested in external federation either, so they'd have to crack and reverse-enginner Diaspora*'s inner workings just like Friendica did a dozen years ago. They could have implemented OStatus, but hardly anybody uses that anymore. They could have implemented Zot or Nomad, but they don't know that either exists, not to mention that they would have had to bow to the will of one individual protocol developer who would not let them one-sidedly meddle with his protocol against his will.

That's why ActivityPub.

#Long #LongPost #CWLong #CWLongPost #Meta #CWMeta #Threads #MetaMeta #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #EUPol #CWEUPol

#cwfediversemeta #fediversemeta #cwlongpost #cwfedimeta #longpost #metameta

Jupiter Rowland @[email protected] · 2023-12-26 · 15:08 UTC

@Alexandradal @eatyourglory @JoeA They can't completely redesign ActivityPub so that it becomes incompatible what we have now and then a) still call it ActivityPub and b) declare it the "official" version.

Meta doesn't own ActivityPub. If anyone owns ActivityPub, it's the W3C. Meta can neither buy ActivityPub from the W3C, nor can they buy out the W3C.

If Meta makes its own proprietary version of ActivityPub and implements it on Threads, then Threads becomes incompatible with the rest of the Fediverse. And the rest of the Fediverse will shrug it off, although I'm not so sure about Mastodon.

The very reason why Threads uses ActivityPub is because the EU demands interoperability between online platforms. ActivityPub was the easiest way for Meta to do that with Threads without implementing something owned by another corporation. It's all EU appeasement. If Threads becomes incompatible with the rest of the Fediverse, it becomes a centralised walled garden, and all the EU will ban Threads again.

#Long #LongPost #CWLong #CWLongPost #Meta #MetaMeta #Threads #Fediverse #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #EUPol #CWEUPol

#cwfediversemeta #fediversemeta #cwlongpost #cwfedimeta #fediverse #longpost

Jupiter Rowland @[email protected] · 2023-12-26 · 15:08 UTC

@Alexandradal @eatyourglory @JoeA They can't completely redesign ActivityPub so that it becomes incompatible what we have now and then a) still call it ActivityPub and b) declare it the "official" version.

Meta doesn't own ActivityPub. If anyone owns ActivityPub, it's the W3C. Meta can neither buy ActivityPub from the W3C, nor can they buy out the W3C.

If Meta makes its own proprietary version of ActivityPub and implements it on Threads, then Threads becomes incompatible with the rest of the Fediverse. And the rest of the Fediverse will shrug it off, although I'm not so sure about Mastodon.

The very reason why Threads uses ActivityPub is because the EU demands interoperability between online platforms. ActivityPub was the easiest way for Meta to do that with Threads without implementing something owned by another corporation. It's all EU appeasement. If Threads becomes incompatible with the rest of the Fediverse, it becomes a centralised walled garden, and all the EU will ban Threads again.

#Long #LongPost #CWLong #CWLongPost #Meta #MetaMeta #Threads #Fediverse #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #EUPol #CWEUPol

#cwfediversemeta #fediversemeta #cwlongpost #cwfedimeta #fediverse #longpost

Jupiter Rowland @[email protected] · 2023-12-26 · 14:11 UTC

CW: Here's why I don't panic about Threads personally; CW: long (over 3,000 characters), Threads, Meta, Fediverse meta, non-Mastodon Fediverse meta

Personally and regarding my Hubzilla channel here, I'm not too worried about Threads.

First of all, I'm not going to connect to anyone on Threads. Not even when more than those select few can be followed. As if there's anything going on there that's of interest within the scope of this channel.

Second, Threads users can't follow anyone outside Threads anyway yet.

Third, even if they could, doesn't mean I'd let them if I don't want to. It's up to me to decide who connects to my channel and who doesn't. I have to confirm each new connection, and if I don't, that actor doesn't receive anything from me.

Fourth, the typical incentive for non-Threads users to follow me isn't there for Threads users.

One of the two main reasons why Mastodon users follow me is because they expect me to explain the Fediverse outside Mastodon to them. Your typical Threads user neither knows nor cares for the Fediverse. They're on Threads because it's "Twitter by Facebook without Musk".

The other and even bigger reason for Mastodon users to follow me is because they've just arrived from 𝕏, and they need some Twitter-like background noise in their personal timelines, so they follow everyone they come across. Threads probably forces loads of background noise upon you right away, so you don't have to take care of that yourself.

Fifth, a channel owned by a virtual world avatar that's primarily about obscure virtual worlds with no real-life information isn't worth data-harvesting. Especially not if I keep badmouthing Horizons and using the term "metaverse" for stuff that's both over a decade older than Horizons and more alive than Horizons because that stuff has been using that word for over a decade itself. Meta would probably rather block this channel before anyone on Threads finds it than harvest it. In fact, I could try to make this process quicker with a few well-placed memes.

Sixth, I can easily silence bad actors on Threads with Superblock.

I was about to ask what the odds are that Threads can federate with Hubzilla in the first place, exotic as Hubzilla is with its ActivityPub support through an optional add-on. But I've got in-bound connections from all over the place already now, from Diaspora* to Misskey to GoToSocial to micro.blog.

Then again, I don't know how Threads handles posts with over 500 characters. After all, it was designed to federate with vanilla Mastodon by people who at that point believed that the Fediverse is only vanilla Mastodon. It could actually be that Threads rejects posts with over 500 characters, just like Misskey and its forks reject posts from a certain length upward.

Finally, if bad came to worse, I wouldn't even have to move away. I could switch ActivityPub off entirely. Granted, that'd mean that I'd lose most of my connections, and I'd have to try and remake those to Friendica using the Diaspora* protocol instead. But that'd completely lock Threads out on a protocol level.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Meta #MetaMeta #Threads

#cwfediversemeta #fediversemeta #cwlongpost #cwfedimeta #fediverse #longpost

Jupiter Rowland @[email protected] · 2023-12-26 · 14:11 UTC

CW: Here's why I don't panic about Threads personally; CW: long (over 3,000 characters), Threads, Meta, Fediverse meta, non-Mastodon Fediverse meta

Personally and regarding my Hubzilla channel here, I'm not too worried about Threads.

First of all, I'm not going to connect to anyone on Threads. Not even when more than those select few can be followed. As if there's anything going on there that's of interest within the scope of this channel.

Second, Threads users can't follow anyone outside Threads anyway yet.

Third, even if they could, doesn't mean I'd let them if I don't want to. It's up to me to decide who connects to my channel and who doesn't. I have to confirm each new connection, and if I don't, that actor doesn't receive anything from me.

Fourth, the typical incentive for non-Threads users to follow me isn't there for Threads users.

One of the two main reasons why Mastodon users follow me is because they expect me to explain the Fediverse outside Mastodon to them. Your typical Threads user neither knows nor cares for the Fediverse. They're on Threads because it's "Twitter by Facebook without Musk".

The other and even bigger reason for Mastodon users to follow me is because they've just arrived from 𝕏, and they need some Twitter-like background noise in their personal timelines, so they follow everyone they come across. Threads probably forces loads of background noise upon you right away, so you don't have to take care of that yourself.

Fifth, a channel owned by a virtual world avatar that's primarily about obscure virtual worlds with no real-life information isn't worth data-harvesting. Especially not if I keep badmouthing Horizons and using the term "metaverse" for stuff that's both over a decade older than Horizons and more alive than Horizons because that stuff has been using that word for over a decade itself. Meta would probably rather block this channel before anyone on Threads finds it than harvest it. In fact, I could try to make this process quicker with a few well-placed memes.

Sixth, I can easily silence bad actors on Threads with Superblock.

I was about to ask what the odds are that Threads can federate with Hubzilla in the first place, exotic as Hubzilla is with its ActivityPub support through an optional add-on. But I've got in-bound connections from all over the place already now, from Diaspora* to Misskey to GoToSocial to micro.blog.

Then again, I don't know how Threads handles posts with over 500 characters. After all, it was designed to federate with vanilla Mastodon by people who at that point believed that the Fediverse is only vanilla Mastodon. It could actually be that Threads rejects posts with over 500 characters, just like Misskey and its forks reject posts from a certain length upward.

Finally, if bad came to worse, I wouldn't even have to move away. I could switch ActivityPub off entirely. Granted, that'd mean that I'd lose most of my connections, and I'd have to try and remake those to Friendica using the Diaspora* protocol instead. But that'd completely lock Threads out on a protocol level.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Meta #MetaMeta #Threads

#cwfediversemeta #fediversemeta #cwlongpost #cwfedimeta #fediverse #longpost

Jupiter Rowland @[email protected] · 2023-12-23 · 09:31 UTC

CW: When Mastodon users try to force their personal preferences upon everyone else; CW: long (1,094 characters), Fediverse meta, Threads meta, Meta meta

What all the discussions about whether or not to block Threads reveals is a very common attitude on Mastodon:

"I want my preference to be the default setting for everybody because having to configure something makes Mastodon too complicated!"

Or even:

"I want my preference to be hard-coded for everybody because adding one more setting makes Mastodon too complicated!"

I guess it isn't rare for either to go along with wanting the whole Fediverse to be either Mastodon proper or exactly like vanilla Mastodon. Maybe even exactly like Mastodon 3.x before certain features that are common everywhere else in the Fediverse were introduced to Mastodon such as full-text search, displaying text formatting or displaying quotes. Because it's so hard to wrap your mind around there being differences between Mastodon on one side and stuff like Firefish, Friendica or Hubzilla on the other side.

#Fediverse #Mastodon #MastodonIsNotTheFediverse #NotOnlyMastodon #Threads #Meta #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #MetaMeta

#mastodonisnotthefediverse #notonlymastodon #cwfediversemeta #fediversemeta #cwlongpost #cwfedimeta

Jupiter Rowland @[email protected] · 2023-12-23 · 09:31 UTC

CW: When Mastodon users try to force their personal preferences upon everyone else; CW: long (1,094 characters), Fediverse meta, Threads meta, Meta meta

What all the discussions about whether or not to block Threads reveals is a very common attitude on Mastodon:

"I want my preference to be the default setting for everybody because having to configure something makes Mastodon too complicated!"

Or even:

"I want my preference to be hard-coded for everybody because adding one more setting makes Mastodon too complicated!"

I guess it isn't rare for either to go along with wanting the whole Fediverse to be either Mastodon proper or exactly like vanilla Mastodon. Maybe even exactly like Mastodon 3.x before certain features that are common everywhere else in the Fediverse were introduced to Mastodon such as full-text search, displaying text formatting or displaying quotes. Because it's so hard to wrap your mind around there being differences between Mastodon on one side and stuff like Firefish, Friendica or Hubzilla on the other side.

#Fediverse #Mastodon #MastodonIsNotTheFediverse #NotOnlyMastodon #Threads #Meta #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #MetaMeta

#mastodonisnotthefediverse #notonlymastodon #cwfediversemeta #fediversemeta #cwlongpost #cwfedimeta

ari :prideified: @[email protected] · 2023-12-15 · 18:30 UTC

Did Your admin click the red button yet?

#meta #metameta #facebook #threads

ari :prideified: @[email protected] · 2023-12-15 · 18:30 UTC

Did Your admin click the red button yet?

#meta #metameta #facebook #threads

Sally Strange @[email protected] · 2023-12-15 · 14:14 UTC

CW: TL:DR: the pro-Threads-federation camp's most common arguments are based on ignorance or lies. Fuck all y'all

My summary of the pro-federation camp's arguments:
-not every FB user is bad
-more is better
-the fediverse could draw people away from threads
-this represents an opportunity for innovation
-porting an account between instances is hard

These aren't unreasonable arguments on the face of it. However, the consistent flaw is that the people presenting these arguments studiously avoid mentioning any of the real reasons the anti-federation camp are opposed, to wit:

-FB's documented history of enabling genocide
-the obvious fact that since they allow e.g. Libs of Tik Tok on Threads, it is already in violation of most "good" instances' terms of service
-FB's documented current practices of abusing workers in lieu of doing actual moderation
-FB's documented history of doing unethical experiments on their users
-FB's documented history of of enabling illegal (in the USA!) racial and religious discrimination

The one thing that the pro-federation camp WILL mention is the concern over EEE (Embrace, Extend, Extinguish), but I've never seen a reasonable explanation for why this is a scenario we shouldn't fear. It's just handwaving.

The pro-federation camp has also repeatedly tried to dishonestly frame the possibility of an admin making an instance block decision with which their users disagree as an example of tyranny. This, I believe, is because "porting instances is hard" is a wack-ass argument and they know it; thus they must catastrophize it and make it sound worse than it is.

So, overall, I've tried to keep an open mind towards the enthusiasts, but the more I listen to them, the less impressed I become. Over several months, none of them (that I've interacted with) have acknowledged, without prompting, that people who aren't straight and cis and Christian and white and able-bodied and moderate/liberal/conservative have a different set of risks to consider than those who are.

And that's the irritating part. Because we're RIGHT FUCKING HERE, we're your mutuals in many cases! We're doing our best to tell y'all what OUR experiences with Mark Zuckerberg's company have been like. The information is there. Thus, we can observe that you remain ignorant out of callousness and carelessness, or you are deliberately lying about our motivations. Really, one or the other, it doesn't matter: both options mean you suck.

Please suck less, #Fediverse.

#meta #MetaMeta #Facebook #FuckZuck #Mastodon #Threads

#fediverse #meta #metameta #facebook #fuckzuck #mastodon