Hi all, we've made the decision to defederate with mastodon.cloud, due to the unfortunate neglect of the server.
-
@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.
-
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.
I have shared a guide on how people can migrate from their OLD Mastodon account to a NEW Mastodon account.
https://mastodon.cloud/@warning/116428433776802175
(Feel free to save the photos and re-post elsewhere as yours if you wish)
-
@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
@stux @fosstodon hello, it has been a while since I last used mastodon but I got a noltification about this. Could you (or the admin account for this instance) provide some context on why is this necessary? Does the low version introduce a security risk, or did something worse happened? Sorry for disturbing.
-
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 General comment on the thread, intended to be completely not-critical, just observational
Actually nah I don't know enough to actually have an opinion on the issue at hand at all, but things like this are interesting is all, I guess - there will be those tempted to shoehorn the incident into their preconceived notions of what is happening here, and I was one of those for a few hot seconds,
but what I see is exactly what one should expect to see, in what is still the very early stages of a networking system and network that is still rapidly evolving. People start things with those things, you know the things... intentions. Maybe good, maybe bad, but intentions. Gotta keep an on eye on intentions, yep.
And a lot of em probably neurodivergent, which means that statistically, some of em are just gonna crash or disappear, those intentioned humans, whether it's depression, war, ADHD, loss of employment, gaining of employment (this has caused me to ghost more than one personal project or trajectory)... so many reasons why people have to pack their bags or pick up their SHTF backpack and go.
A neglected server can limp along for a long while, but if it's neglected with open signups, that's a problem for the whole network. That's as close as I'm gonna come to my personal axe.
-
@stux @fosstodon hello, it has been a while since I last used mastodon but I got a noltification about this. Could you (or the admin account for this instance) provide some context on why is this necessary? Does the low version introduce a security risk, or did something worse happened? Sorry for disturbing.
For mastodon.cloud, it's also very absent mods, and some awful accounts signing up there unhindered. (From what I understand)
-
@fosstodon What happened there? Is it problematic content?
@danieruotakuboy @fosstodon For (slightly) more information see https://sfba.social/@announcements/116401088567092431 . I think @iftas might have had a post too but I'm not sure I'd be able to find it.
-
For mastodon.cloud, it's also very absent mods, and some awful accounts signing up there unhindered. (From what I understand)
@5ciFiGirl @stux @fosstodon ah so they left a server running unmoderated with unmetered sign up, i see
-
@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.
@dalias @sheogorath @fosstodon are you maybe thinking about this? It's similar in spirit:
https://joinmastodon.org/covenant#:~:text=Commitment,another%20server
-
@fosstodon General comment on the thread, intended to be completely not-critical, just observational
Actually nah I don't know enough to actually have an opinion on the issue at hand at all, but things like this are interesting is all, I guess - there will be those tempted to shoehorn the incident into their preconceived notions of what is happening here, and I was one of those for a few hot seconds,
but what I see is exactly what one should expect to see, in what is still the very early stages of a networking system and network that is still rapidly evolving. People start things with those things, you know the things... intentions. Maybe good, maybe bad, but intentions. Gotta keep an on eye on intentions, yep.
And a lot of em probably neurodivergent, which means that statistically, some of em are just gonna crash or disappear, those intentioned humans, whether it's depression, war, ADHD, loss of employment, gaining of employment (this has caused me to ghost more than one personal project or trajectory)... so many reasons why people have to pack their bags or pick up their SHTF backpack and go.
A neglected server can limp along for a long while, but if it's neglected with open signups, that's a problem for the whole network. That's as close as I'm gonna come to my personal axe.
@jpaskaruk @fosstodon Yup, I agree. Besides instructions (e.g., in blogs) on how to set up a mastodon server, there should also be some instructions how to set up robust administrative structures (co-admins, moderators) that could take over. At least for servers that are intended to host other 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
@muppeth
Do you think about de-federating fe.disroot.org from mastodon.cloud as well?
Sounds sensible to do so, imho.
