I was wondering why I can’t follow people from Threads on Mastodon and found out it’s because the server I’m on has blocked interoperability with Threads.

Wow, so what are my options here? Nag the admins? Switch my account to a different server? What do I lose if I do that? Which one do I switch to? 🤔

https://www.threads.net/@thatadamguy/post/C02Bv7LPmET/?igshid=MzRlODBiNWFlZA==

It sounds like if I switch servers on Mastodon then I’ll lose my post history. Given that I expect I’ll just stop posting on Mastodon when Threads fediverse integration is done and instead will ask Mastodon users to follow my Threads account.

This actually helps consolidate my text-based social media accounts down to one.

@carnage4life many many people are opposed to threads, even just in general. there were instructions circulating yesterday about how to block the entire domain. moving to threads is going to decimate your audience
@Viss @carnage4life It seems to be it is too early for such opposition... is that because Threads is from Meta?

@locksmithprime @carnage4life yes, and nobody trusts them. at all. nobody is happy that they intend to hoover up data, produce ads, train AIs and other stuff people abjectly came to masto to avoid.

also, the relationship is one-way. masto can see threads, threads cant see masto.

so moving to threads means losing the ability to interact with your audience entirely.

@Viss @carnage4life I see. Well, Meta... the whole world uses Whatsup, but I cannot make myself use that app.
@locksmithprime @carnage4life there are several great alternatives to whatsapp, and they have even been in the news several times because they arent as 'secure' as they claim to be

@Viss @locksmithprime @carnage4life

How is federating making it any easier to Hoover up data? You can view all this without an account.

@plasma4045 @locksmithprime @carnage4life programatic firehose-level api access to the backend is a very different architectural engineering lift. a way easier one. thats sanctioned. as opposed to individually scraping servers on a onsie twosie basis

@Viss @locksmithprime @carnage4life

How sure are we that some of the instances you’re already federated with aren’t just Meta, OpenAI, or Microsoft hovering up data?

Let’s get real - this stuff is all public.

@plasma4045 @locksmithprime @carnage4life because of the thousands of instances that exist, most of them are here expressly to not collect data like meta and google. and just because something is public doesnt instantly mean its trivially accessible or scrapeable, or would even permit that. threads is all public too.

also, look whats happening with ai and scraping of public data, and all the lawsuits.

@Viss @plasma4045 @locksmithprime @carnage4life that's a thing they could do by just having a quiet instance anyway...

@WowSuchCyber @plasma4045 @locksmithprime @carnage4life technically, perhaps, depending on their config. but i estimate that once they were found out, a majority of instances would instantly block them outright.

they lied to congress and the senate MULTIPLE TIMES and got away with it. there is zero reason to trust facebook ever again.

@Viss @plasma4045 @locksmithprime @carnage4life oh yes, I'm not trying to defend them here, I'm against Meta. But I think it's kinda moot to try to hide a content that is inherently public to one of the largest and most capable internet company...
I can hear potential issues with contribution to the protocol and there's clearly something to do there.
But stopping them from collecting data, I think it's impossible.

@WowSuchCyber @plasma4045 @locksmithprime @carnage4life it is quite possible. from a legal standpoint, getting the firehose from twitter is asking one legal team for permission.

getting the same from mastodon? when every server has a unique admin with their own unique set of rules? good luck. every server is a unique entity with its own terms of service. every server is its own unique legal entity.

trying to do big public scrapes is noisy, burdensome and makes them look really bad.

@WowSuchCyber @plasma4045 @locksmithprime @carnage4life so its in their best interest to get some kind of api level access. which they now have. but even still, they are at the mercy of the existing fleet of servers out there.

this access will allow them to taillor their existing bullshit and disinformation machine to grapple with activitypub.

its going to get ugly and fucked, just like cambrige analytica. its practically guaranteed. they got away with murder, so they'll keep murdering

@carnage4life I don't want to interact with threads bc I'm afraid of embrace-and-extend like Google Chat did to XMPP. I won't follow your account on threads, which makes me sad bc I really enjoy your content.

I realize I'm only one person, but maybe if you hear enough pushback, you'll reconsider. Ultimately, you do you tho. ❤️

@carnage4life i absolutely enjoy your posts, and very much appreciate your point of view, we agree on a lot and disagree on a little.

if you do switch to threads i wish you luck but i will unfortunately miss out on your great insights and inventive wit.

my small (very small) wish is you self host a mastodon instance, i wont block you for federating with threads.. but i most certainly am blocking threads.

(admin of a small instance)

thanks for your contributions

@carnage4life To follow you at your threads address, in much the same way I can follow Mosseri already? Seems like an eminently reasonable move on your part and zero impact to me apart from the change of address.

I won’t be clutching my pearls over this one.

