@maxoakland That's not really my own aim, but I appreciate your position. That complexity only exists because of a need to workaround Pixelfed's implementation. Both Slurp and Posty have to actually handle downloading the images from Pixelfed, because it's not included in the export.
11
Replies
17
Boosts
Attention please! (Clears his throat).
Seeing that the Pixelfed.social server was receiving spam and scam accounts, I decided to switch server. Imagine my surprise when I discovered... I couldn't. You can't migrate a Pixelfed.social profile to another instance. Apparently, this has been the case for over a year, by other complaints I've seen.
The lead developer has said something like they're working on fixing it, but it's been like this for a while...
I asked @pixelfed for an explanation several days ago. They've posted things, but they haven't answered to me.
Meanwhile, they've disabled one of the main features of the Fediverse on the largest (and "official") #Pixelfed server.
In other words, they're holding all their users hostage, which goes against the philosophy of the #Fediverse.
What's more, Pixelfed has a function to export your data. However, exporting posts always fails.
I thought, well, at least I can import the people I follow. Nope, because the only import tool they've designed is one for importing your Instagram account. Disabled on the main Pixelfed.social server, by the way.
I even started to think it was because they were one version behind the server I wanted to move to (which would be strange, since it's the main server).
Well, no, they have the same version. But you can only migrate your account INTO Pixelfed.social, not the other way, OUT of Pixelfed.social. That makes the whole thing crystal clear to me.
In short: NEVER create an account on Pixelfed.social, or you'll be held hostage. I recommend another servers (Luzeed, Fotolibre, for example). And there's also @vernissage for sharing photos.
You can all follow me again at this account: @andrewblasco@luzeed.org. Because of course, without account migration, you lose all your followers 🤷🏽♂️
@andrewblasco @pixelfed @vernissage @andrewblasco You can try to use Posty to convert your Pixelfed archive into a Mastodon-compatible one.
https://posty.1sland.social/pixelfed
One of the biggest issues with the Pixelfed archive is that it contains none of your images at all. You actually need to convert it to a Mastodon archive with Posty just to include the actual images (instead of links to the images).
https://writer.oliphant.social/oliphant/posty-for-pixelfed-what-fresh-hell
Edit: Note you can also use Slurp! https://codeberg.org/vyr/slurp#importing-a-pixelfed-archive
@oli Until we fix this complexity, federated social media won't be mass market. And I think we should aim for that
@maxoakland That's not really my own aim, but I appreciate your position. That complexity only exists because of a need to workaround Pixelfed's implementation. Both Slurp and Posty have to actually handle downloading the images from Pixelfed, because it's not included in the export.
@oli "One of the biggest issues with the Pixelfed archive is that it contains none of your images at all." that is... wild.
On that note, other than looking through it yourself, what else can you do with a Mastodon archive?
Is there a way to upload it to a different Mastodon server, or something?
@argv_minus_one @andrewblasco @vernissage @andrewblasco Yes, once you have it, you can via Slurp. That can migrate you to GoToSocial, which lets you import backdated posts and even has a 'gallery' mode.
You can also turn it into a static HTML archive with Posty a little app I created.
I did it here, although my Pixelfed is definitely a test account and hardly has the volume a real production user would.
@andrewblasco @pixelfed hey, @pixelfed this is not cool. #Fediverse
@diraquel @andrewblasco @pixelfed That’s bad customer service. Please reconsider unblocking the user and constructively address the issue. Otherwise, we’ll have to let others know not to trust you.
