Hi all, we've made the decision to defederate with mastodon.cloud, due to the unfortunate neglect of the server.
-
Hi all, we've made the decision to defederate with mastodon.cloud, due to the unfortunate neglect of the server. Mastodon.cloud was already limited by Fosstodon. We will complete the defederation in 72 hours. Please reach out to accounts you still follow on mastodon.cloud and encourage them to move, while you can still contact them as the defederation will break your follow.
@fosstodon pot calling kettle black
we still remember when your modteam has nazis lmao -
System shared this topic
-
@fosstodon What happened there? Is it problematic content?
@danieruotakuboy@vzla.masto.host @fosstodon@fosstodon.org
If I understood correctly it is abandoned server, probably not updated and has spams due to having open registration.
-
Hi all, we've made the decision to defederate with mastodon.cloud, due to the unfortunate neglect of the server. Mastodon.cloud was already limited by Fosstodon. We will complete the defederation in 72 hours. Please reach out to accounts you still follow on mastodon.cloud and encourage them to move, while you can still contact them as the defederation will break your follow.
-
@fosstodon What happened there? Is it problematic content?
@danieruotakuboy @fosstodon there hasn't been any moderation there for most of a year, and it has open registration, so spammers are signing up there and operating without getting shut down.
-
@fosstodon What happened there? Is it problematic content?
@danieruotakuboy @fosstodon The server is likely abandoned from what it seems. The main admin on there hasn't posted anything for over 3 years, and it's using an outdated version of the Mastodon client that's been out of support since last April. Especially in the last year or so, there's been persistent issues with spammers and inappropriate content springing up on there (due to still having open registrations) that's not being actively removed, even after multiple reports.
-
Hi all, we've made the decision to defederate with mastodon.cloud, due to the unfortunate neglect of the server. Mastodon.cloud was already limited by Fosstodon. We will complete the defederation in 72 hours. Please reach out to accounts you still follow on mastodon.cloud and encourage them to move, while you can still contact them as the defederation will break your follow.
@fosstodon I was also thinking about it.. For now we contained it but perhaps need further action
-
@fosstodon 72 hours is pretty short notice. Isn't standard practice for responsible defederation in the range of a few weeks notice at least?
@dalias @fosstodon defederation is an act of self-defense.
-
@fosstodon pot calling kettle black
we still remember when your modteam has nazis lmao@moogstad @fosstodon you should totally defederate from them.
-
R relay@relay.mycrowd.ca shared this topic
-
@fosstodon I was also thinking about it.. For now we contained it but perhaps need further action
@fosstodon Btw, pawoo.net & mstdn.jp are from the same company that also owns mastodon.cloud
Both run v4.1.18 and v4.1.25
-
@dalias @fosstodon defederation is an act of self-defense.
@Iwillyeah @fosstodon We all understand that. However since it severs your users' relationships, standard practice for a responsible instance is that you give sufficient notice that people can move if they don't want their relationships severed.
-
@Iwillyeah @fosstodon We all understand that. However since it severs your users' relationships, standard practice for a responsible instance is that you give sufficient notice that people can move if they don't want their relationships severed.
@dalias @fosstodon i suppose it depends on the level of harm federation is causing.
-
Hi all, we've made the decision to defederate with mastodon.cloud, due to the unfortunate neglect of the server. Mastodon.cloud was already limited by Fosstodon. We will complete the defederation in 72 hours. Please reach out to accounts you still follow on mastodon.cloud and encourage them to move, while you can still contact them as the defederation will break your follow.
@fosstodon #Slashdot has their Mastodon account there.
Are they sleeping?
-
@dalias @fosstodon i suppose it depends on the level of harm federation is causing.
@Iwillyeah @fosstodon Yes, I'd say it depends on the level of harm and whether there are any known or potential legitimate relationships with the instance.
If it's just a nazi/csam/whatever instance, immediate defederation is of course fine.
But if it's an abandoned instance your users have actual friends on, ideally you'd give a full notice period. This would of course work better if Mastodon had better controls for low-trust instances, like a stronger version of limiting that refuses to even federate anything from the instance unless it's from an account that has a relationship with one of your users.
-
Hi all, we've made the decision to defederate with mastodon.cloud, due to the unfortunate neglect of the server. Mastodon.cloud was already limited by Fosstodon. We will complete the defederation in 72 hours. Please reach out to accounts you still follow on mastodon.cloud and encourage them to move, while you can still contact them as the defederation will break your follow.
@fosstodon I'm trying to coordinate with their admin to find a solution swiftly.
-
@fosstodon pot calling kettle black
we still remember when your modteam has nazis lmao@moogstad @fosstodon a substantial remediation effort was done including an entirely new moderation team.
-
Hi all, we've made the decision to defederate with mastodon.cloud, due to the unfortunate neglect of the server. Mastodon.cloud was already limited by Fosstodon. We will complete the defederation in 72 hours. Please reach out to accounts you still follow on mastodon.cloud and encourage them to move, while you can still contact them as the defederation will break your follow.
Shunning in the interwebs is brutal.
-
Hi all, we've made the decision to defederate with mastodon.cloud, due to the unfortunate neglect of the server. Mastodon.cloud was already limited by Fosstodon. We will complete the defederation in 72 hours. Please reach out to accounts you still follow on mastodon.cloud and encourage them to move, while you can still contact them as the defederation will break your follow.
Thank you.
-
Hi all, we've made the decision to defederate with mastodon.cloud, due to the unfortunate neglect of the server. Mastodon.cloud was already limited by Fosstodon. We will complete the defederation in 72 hours. Please reach out to accounts you still follow on mastodon.cloud and encourage them to move, while you can still contact them as the defederation will break your follow.
@fosstodon Should I keep my clothes on?
-
@fosstodon 72 hours is pretty short notice. Isn't standard practice for responsible defederation in the range of a few weeks notice at least?
@dalias @fosstodon Is it? It's the first time I see a heads up for defederation in general. Do you have any other examples, where people gave a heads up? I would like to see how they handled things.
-
@dalias @fosstodon Is it? It's the first time I see a heads up for defederation in general. Do you have any other examples, where people gave a heads up? I would like to see how they handled things.
@sheogorath @fosstodon I don't recall where I saw the policies written down, but it was something I asked instance admins about when moving the musl libc account. ISTR there being something good instances basically agree on about this.
