The more and more old servers I see close, the more intolerable it is that Mastodon still doesn't offer a way to migrate data like posts to new accounts.
-
The more and more old servers I see close, the more intolerable it is that Mastodon still doesn't offer a way to migrate data like posts to new accounts. A user's post history is valuable, and it's more valuable the older the account is. Users *should* have the option to migrate those to a new server!
I think for many users, if they lose their posting history when moving to a new server, they have less reason to stay here instead of moving to a new network. If they're losing everything anyway, why not move to bluesky or something else?
-
I think for many users, if they lose their posting history when moving to a new server, they have less reason to stay here instead of moving to a new network. If they're losing everything anyway, why not move to bluesky or something else?
I'm thinking about this because I saw a Mastodon server of eight and a half years shutting down, which is leaving its migrating users in a very awkward position if they have years' worth of posts that are being lost.
It's not, to be clear, the server admin's fault - they don't control Mastodon's feature set. It's squarely the responsibility of Mastodon to supply the server migration tools necessary to resolve these problems for its users.
-
I'm thinking about this because I saw a Mastodon server of eight and a half years shutting down, which is leaving its migrating users in a very awkward position if they have years' worth of posts that are being lost.
It's not, to be clear, the server admin's fault - they don't control Mastodon's feature set. It's squarely the responsibility of Mastodon to supply the server migration tools necessary to resolve these problems for its users.
@misty ya, overall account migration needs work esp around adversarial admins or sudden shut offs.
this is not helpful but that said re post data i’m kinda leaning towards opposite in that i feel it’s maybe healthier that this is a somewhat ephemeral medium?
if your server dies repost your faves and let The Archive handle the rest kinda vibe
-
@misty ya, overall account migration needs work esp around adversarial admins or sudden shut offs.
this is not helpful but that said re post data i’m kinda leaning towards opposite in that i feel it’s maybe healthier that this is a somewhat ephemeral medium?
if your server dies repost your faves and let The Archive handle the rest kinda vibe
@misty this thought is informed by when i wanted to migrate off xitter and i got all of my post data and i thought of hosting it somewhere but
i came to the conclusion that i myself could not be arsed to read through thousands of dumb tweets to pick out the good ones & the risk of hosting a convo i would now regret seeing was not worth it
-
@misty this thought is informed by when i wanted to migrate off xitter and i got all of my post data and i thought of hosting it somewhere but
i came to the conclusion that i myself could not be arsed to read through thousands of dumb tweets to pick out the good ones & the risk of hosting a convo i would now regret seeing was not worth it
@misty (i’m not trying to contradict the feeling you have & rightfully point out that people care about this stuff! more a reflection of an epiphany i had where i realized that i didn’t care about it as much as i thought i did)
-
@misty (i’m not trying to contradict the feeling you have & rightfully point out that people care about this stuff! more a reflection of an epiphany i had where i realized that i didn’t care about it as much as i thought i did)
@phillmv Ywah, I think that’s a valid perspective. I have a bit of a knee jerk reaction to it mostly because the conversation thus far has been dominated by people with that perspective arguing that as a result the migration option *should not exist at all, for anyone, even as a choice*, and that’s led to the current situation where Mastodon doesn’t allow it. I think it’s totally fine for post migration to be opt-in but there’s enough people with post histories where it matters it should exist!
-
@phillmv Ywah, I think that’s a valid perspective. I have a bit of a knee jerk reaction to it mostly because the conversation thus far has been dominated by people with that perspective arguing that as a result the migration option *should not exist at all, for anyone, even as a choice*, and that’s led to the current situation where Mastodon doesn’t allow it. I think it’s totally fine for post migration to be opt-in but there’s enough people with post histories where it matters it should exist!
@phillmv I run my own server so I’m not vulnerable to unexpected shutdowns, thankfully. But my own post history does have plenty of things I actually would want accessible from the same server I’d continue posting to after moving.
I could do that on GoToSocial or, ironically, Bluesky. But it’s simply not an option on Mastodon.
-
I'm thinking about this because I saw a Mastodon server of eight and a half years shutting down, which is leaving its migrating users in a very awkward position if they have years' worth of posts that are being lost.
It's not, to be clear, the server admin's fault - they don't control Mastodon's feature set. It's squarely the responsibility of Mastodon to supply the server migration tools necessary to resolve these problems for its users.
You know, the other thing I'm thinking is: as a community, we keep telling people to stay off mastodon.social. But if you signed up for mastodon.social in 2016 or 2017, it's one of the only options available that would still be working today with your full post history intact. If you signed up anywhere else, you've *probably* been through multiple migrations and lost your full posting history several times over.
-
You know, the other thing I'm thinking is: as a community, we keep telling people to stay off mastodon.social. But if you signed up for mastodon.social in 2016 or 2017, it's one of the only options available that would still be working today with your full post history intact. If you signed up anywhere else, you've *probably* been through multiple migrations and lost your full posting history several times over.
If we want users to sign up on non-mastodon.social servers, we *need* to make server migration actually, genuinely painless and make it possible to actually bring over *all* of your account's content if you want that. Otherwise, "just use mastodon.social" will continue to be the lowest-risk option and picking another server will actually be riskier.
-
undefined Oblomov ha condiviso questa discussione
undefined gabriele renzi ha condiviso questa discussione
-
If we want users to sign up on non-mastodon.social servers, we *need* to make server migration actually, genuinely painless and make it possible to actually bring over *all* of your account's content if you want that. Otherwise, "just use mastodon.social" will continue to be the lowest-risk option and picking another server will actually be riskier.
@misty I've been thinking about this since my first server change, and what I realized is that the biggest obstacle to this isn't even Mastodon's lack of support for it, but a huge limitation in the ActivityPub protocol itself: objects IDs must be “a publicly dereferenceable URIs [...] with their authority belonging to that of the originating server”. So even if the content would be copied over, all threads and references would still become invalid 8-(
1/?
-
@misty I've been thinking about this since my first server change, and what I realized is that the biggest obstacle to this isn't even Mastodon's lack of support for it, but a huge limitation in the ActivityPub protocol itself: objects IDs must be “a publicly dereferenceable URIs [...] with their authority belonging to that of the originating server”. So even if the content would be copied over, all threads and references would still become invalid 8-(
1/?
@misty it would still be better than a total loss, but still catastrophically incomplete.
I can envision this being fixable with some kind of “object move” that servers recognize so that they can edit the in-reply-to etc to keep threads intact, even though plain URLs inside would still be broken.
Or maybe we need some other kind of “global derefernceable IDs” for the objects? Do the FEPs for nomadic identities support something like that?
2/2
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@rbreich
Trumpism
-
@ntnsndr fantastic news, congratulations - and thank you for that service to the community.
-
@Ryoma123 @LaVi @bianot magari in anagrafe son fancazzisti e non fanno niente, però c'è il divieto di dare nomi che “arrechino pregiudizio morale”, lo stesso nome del padre o dei fratelli (adesso il divieto potrebbe essere per lo stesso nome della madre, se la figlia prende il cognome della madre), e in teoria dovrebbe essere vietato anche dare il nome uguale al cognome
poi magari, appunto, chi c'è in anagrafe quel giorno non ha voglia di fare storie e lo accetta, ma facendolo non ha fatto il suo lavoro
-
@matz darebee è veramente ben fatto 😊
-
@eccosilvia molto, mi piace anche il suo modo di porsi. Dice esattamente le stesse cose di Gratteri.
-
@ro Vedi ? Categorico e chiarissimo. 😁
-
Per gli amanti delle ferrovie e i curiosi in generale, ecco come si fa a controllare i binari, le infrastrutture ecc. per mantenerle in sicurezza. Molto bello, il treno Diamante 2.0 !
https://piped.casasnow.noho.st/watch?v=g7o9lA4Oro0?feature=shared
-
It has been the honor of my work life to serve the people of Colorado as a professor at CU Boulder, and to have my colleagues' support—today, with a medal recognizing tenure. I'm wearing a sweater from my grandfather, an earlier Prof. Schneider.
