Yeesh, reviewing different export formats.
-
Yeesh, reviewing different export formats. I've basically got Mastodon (and its variants) covered. Mastodon, Hometown, Glitch, all basically the same export.
What I hadn't credited Mastodon for, and I guess I should have....
They actually include the media attachments for your posts in the export
This is why the export for Mastodon is a zip file and the export for, say, Pixelfed is a single
.jsonfile.If the server hosting your Pixelfed archive goes down, there go your images, too.
The good news is that I think I can allow Pixelfed uploads and convert them to a standard format, it just means downloading the images from their remote location and creating a local folder structure for them.
Misskey? Holy fuck it's like, "Here's attachments, they have a fileID."
Um.... okay? Let me guess, it's an ID I pass to an endpoint at Misskey to retrieve the image, right?
Let's just say that Misskey archives will be last, if I get to them at all.
But might as well move right along to Pixelfed.
-
Oliphantom Menacereplied to Oliphantom Menace last edited by
Honestly, right after getting your Pixelfed export, you're going to be pretty much forced to use Posty to extract all those images your export didn't actually give you, anyway.
-
Oliphantom Menacereplied to Oliphantom Menace last edited by
I'm just baffled, honestly. That's not an export. Unless all the data is in there, it's not an export.
Unless the intent is that you export it, to immediately import it to a new instance, which can pull over your images via some sort of Pixelfed import api. I guess that would sort of make sense.
But the entire idea of walking away with a static site of your entire Pixelfed experience just isn't a thing. That can't happen, because the images (you know, the most important part of Pixelfed) isn't in your export.
References to them are, but that's not the same thing on a transient web.
-
Oliphantom Menacereplied to Oliphantom Menace last edited by
But for all my puzzlement, I can dig it.... I understand why you'd do that. Downloads of your export are quick, instant, even, and they don't have to "prepare your export" or give you a 7 day waiting period on new ones that way.
And at least they include direct URL references to all your images, so in a worst case scenario that your PixelFed instance is shutting down and you don't want to migrate to a new host, there'd be time to create your export from the hosted data.
Misskey? I feel like I need to learn Misskey first to create an export.
No idea if the other forkeys use the same export format, but let's hope so.
Incidentally, if any *key friends want to tell me WTF the
fileIdreference is supposed to mean for image attachments, that'd be keen.Oh, one other thing:
Misskey and Pixelfed both..... it's just the posts.
Just your posts.
Which, okay, fine, but there's an entire profile, you know what I mean? Where you upload an avatar image and a header maybe and have some bio text and--
WHERE IS THAT?
(In their .json exports? Nowhere, apparently.)
-
Oliphantom Menacereplied to Oliphantom Menace last edited by
Pondering whether I just literally scrape their Pixelfed profile, if it's still up and available.
But then again, if their profile isn't available, their export is gonna be similarly useless without the ability to pull down images.
-
Oliphantom Menacereplied to Oliphantom Menace last edited by
Hey, Misskey, give me your attachments!
Misskey:
....Thanks. Thanks, Misskey.
