Clarification

You do not have to worry about your mastodon.social (m.s) account being defederated.

There is a well meaning, but misleading post currently promoted that suggests you should move your m.s account because:

1) "Instance admins are considering defederating them"
2) "Their admin is making spam accounts easier to create."

Very few, if any, instances are considering blocking m.s, and the recent spam attacks are worthy of sober discussion, not hyperbole. [more]

1/
#moderation

@mastodonmigration If you read through #mastoadmin posts after the recent spam wave, some admins definitely blocked or silenced mastodon.social. Some temporary, some longer.

@daniel As discussed above, the issue here is not whether some instances temporarily blocked mastodon.social while the attack was going on. The implication was that people on mastodon.social were at risk for being "defederated" and that they should change instances to avoid this. This was a misleading because peoples accounts on mastodon.social are not at risk of being isolated.

1/

@daniel If what had been presented is that instances under attack may be temporarily defederate, and that mastodon.social has recently experienced hacker attacks, which resulted in a few instances blocking them for a short period of time while the attack was being addressed that would not have been as frightening.

In fact, that would be a good description of the system working as intended. Isolating the area under attack while the problem was addressed.

2/

@daniel The implication is that mastodon.social is particularly vulnerable to such attacks because it is big, and it is too big to be successfully moderated. This simply does not make sense. Any instance with open admissions can easily be subject to such attacks and while it is certainly difficult to moderate larger instances it is just a matter of allocating sufficient resources. In this case the attack was dealt with pretty swiftly, so it is not a good example of a breakdown.

3/

@daniel Any instance, big, medium or small that is targeted in this manner will need to do the same thing. It will need to address the attack and while it is doing so, it may be defederated. Hopefully, that defederation will only be temporary as was the case with the latest mastodon.social incident. One could say that smaller instances have the risk that if they don't respond quickly enough it could trigger more permanent isolations. These are all issues we should be discussing.

4/

@daniel What attacks like this are intended to do is to exploit our weaknesses and create dissention. Rather that use this attack that was basically thwarted to initiate a blame game, we should be taking lessons from it on how better to manage the next assault, Because the bad actors are not done with us, not by a long shot. We got this, but we have to work together.

5/

@mastodonmigration I just don't understand where this certainty of your statement comes from or what your intention is. "They will not...", "They're not at risk...".

There are definitely considerations by admins to defederate mastodon.social if it reaches a certain user share:
https://mstdn.social/@feditips/110260432218416976

And I'm pretty sure I've also seen statements by bigger instances with a couple thousand of users that back this decision (unfortunately the search isn't really good enough to find those posts atm).

The question is also whether the temporary blockings of mastodon.social will at some point become very many temporary blockings which are then actually more or less permanent. The moderation of mastodon.social
will definitely suffer as the number of users increases (even if you leave out spam accounts and attacks like yesterday). The other issues were mentioned in the post by @feditips .

If the users can do it and are confident enough, they should
definitely register on other instances. If only for the reason of load distribution and to keep the #Fediverse alive and a nice and friendly place.

Btw some of the other fediverse software uses captchas to prevent bot accounts.
FediTips has moved! (@[email protected])

I don't think people are realising the danger the Fediverse is in. The only thing stopping corporations and VCs taking over this place is that the Fediverse is spread out on many different servers, which makes it very difficult to purchase. If most of the Fediverse ends up on mastodon.social, which is now a strong possibility, there will be nothing to stop most of it being sold to Musk or Zuckerberg or whoever. The bigger mastodon.social becomes, the more likely a buyout is to happen. (1/4)

Mastodon 🐘
@daniel @feditips These seem like two separable issues. 1) Vulnerability to hacker attacks and 2) The wisdom of have very large instances. We should be discussing both, but not necessarily conflating the two. You raise a good point that captchas to validate sign ups may be a good thing to reduce hacker spam. The feditips article raises a myriad of good reasons why large instances carry risk for our future. Neither of these are simple matters and they don't necessarily go together.
@daniel @feditips Regarding the "not at risk" statement. People on mastodon.social are simply not at risk of being permanently fediblocked isolated from large parts of the Fediverse. They simply are not, and to suggest they are is a scare tactic.

@mastodonmigration @daniel

It's not a scare tactic.

Blocking mastodon.social is now seriously on the cards for many admins, even ones who would never have done it before.

The reason the Fediverse exists is to be decentralised. M.s is way too large now, and getting even larger due to the official app's terrible new onboarding.

If people want this place to be decentralised, they need to move off mastodon.social. If they don't care, then they can expect more fediblocks as m.s grows.

@feditips @mastodonmigration @daniel If my instance blocks mastodon.social I will move to it.
@feditips Does this concern apply to mstdn.social as well? Thanks.

@TimKStanton

No.

Mstdn.social is a totally different server owned by totally different people. It has no connection whatsoever to mastodon.social.

@feditips Thank you so much for your fast and thoughtful response!!

@mastodonmigration @daniel

