Conversation
Notices
-
Embed this notice
voltrina (voltrina@pl.voltrina.net)'s status on Thursday, 23-May-2024 03:16:39 JST voltrina given my current circumstances with hosting and being stuck on a practically abandoned pleroma fork, i might migrate to den.raccoon.quest
i wish there was proper misskey mobile clients and that the web UI wouldn't use so much battery though-
Embed this notice
iced depresso (icedquinn@blob.cat)'s status on Thursday, 23-May-2024 03:16:37 JST iced depresso @voltrina you might be able to get an adminblob to help you migrate to akkoma or mainline pleroma maybe? -
Embed this notice
iced depresso (icedquinn@blob.cat)'s status on Thursday, 23-May-2024 03:20:38 JST iced depresso @voltrina i think you have to specifically ping them but one of them might be bored enough
@sun @p @j @hj
i don't remember if lain still does any of this. -
Embed this notice
voltrina (voltrina@pl.voltrina.net)'s status on Thursday, 23-May-2024 03:20:40 JST voltrina i hope so, i'll reconsider my decision if someone pops up here
i have switched between *oma forks multiple times in the past without rolling back database migrations on my old instance, but it eventually caused the instance to break as soon as i had to install a update that required database migrations -
Embed this notice
Christmas Sun (sun@shitposter.world)'s status on Thursday, 23-May-2024 03:37:34 JST Christmas Sun @icedquinn @j @p @voltrina @hj I've never done it -
Embed this notice
iced depresso (icedquinn@blob.cat)'s status on Thursday, 23-May-2024 03:56:20 JST iced depresso @dushman @voltrina misskey too battery hongers was the complaint -
Embed this notice
Dushman (dushman@den.raccoon.quest)'s status on Thursday, 23-May-2024 03:56:23 JST Dushman @voltrina@pl.voltrina.net
I mean you can just install it as a web app with like any browser on mobile -
Embed this notice
(mint@ryona.agency)'s status on Thursday, 23-May-2024 18:47:20 JST @p @j @icedquinn @voltrina @hj @sun Nukie's instance was successfully migrated from ackoma to pleroma without any issues (aside from the usual need to purge DB config). One just needs to revert DB migrations to the point where they diverged. narcolepsy and alcoholism :flag: and Christmas Sun like this. -
Embed this notice
pistolero (p@fsebugoutzone.org)'s status on Thursday, 23-May-2024 18:47:21 JST pistolero @icedquinn @voltrina @hj @j @sun
> i think you have to specifically ping them
In my case, yes.
> switched between *oma forks multiple times in the past without rolling back database migrations
Just switching FSE from develop to stable required me to jump through some DB migration hoops.
I don't know that you can jump databases from soybox to Pleroma directly: there are gonna be dups that are named differently, there are going to be other conflicts. Usually, the easiest way to do this is hop domains, but the "correct" way to do it would be to revert all of the migrations that happened before the fork, then switch codebases, then run the new migrations. In theory, they'll all apply cleanly, but it is often not the case, since the older databases tend to be the bigger ones and this means they're much harder to test. (FSE's 500 gigs, there are migrations that would take actual days.) -
Embed this notice
pistolero (p@fsebugoutzone.org)'s status on Thursday, 23-May-2024 19:16:35 JST pistolero @mint @hj @icedquinn @j @sun @voltrina Yeah; as noted, sometimes that doesn't play as cleanly as you might hope. and narcolepsy and alcoholism :flag: like this.
-
Embed this notice