@carnage4life I'll still be able to follow you on Threads. I think Jerry at infosec.exchange made a good call to silence Threads but allow people to still opt-in to follow Threads accounts if they want to. It would be nice if the follows worked both ways though ... I heard people on Threads won't be able to follow Mastodon accounts?
@tsupasat
From the comments I've seen it sounds like people on Threads will be able to follow people on fedi.... But the communication will be **only** in that direction, you won't be able to follow them, nor will their responses or reactions make it back to you.
@carnage4life
@carnage4life I believe you could port to #firefish and not lose accounts or followers. My point being, there are options without going back into a Meta walled garden.
@carnage4life get an alt! That is, don't move right away. Just check it out. If you've never switched instances before I think you'll find it fascinating. If you do end up moving, let me know if you have questions. I've done it 4 - 5 times now

@carnage4life I believe the old posts stick around when you set up the redirect for example from 2018 when I set that up

https://mastodon.social/@reconbot/100913703427402690

@carnage4life will miss you though I don’t expect threads to go smoothly
@carnage4life Absolutely predictable consequence of server operators preemptively blocking Threads. People will either migrate to larger servers that don't, or to Threads altogether. I would hate to see you leave Mastodon even if you were still in my home feed through Threads, simply because I believe Mastodon is the better platform. I hope it doesn't come to it.

@carnage4life Hi Dare - @trumpet has posted a thread explaining the reasons for holding back. The position is trying to take a middle ground - a sort of "wait-and-see" approach. So, Mas.to is not rejecting Threads integration but is waiting to see how it plays out. I am not on one side or the other on this and I think this is a good middle ground for the time being. As frustrating as it is.

Here is the post with the arguments:

https://mas.to/@trumpet/111586370843868206

[email protected] (@[email protected])

HELLO THERE! I’m getting a lot of questions about Threads, so here’s a short thread (pun intended) which should provide clarity on our position. We chose many months ago to block Threads because of two primary concerns. Firstly we saw performance issues last November because of explosive growth, and while we have much stronger infrastructure now we are keen to avoid that happening again. We also have concerns as to whether Threads will manage to effectively moderate their users at launch. /1

mas.to
@carnage4life - I hope you continue to post on Mastodon, but in any case I'm grateful for what I've been able to read so far.
@carnage4life if interoperability is there, why use Threads as main service and not Mastodon?
Currently the Threads app is way shittier than the Mastodon app I’m using. If complete Fediverse integration would be there tomorrow, I’d definitely still use Mastodon/Ivory.

@carnage4life ultimately if they don't lift the block switching instances is your only option.

Given the limited interoperability right now, I guess the question is if it's worth letting your instance admins know your preferences and waiting to see what they do.

@carnage4life also you can only follow a handful of select accounts for testing right now. It’s a feature that’s still being worked on at threads. You can follow @mosseri and a few others but not everyone (yet).
@carnage4life Semi-tangential question: How do you discover people on Threads without joining Threads? Are people linking their Threads accounts in other places that you discover, like Twitter accounts used to be?

@carnage4life

I'm thinking mastodon.social is a safe bet because @Gargron seems pretty psyched about this thing working out. You might start by setting up a test account to check that it's firing on all cylinders

@carnage4life I didn't know threads was part of the fediverse
@paulbiggar @carnage4life they’re doing some tests on a few accounts (e.g. @mosseri) at the moment, still early - but it works

@carnage4life
If you swtich, your posting history on mas.to stays on mas.to. & some of your follows or followers may break, if their instance is blocked by your new server or vice-versa. Also people seem to say that it's a good idea to manually migrate your following list, just in case.

It's not as small a deal as it's commonly made out to be, but it's not earth-shattering.

@carnage4life I seem to be able to follow Threads accounts from sfba.social - in my limited poking around, I haven't found any super-compelling content yet, but early days...
@carnage4life @fosstodon isn’t blocking them and is a great instance
@carnage4life One option is to create another account on a different server which does not block Threads and use a client which supports multiple accounts so you can combine both into a single timeline. There is not feature to merge accounts with Mastodon so the downside is you'd be fracturing your identity across redundant accounts. On the 2nd account you could direct people to your primary if you choose this option.
@carnage4life any other server that hosted known hate groups would be defederated by many. Threads has many (e.g. LibsOfTikTok, Gays Against Groomers, etc.). I'm...not fond of the huge banhammer, but I don't know how you avoid the fediverse becoming a Nazi bar, and I distinctly don't want the fediverse to become a Nazi bar. I'm also on mas.to, but, I'm probably OK with not being able to interact with Threads. At least for now.
@carnage4life but, also this is a challenge of the platform. With a bunch of small servers where everyone knows everyone, this model makes perfect sense. But, that's not where we are. There are millions of users now, and the bigger instances have tens/hundreds of thousands, and Threads would, I assume, be the biggest single instance. It feels gross to ban everyone for the actions of a few (though the ban is actually about the inaction of the server admins, failing to moderate hate speech).

