Hmm, I'm beginning to see the issue here with one way Federation from Threads.
Or, Star Trek Whale Probe effects. "We're just looking to communicate"... "WE"VE LOST ALL LIFE SUPPORT! DEPLOYING SOLAR SAILS! I HOPE WE SURVIVE!"
Actually, maybe Close Encounters of the Third Kind. I hope my server is not going to lose all its windows.... #threads https://www.youtube.com/watch?v=S4PYI6TzqYk
Close Encounters of the Third Kind (6/8) Movie CLIP - Communicating with the Mothership (1977) HD

YouTube

@ai6yr
Reminder that you can always block accounts, or limit or block them, on the server level, if it gets too extreme. Individual users can also silence the server.

I might start keeping a list of everyone we block on there and just periodically publishing it.

@ai6yr it won't be like this forever.
@vmstan @ai6yr never give a company the benefit of the doubt, especially undeserving companies
@louie They're still just in testing. Not everyone can even activate this feature. So for now I think it's actually reasonable to do this.
@ai6yr My instance preemptively blocked Threads. As a mod, I supported that. I opened a second account on another server to play around with Threads federation, and from the user perspective, it’s fine. I only see people I want to see. Slightly annoying that you can’t reply from Mastodon yet.
@ai6yr one way blocks come to the rescue
@ai6yr Are you concerned about some sort of volume? Or is it that you can only subscribe and not reply? Or something else?
@rob @ai6yr to me, the mechanics of the comms is one of the more realistic potential problems with threads. Masto is apparently a somewhat inefficient architecture, adding significant volume to a small instance could be problematic
@pixelpusher220 @rob Yep, outgoing traffic could be an issue, for sure. I have a plan if that happens here (migrating all my bots to a new instance on an ISP with no outgoing traffic charges), but that would be a PITA.

@pixelpusher220 what is small? and where would the significant volume come from?

I have my own hosted instance, so that's why I am asking.

@ai6yr

@rob @pixelpusher220 I've got a small instance, but with a lot people/bots that are followed... if you had a *lot* of people from Threads follow it would (currently) create a huge outgoing queue backlog when there is high post volume, I believe... i.e. a single person followed by 5000 people results in 5000 outgoing requests to servers (posting that thing to all 5000 people following you).

@ai6yr @rob or 25,000 'reports' of a post or account.

just the influx of a node with 100 million people being processed by nodes of of the size of 10. Any interaction has the potential to bring the small node to it's knees conceptually.

@ai6yr @pixelpusher220 That’s so weird. You’d think that if 4,999 were on Threads and 1 was on a different server, that’d be 2 posts. One to Threads, which would then route to the single addresses and one to the other sever. But you’re saying that’s not how it works.

I guess servers don’t route messages to accounts. Everything happens at the account level.

Is that right?

@rob @pixelpusher220 UPDATE: looks like Mastodon accepts shared inboxes, and *does* distribute internally. So it's just queues to every SERVER (vs. every account). So perhaps this is not as inefficient and I had been thinking. https://seb.jambor.dev/posts/understanding-activitypub/
Understanding ActivityPub - Part 1: Protocol Fundamentals

I explain how I'm using ActivityPub.Academy to explore ActivityPub.

@ai6yr @pixelpusher220 I think where you might get crushed is if you had a viral post that tens of thousands of people responded to with media attachments. Now there I could see a server wilting under the bright glare of a much larger server.
@ai6yr Maybe I'm just naïve but "one-way federation" ≠ "federation".
@pjohanneson We can see Threads posts, but they can't see Fediverse posts (or replies).
@ai6yr Yeah, my opinion is that it's not federation if it's only one-way. That's just shouting.
@ai6yr @pjohanneson Sounds like a loudspeaker for all those sh*ty ads and influencer types to me.

@ai6yr

However, I’m told that will change in the future.

I don’t know how 🤷🏻‍♂️

I like the idea of the few active Threads users there will ever be are only vaguely aware of the Fediverse blob, the mass unable to be analyzed for insights.

The idea makes me happy.

@ai6yr One way federation equals spam, not federation
@ai6yr You can treat them like RSS.
@ai6yr isn't the same as twittex?
lists.d/activitypub.threads.domains.block.list.tsv at main · greyhat-academy/lists.d

List of useful things. Contribute to greyhat-academy/lists.d development by creating an account on GitHub.

GitHub
@kkarhan @ai6yr
While I don't disagree with the sentiment, if we were going to block them preemptively, we already would have done that. Remember that everyone has had plenty of time to learn about and think on this decision: different servers operate on different principles, so we make different decisions on the same evidence. This gives people options, which is good for Fedi.
@Raccoon @kkarhan Yep, let everyone make their own decisions. The jury is still out for me, but I am watching this carefully for both the "Meta is evil" and "OMG there are a million people on Threads is that going to break my server?!" reasons.
@ai6yr @kkarhan
Be sure to keep your users in on what's going on, and make sure they know what might happen and what their options are. At some point I will try to put out a list of servers they can move to if they want to go somewhere that's blocking threads, and maybe get some of those servers to point their users towards us.

@Raccoon @ai6yr well, I specifically chose an Instance that does block them and I'll continue to exclusively use those that do as of @FediPact ...

In fact, I do consider blocking every instanve that doesn't block them to enshure none of my content is being subjected to the inacceptable ToS of StasiBook...

#MyAccountMyChoices
https://techhub.social/@Raccoon/112209900116603967

Raccoon at TechHub :mastodon: (@[email protected])

@[email protected] @[email protected] While I don't disagree with the sentiment, if we were going to block them preemptively, we already would have done that. Remember that everyone has had plenty of time to learn about and think on this decision: different servers operate on different principles, so we make different decisions on the same evidence. This gives people options, which is good for Fedi.

TechHub

@kkarhan @ai6yr @FediPact
A couple things here...

One, if your instance is blocking Threads, they can't see your posts, period. Instances don't share other instances posts as part of Federation, only their own: servers have to get posts from the servers they came from. This system was specifically built with blocks of bad actors in mind.

Second, none of the instances which are not yet blocking Threads actually trust the Facebook company. We aren't planning to give them anything that isn't already publicly available to any other server, we just aren't blocking them preemptively. Most of us actually think it's great that y'all are blocking.

Finally, we didn't agree to any sort of Fedi Pact as far as I understand, but blocking us on the grounds of choosing different strategies for the same communal goals, when we all agree on the big picture, that the decentralized community is good, seems very counterproductive to those goals.

@kkarhan @ai6yr @FediPact
Also, a large part of why a chunk of us aren't blocking them is specifically because we believe in that "my account my choices" concept. We want to make sure that people around the network have plenty of options, and are happy to see them migrate to and from our server to take advantage of that. Some users want the option of being able to follow and talk to people on Facebook's network, assuming they actually federate. Other users want the option of having their posts be inaccessible from Facebook servers.

Both of these things are legitimate, and some people may even decide to take both, creating a big public account on a server that doesn't block threads, and a more private one on a server that does: I actually have at least one alt account on a server that's blocking Threads.

@Raccoon @ai6yr @FediPact

Again: Your Account = Your Choices!

I just chose to deliberately NOT wanting to have #NSAbook / #StasiBook in my life and to enforce that boundary by all means necessary - period.

#EOD

@ai6yr One-way federation sounds like RSS with extra steps. In that note, I'm surprised that Mastodon doesn't support following RSS feeds directly.
@ai6yr i wish someone did this to me
@ai6yr
So far, it hasn't been like that, mainly because people have to actually follow the content for it to show up over here, and they honestly don't have a lot of actual content people want to follow...