There are comments asking us to elaborate so here are some more specific reasons why we will be defederating.
-
Secondly, their Mastodon software version has not been updated for an extended period of time and has known security vulnerabilities. We do not want to risk any exploits with those vulnerabilities that may affect our users.
An instance that is unmoderated and insecure poses a risk to other servers it federates with. The Fosstodon team did not take this decision lightly, and arrived here after months of observing these issues.
Again we encourage you to reach out to any accounts you follow on mastodon.cloud and ask them to migrate their accounts to an active server.
This is not only to allow them to continue to participate in the fediverse community but also for their own security, as mastodon.cloud is no longer a secure platform.
-
Secondly, their Mastodon software version has not been updated for an extended period of time and has known security vulnerabilities. We do not want to risk any exploits with those vulnerabilities that may affect our users.
An instance that is unmoderated and insecure poses a risk to other servers it federates with. The Fosstodon team did not take this decision lightly, and arrived here after months of observing these issues.
I would expect that to have the same security implications like someone I know with an insecure email provider.
Yes, that might enable bad actors to impersonate my mate, but that does not exposes me to an immediate threat.
Overall, the communication by Fosstodon reminds me a lot of corperate business language.
Monitoring the issue for month to arrive at a 72h notice makes it even more questionable. See https://hachyderm.io/@dalias/116431358768467909
-
System shared this topic
-
I would expect that to have the same security implications like someone I know with an insecure email provider.
Yes, that might enable bad actors to impersonate my mate, but that does not exposes me to an immediate threat.
Overall, the communication by Fosstodon reminds me a lot of corperate business language.
Monitoring the issue for month to arrive at a 72h notice makes it even more questionable. See https://hachyderm.io/@dalias/116431358768467909
@ghost_letters @fosstodon fosstodon provides a free service. They have to manually moderate users and spammers from mastodon.cloud. It creates a lot of work for them to not defederate.
-
@ghost_letters @fosstodon fosstodon provides a free service. They have to manually moderate users and spammers from mastodon.cloud. It creates a lot of work for them to not defederate.
No doubt about that part. My reply was aimed at the second post that talks about security implications.
-
I would expect that to have the same security implications like someone I know with an insecure email provider.
Yes, that might enable bad actors to impersonate my mate, but that does not exposes me to an immediate threat.
Overall, the communication by Fosstodon reminds me a lot of corperate business language.
Monitoring the issue for month to arrive at a 72h notice makes it even more questionable. See https://hachyderm.io/@dalias/116431358768467909
@ghost_letters @fosstodon I agree. 72 hours is not enough time. People aren't setup to "evacute" a server in that little a time.
-
Again we encourage you to reach out to any accounts you follow on mastodon.cloud and ask them to migrate their accounts to an active server.
This is not only to allow them to continue to participate in the fediverse community but also for their own security, as mastodon.cloud is no longer a secure platform.
@fosstodon Those on that instance need more than 72 hours to evacute. We need a hair more pragmatism.
-
@fosstodon Those on that instance need more than 72 hours to evacute. We need a hair more pragmatism.
Their accounts won't cease to exist after 72 hours, they simply won't be able to communicate with people on the fosstodon.org instance. I suspect that a number of other instances have already defederated them or will do so in the near future.
People on that instance will be able to migrate their accounts for as long as it continues running. Of course there's no knowing how long that will be.
-
@ghost_letters @fosstodon I agree. 72 hours is not enough time. People aren't setup to "evacute" a server in that little a time.
@adventure_tense @ghost_letters @fosstodon they can restore relationships later whenever a user migrated elsewhere tho
-
R relay@relay.mycrowd.ca shared this topic
-
@fosstodon Those on that instance need more than 72 hours to evacute. We need a hair more pragmatism.
@adventure_tense @fosstodon If you’re checking your account regularly I’d offer that 72 hours seems fair. If you’re not checking it recently I think that is on the user.
-
Again we encourage you to reach out to any accounts you follow on mastodon.cloud and ask them to migrate their accounts to an active server.
This is not only to allow them to continue to participate in the fediverse community but also for their own security, as mastodon.cloud is no longer a secure platform.
@fosstodon what's the easiest way to list all accounts I'm following on mastodon.cloud ?