The whole point of this place is to spread the network out:

https://fedi.tips/why-is-the-fediverse-on-so-many-separate-servers/

If the growth of m.s is a threat to this, then that growth needs to be stopped.

Ideally, the owners of m.s would stop taking signups, or at least remove it from the official app. But they're doing exactly the opposite, they're telling everyone to sign up on m.s.

M.s are destroying the driving force of the Fediverse by doing this, m.s need to stop.

Why is the Fediverse on so many separate servers? | Fedi.Tips – An Unofficial Guide to Mastodon and the Fediverse

An unofficial guide to using Mastodon and the Fediverse

@feditips @mastodonmigration @daniel ideally, Limiting or Silencing etc. Should work in the long run, too, but we'll see about that. Sloth.run and tooot.im already limit mastodon.social indefinitely

@feditips honest question from a non-techie who came here when Twitter was first purchased but not from Twitter: Would it be feasible for new sign ups to be offered the option to be automatically put on a random instance to start? Of course the instances on that list would choose to opt in to it and new users could choose to DIY if they desired. But from my perspective as a still newbie, what instance I ended up on mattered very little as a casual user with no specific focus. I think most people are like me.

I get that the wealth of servers protects the system as a whole from takeover etc and that's great. But asking new users to care what instance they are on and evaluate them from the get go is a big hurdle. It's hard to grok why the choice even matters when one first signs up. So sign new users up to a random one by default to spread everyone around, but give them the option to choose too. Could that work?

@cmonster

Yes, a random server from a trusted pool with good track records is exactly what people are suggesting should happen.

@feditips great. I hope that happens.
Thanks for all you do. Yours was one of the first accounts I followed and still one of my faves. I learn new stuff all the time from you!πŸ™
@cmonster @feditips I have been thinking about this very idea during the recent spam incident. You articulated it better than I.
@cmonster @feditips This is certainly one of the suggestions, and there is absolutely no technical reason it would not work.
@feditips @daniel Again, your work on this issue is commendable. But misleadingly telling people they will be isolated if they don't move, will not help your cause.
@feditips
I'm on a matrix channel of dozens of Fediverse admins. Blocking m.s has come up and has been discussed in all seriousness.
@mastodonmigration @daniel
@feditips @mastodonmigration @daniel This feels like cutting off your nose to spite your face. If the majority of the network is on mastodon.social and the only way to access the majority of the network is to join mastodon.social, new users will (rationally) choose to join mastodon.social, leading to further centralization. It’s a positive feedback loop.

@feditips @mastodonmigration @daniel

Why a block? Why not limit or silence if one wants to take action? At least until there are moderator tools to help avoid these attacks?

Blocking sounds extreme to me.

Blocking might cause a large exit from the Fediverse if people feel they are being made pawns in some sort of internal uprising.

I'd be pissed if suddenly I lost all my connections to people I communicate with on mastodon.social. I'd think, "who the hell are these people to decide that I can't talk to my friends any longer or follow people who I like to follow."

I'd leave permanently. I would never trust another server Admin. I'd never come back.

Convince me that I'm wrong.

@Jerry @mastodonmigration @daniel

"I'd be pissed if suddenly I lost all my connections to people I communicate with on mastodon.social. "

It's not going to be painless, but it will be a lot easier than if m.s becomes a majority of the Fediverse.

If that happens, the Fedi itself could be bought and sold on the whim of the owner of m.s (which at the moment is Eugen but who knows who it will be in the future).

It's like global warming: the longer you wait, the harder it is to take action.

@feditips @Jerry @mastodonmigration @daniel its a shame theres no way to be able to put in your servers address into a search engine and see all the fediverse instances that have blocked you. I understand why that isnt possible though as someone pointed out, bad actors like hateful instance owners could use that info to target everyone who blocked their instance. not sure theres a solution to help those of us who want to check our instance isnt blocked and contact admins if it is by mistake.1/2

@guiltmanager @feditips @Jerry @mastodonmigration

its a shame theres no way to be able to put in your servers address into a search engine and see all the fediverse instances that have blocked you.There's a website that does this actually. And yes, it used to harass people which is why I'm not going to share the address.

If the website is correct, mastodon.social is currently moderated (muted or blocked) by about 279 instances across the fediverse.

@daniel @feditips @mastodonmigration @Jerry can understand why you wouldnt share it! however if you feel like sharing it privately feel free to dm me, although admittedly it would probably take you a while to research me enough to know my intentions aren't bad.
@feditips @Jerry @mastodonmigration @daniel maybe a service you put in your server address and it says "you are not blocked" or "you are blocked by one or more instances, appeal by typing message and email in this box which will be sent to all instance admins" then you can ask "hang on my instance is blocked is this just a blanket block of say all digital ocean ips, or something to do with my content"
@feditips @daniel Generally support your campaign here, but it would be much better to encourage people to move to smaller instances for the many reasons you spell out very well than to try to make them afraid that mastodon.social will be isolated, which simply is not going to happen.