(mint@ryona.agency)'s status on Sunday, 01-Jan-2023 07:40:52 JST
@adminVEVO Why then keep a fresh empty instance on an old domain? IPs don't match either, something is fishy. >i thought it would fuck up federation + following relationships or something Reasonable concern, though I think if you resend follow request to an user who already accepted it, it should go through fine, at least on Pleroma and in case of non-locked profiles (at the very least it was the case for me when Nekobit moved back and forth between domains).
@adminVEVO >(compatible; Pleroma 2.5.50-194-g00ebaee6-ryona-dev) Huh. I think I've explicitly warned against using my fork for third-parties, but this warning got lost with the rest of kiwigit. There's zero quality control, I merge shit in master branch to test and then fix it as I go on. Expect everything to break if you update it at the wrong time. If you've gone with it because of custom reacts, consider Eientei's fork instead, Yukkuri maintains a better workflow in that regard. https://gitlab.eientei.org/eientei/pleroma https://gitlab.eientei.org/eientei/pleroma-fe
@mint@adminVEVO > There's zero quality control, I merge shit in master branch to test and then fix it as I go on. Expect everything to break if you update it at the wrong time.
Unfortunately it is the same for eientei as well, changes in eientei branch can be in WIP state, while being tested on feditest*.eientei.org mock instances. Changes that make to eientei main instance are relatively tested, but nothing is perfect.