Here's why I don't panic about Threads personally; CW: long (over 3,000 characters), Threads, Meta, Fediverse meta, non-Mastodon Fediverse meta
View article
View summary
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
