Moved from one piefed instance to another, exported/imported settings, nothing happened
To be precise: I used the export feature on piefed.zip. The resulting .json file seems to contain all my blocks and other settings but as far as I can see (I already started manually adjusting some basic stuff) nothing actually got imported, and there was no error message.
It said that it could take a few minutes, but that was yesterday.
15 replies
There's a bug in the export / import where the 'user notes' (the little emoji or text you can tag other users with) uses a different json structure. Lemmy does not have user notes so it's not included in exports from them.
If you look at the json file and do a find for
"note":and replace with"body":that'll fix it.A proper fix will be in v1.8, out soon.
Thanks, that fixed it (a page reload is required).
Not sure I understand why you mentioned Lemmy, but I moved between 2 piefed instances.
BTW, just now when I logged in I got the onboarding wizard which for some reason I did not get before.
And it wasn't me who chose your replied as "prefered" or solution.
Weird.
🤔 is it possible that cookies & local data from 2 piefed instances interfere with each other?
There is a flag saved in the database once you go through the onboarding so that you aren't shown it a second time. For some time there was a bug that prevented it from showing up at all that was recently fixed. So, some users are seeing it for the first time well after they initially created their account because they were (wrongly) not shown it originally, but it is being properly shown now. After going through it once, you shouldn't ever see it again though.
Community moderators and admins are also able to flag a comment as an answer.
This is something that is primarily handled by the browser in a session cookie. There shouldn't be any cross-pollination between domains. FWIW, I currently have 10 PieFed accounts logged in on 10 different instances (plus 3 lemmy accounts and 1 mbin account) and have never had any issue with cookies interfering with each other.
What are the practical differences between piefed.zip and piefed.social? I registered on .social because I just like the vibe, but other instances also look nice.
I decided to switch because they started using cloudflare and I kept getting "Are you human" bs more and more often.
.social is the original I think and gets updates soonest in general. I think .zip has been recommended to me as having minimal defederation and blocking and such. Philosophically I should change but honestly rimus decisions jive with mine so I have been to lazy to move over for technicalities.
piefed.zip is currently on PieFed v1.8.0-dev
piefed.social is currently on PieFed v1.7.17
yeah I had no idea an instance was using a dev branch. basically I came in early on and even at that time there was something that warned that .social was more likely to be unstable getting stuff. it sounded like it was like it was used a bit like staging (I said dev at one point and got the grief). Kinda like new prod versions were immediately put on it and then formally uploaded as the new prod. things may have changed since then.
I think the main ones would be that we don't use vote quota and I think we might have fewer defederations
.social is the piefed flagship instance, so it gets updates first. We try to keep .zip more or less up to date, RL permitting
piefed.zip is currently on PieFed v1.8.0-dev
piefed.social is currently on PieFed v1.7.17
But I find that a little confusing; I cannot find "1.8.0-dev" on pyfedi's codeberg.
That's just because when updating we pull from main instead of keeping to the tagged versions. I do have a plan to have a script replace that string with the hash of the topmost commit we pull. But I want to finish some other tooling first. Effectively .zip currently is on 1.7.17+one commit
I did find 1.8.0-dev in the code meanwhile, so yeah, it's just the main branch's latest commit, not release.
That's all I found confusing; don't change it for me!
I did a quick peek into the logs and found the server-side error that is hanging things up. I don't really have the bandwidth to get a quick fix in, but it isn't anything you are doing wrong. I think rimu should be able to pop a fix in soon.
Funnily enough, it seems like the error is something that can only happen when migrating from piefed -> piefed...the lemmy -> piefed migration path is used a lot more often, so there have been more chances for problems to surface in that scenario.
Yes I thought it could've been something like that.
piefed.zip's cloudflare protection is singling me out more and more often. I hope you never go down that path here.
You might want to check the API response directly via the developer console if you haven't already.