#QOTO #Question - Moving to another server problematic?
If moving to another server will there likely be problems on new server since they will have character limit less than what we have here? - also previous attachments would probably be bigger too...
so if importing all posts from exported backup - what could you see as problematic on new server ? (or maybe new server will just ignore / cut off what is too much?)
@freemo Don't mind losing some stuff, so why do you think I can't move at all and do you mean just right now at this time of updating or do you mean just usually it's not possible because of QOTO differences to standard instance installs? Thanks
🇳🇱
@freeschool its a bug two people expierenced since our migration. Not even sure if it will effect you or not. I suspect it will get fixed in the 5 updates we currently have in the pipeline.
@freemo So normally how would it be exporting backup from ours and importing to other servers considering the allowances here are more than most other places?
@freeschool mastodon never supported the migration of your posts. It isnt an incompatibility thing, you cant do it at all. Migrations move your followers only
@freemo So is it right to say: It's possible to archive one's own posts/toots via https://qoto.org/settings/export
but one cannot take those / import those elsewhere?
@freeschool im not sure if the export function exports your toots at all off hand. But you are correct that there is no way to import toots and likely neverwill be due to the spam that would be produced if you did
Exported Messages Archive (.tar.gz) ?... any ActivityPub software that can read exported archive? (Exporting messages / toots to archive and reading it elsewhere)
@freemo A quick visit to settings/export page or https://qoto.org/settings/export tells me yes, toots are included.
So I wonder maybe what "compliant software" exists to read this *.tar.gz archive...
Settings/export page says:
"You can request an archive of your toots and uploaded media.
The exported data will be in the ActivityPub format, readable by any compliant software."
The setting/export page has also personal details showing user what is for for archive (I assume all of it or perhaps CSV lists marked below you have to do manually)
Media storage 1 GB
Toots 1111
Follows 1 CSV
Lists 1 CSV
Followers 1
You block 1 CSV
You mute 1 CSV
Domain blocks 1 CSV
(1's in stats are just for example)
❓ Question is about Exporting messages / toots to archive and reading it elsewhere somehow.
Even just text without media.
I'm not a programmer but could follow some steps if tested by someone to work or program made.
No idea off hand what can read it. I suspect its some structured text and can be open in a text editor once decompressed, just a guess.
All i know for sure is you cant import toots and likely never will be able to. Its been discussed many times and due to the nature of AP it will not be possible in a way that doesnt cause spam.
"Activity compliant software" for Archive Data (JSON) export ?
@freemo An archive from 2018 (which I left Fedi from frustration) was similar .tar.gz compressed file with a .tar file inside (so another compressed file) and then uncompressed that has JSON* files inside as listed below...
actor.json
avatar.png
header.png
likes.json
outbox.json
*not sure if names of things have changed since then and seemingly didn't have any media saved - hmm...
Regarding potential spam on any importing (if you could) - Yeah I was thinking how the spam would be managed, but then I thought simply "how about muted import?" so imported posts would show but unannounced (seems possible but perhaps not across all software).
But overall anyway I assumed INcorrectly and was wrong - so you can't move posts at all top another server and perhaps only save them locally and read them by "Activity compliant software"... wherever / whatever that is!
❓ Anyone have a clue about "Activity compliant software" ❓
#FediHelp #Mastodon #Fediverse #Help #OpenSource #FLOSS
#QOTO #Question
If import were muted then no one could really see your toots outside of the server you were on.
The reason is servers see toots cause thry get pushes, thry dont pull them in.
Those files wont be able to be imported by any software, they are just dumps of the AP endpoints judging by the names.
@freemo
The outbox.json had the sent messages a bit like an email outbox file and fairly readable in plain text / without tools as one long scroll.
Would be nice cleaned up by a small tool / program. ⚒️
And about importing post theoretically in future (Sorry muted was wrong word and it still might be an incomplete idea) I meant posts are added "unlisted" and only when people look at profile they would they see or could search in future (if feature existed)... if not probably all servers adding a flag to say "all these posts are being imported" so "ignore in these way" but yeah if that doesn't work and is not close to workable, skip this idea.
@freeschool even if you add them unlisted... if you have followers it will spam tbem. If you dont no one will ever be able to see them (since you cant see messages from before a server wide follow). So even then imports wont be possible.
@freeschool the outbox json is literally the raw endpoint youd see if i pointed at the AP API btw...
Check out my blog with AP support as an example:
curl -H "Accept: application/activity+json" -X GET https://jeffreyfreeman.me/outbox.ajson
Exported Messages Archive (.tar.gz) ?... any ActivityPub software that can read exported archive? (Exporting messages / toots to archive and reading it elsewhere)
This is how to compile `outbox.json` with `jq` to an array of posts that have the `published` date and its `content`.
```
jq '{ data: [.orderedItems[] | {published: .published, content: (.object | objects | .content // empty) }] }' outbox.json > content.json
```
(remark: not a jq expert, thus this could probably be simplified)
@freeschool
If you migrate to a new server you can not move your posts at all. And you will loose a large portion of your followers (20%+). You will loose a similar portion of those you follow.
So most of your concerns are nonissues.
Also keep in mind migrations seem bugged for 2 people right now so you may not be able to migrate at all until we finish our update process which shouldnt be too much longer