@carnage4life It is fairly easy to switch. You lose your post history though. All your followers and follows come with though.

https://blog.joinmastodon.org/2019/06/how-to-migrate-from-one-server-to-another/

How to migrate from one server to another

With the sad news that KNZK was shutting down we thought it might be useful for people to have a refresher on the features that Mastodon has built in that make moving instances easy and painless. Backing up Your Data Data export If you are moving to a new instance the first thing you will want to do is to get a backup of all of your data. Thankfully this process is painless with the Data Export tab under the “Import and Export” page. Here you can download your followers list, your muted users list and your blocked users list.

Mastodon Blog
How to Kill a Decentralised Network (such as the Fediverse)

How to Kill a Decentralised Network (such as the Fediverse) par Ploum - Lionel Dricot.

@carnage4life It looks like threads.net is listed here: https://codeberg.org/oliphant/blocklists. Which mas.to seems to base their blocklist off of.

Almost looks like 60-80% of consensus for blocks to appear on that list. Is threads.net already blocked that widely???

I don’t understand how so many people here advocate for the fediverse concept while also blocking servers over literally nothing. threads.net has not fedierated any spam, malicious content or anything negative yet. Way too premature…

blocklists

Blocklists

Codeberg.org

@fishcharlie
"I don’t understand how so many people here advocate for the fediverse concept while also blocking servers over literally nothing."

I don't understand why people don't understand this. Federation is about connecting, yes, but also about not connecting with those one doesn't like. You're basically saying "you guys say you like having choices but you chose differently from me, what's up with that?"

Also, premature? How many genocide enablings, political manipulations, labor abuses, and unethical experiments does it take?

@SallyStrange And what federated content have you seen from threads.net that you don’t like? There’s only like a handful of federated accounts.

I view it as extremely premature. They just started federation yesterday. Yesterday!

Overall tho. I don’t have a problem with server admins making this decision if they are transparent about it. However so far I haven’t seen one concrete federated post that warrants blocking the server. I don’t think that is instilling transparency. (1/2)

@SallyStrange My real issue tho is the fact that @Mastodon doesn’t allow you to take your posts with you if you decide to move servers. If users aren’t happy with their server admins choice, they should be able to move with zero negative impact. Right now that isn’t the case. I hope a fix for that is on the roadmap. (2/2)

@fishcharlie @SallyStrange @Mastodon Your posts are not some gold nuggets you hoard.

That's such a toxic mindset.

Microblogging is not blogging, so if you are obsessing about some old post that was hot for a few hours in July 2022, just screenshot it and put it in an actual blog post.

It's unhealthy af, but nobody's stopping you.

@fishcharlie @SallyStrange That same "argument" would apply to instances with names that include slurs, references to child pornography or to violence.

"And what federated content have you seen from map.moe that you don’t like?"

Fuck that. We don't need to wait for obvious bad actors to prove their obvious intentions.

And Meta's intentions are obvious.

@androcat @fishcharlie oh but have you considered that it's haaaaaard to port an account across instances? 😢😢😢
@SallyStrange @fishcharlie
in my time on fedi i've seen big drama over alleged bad actors over

- data scraping
- enabling bigots
- using threats of cutting off large swathes of users from each other in order to manipulate instances into complying with more draconian content standards than they actually want
- wilful retention of deleted data
- creepy stalking behaviour
- waves of angry algorithm-trained normies making life miserable for existing users

if you put all those in a venn diagram, Meta would be in the middle of the overlap of all of them
@fishcharlie @carnage4life it's 60-80% of a (rather short) "trusted sources" list of pre-approved instances, quite a few of which are *notorious* in the larger fediverse for being extremely trigger-happy about defederating, so threads being well represented on there doesn't say much at all about the rest of fedi being hostile to threads

(and i'm saying this as someone who wishes a lot more people were a lot more hostile)
@apophis @carnage4life So after some digging. By “rather short” does that only mean 6 instances? 🤯 https://writer.oliphant.social/oliphant/trusted-source-membership
Trusted Source Membership

Requirements to be a Trusted Source and contribute blocks to shared blocklists. Inclusion Criteria Server admin and moderation team mus...

The Oliphant
@fishcharlie @carnage4life i hadn't even checked and had assumed/misremembered it being more than that, lol

@fishcharlie This blocklist is based on a small (and opinionated?) subset of servers, and the consensus is based on server count, not user count. This may not be representative.

@carnage4life

@fishcharlie @carnage4life those people have read threads T&Cs and don’t agree with the “we can take it all in” approach, and it also says they’d be sending their advertisement spam over too.
Also, there is a high probability of “embrace/extend/extinguish” that will be attempted

@sxpert @carnage4life But by federating with Threads you aren’t agreeing to their T&Cs. You only agree to that if you create an account on Threads.

(Not a lawyer & this isn’t legal advice, so this information might be completely wrong)