npub1myczpl7ftv0tpqlrwhf24phauuynlkj3ekg07e2966ftxupznrgqw2dqgs (npub1myc…dqgs) npub1kq2pwuws34y2g9aaatsrzl5fy3ttc5t6x7fhs3cvln8qx6ts95rqxwdc9m (npub1kq2…dc9m)
There seems to be a problem with the way Mastodon handles suspensions (aka defederation, although temporary).
All followings between the two instances are deleted, but not resored when the suspension is lifted and the instances are reconnected.
Moderators/admins have few tools to deal with spam attacks from other servers. It is a lot of work, because when reported, each spam acc needs to be suspended one by one, batch resolution of reports/blocks is not really feasible.
Just imagine, just how a hell of total work hours are caused by these spam accounts: on every instance (currently around 15 k !!), a mod has to invest several clicks for each (ok, not every spamm acc wrote to all instances, but still).
1) Other instances can be *silenced* (like muted: only followers will see the toots). However, the last spam attacks use direct messages (with @ mentions) and these are apparently unaffected by silencing.
2) Other instances can be blocked/suspended/defederated. Spam DMs won't come through, and existing DMs will be deleted.
So the decision is basically: spam protection vs maintaining follower networks.
This time, it sucks if you had important ties to mastodon.social. Because it will be difficult to rebuild them (I am not aware how to export and backup your follower/following lists).
Hopefully, this will be addressed by the devs, as this situation is unbearable. Odds are high that this will be a priority, because the main devs are running mastodon.social.
Earthworm /
npub1xm…de5ut
2023-05-17 12:15:08
in reply to nevent1q…p3v0
Author Public Key
npub1xm6eexa94xd7x79lugtcunfcews2z934aheut6ns3scg4s8ukw2sade5utPublished at
2023-05-17 12:15:08Event JSON
{
"id": "6be0ef0f90d6d63b3ccea44e790a644236eddd71429345fbcabdf23c7795b097",
"pubkey": "36f59c9ba5a99be378bfe2178e4d38cba0a11635edf3c5ea708c308ac0fcb395",
"created_at": 1684325708,
"kind": 1,
"tags": [
[
"p",
"d93020ffc95b1eb083e375d2aa86fde7093fda51cd90ff6545d692b3702298d0",
"wss://relay.mostr.pub"
],
[
"p",
"b0141771d08d48a417bdeae0317e892456bc517a379378470cfcce0369702d06",
"wss://relay.mostr.pub"
],
[
"p",
"27afc02bc9b8de25ee456552dcd008b2115237a9794b94cd67311922f0542c15",
"wss://relay.mostr.pub"
],
[
"p",
"1ccf5d986247440d9a7627bcbe5b3a8b371df87fee28d3491db43c56a9482d1f",
"wss://relay.mostr.pub"
],
[
"e",
"cc314102de19dc47f415c9cf1e10fd6e1df042d353b65c9e7a6ecd240dc1f5a1",
"wss://relay.mostr.pub",
"reply"
],
[
"mostr",
"https://kolektiva.social/users/earthworm/statuses/110383969635187006"
]
],
"content": "nostr:npub1myczpl7ftv0tpqlrwhf24phauuynlkj3ekg07e2966ftxupznrgqw2dqgs nostr:npub1kq2pwuws34y2g9aaatsrzl5fy3ttc5t6x7fhs3cvln8qx6ts95rqxwdc9m \n\nThere seems to be a problem with the way Mastodon handles suspensions (aka defederation, although temporary).\nAll followings between the two instances are deleted, but not resored when the suspension is lifted and the instances are reconnected.\n\nModerators/admins have few tools to deal with spam attacks from other servers. It is a lot of work, because when reported, each spam acc needs to be suspended one by one, batch resolution of reports/blocks is not really feasible. \nJust imagine, just how a hell of total work hours are caused by these spam accounts: on every instance (currently around 15 k !!), a mod has to invest several clicks for each (ok, not every spamm acc wrote to all instances, but still).\n\n1) Other instances can be *silenced* (like muted: only followers will see the toots). However, the last spam attacks use direct messages (with @ mentions) and these are apparently unaffected by silencing.\n\n2) Other instances can be blocked/suspended/defederated. Spam DMs won't come through, and existing DMs will be deleted.\n\nSo the decision is basically: spam protection vs maintaining follower networks.\n\nThis time, it sucks if you had important ties to mastodon.social. Because it will be difficult to rebuild them (I am not aware how to export and backup your follower/following lists).\n\nHopefully, this will be addressed by the devs, as this situation is unbearable. Odds are high that this will be a priority, because the main devs are running mastodon.social.",
"sig": "707c7fcbe7e5ad17d2f4284ab89871b86e35e068dda9b63887a76c73a89a24da63db2ebbaaf2cb25301b338ff5864d522dac12f4a5d508d0eb9903e06ebc44c9"
}