Likely Saturday, 1st of November.
We need to do some server OS upgrades and a some other things that will cause a few hours downtime.
Maybe I will already start with some smaller things this week, that should only cause a short down-time for reboots.
Once that is done, I will look into running a Piefed test instance to investigate how to do the database migration from Lemmy. If everything goes smoothly, we might be able to do the Lemmy to Piefed migration end of this year or early next year.
Hi, tourist to slrpnk here. Just caught this. Cool to see you’re planning to move to Piefed, but what does “hardcode lemmy.ml as a source to pre-fetch popular communities” mean in practice. I did Matrix you, so sorry for double-ping (I just discovered you were in the piefed chat) but this seems like quite an outrageous concept.
It is an attempt to pre-populate new instances with some popular communities which is seen as a way to improve discoverability. I find the general concept of using “popularity” for that to be somewhat problematic, but the main issue I have with the actual implementation is that it uses lemmy.ml as the source of truth for that, and there is no way to change that*. I have since learned that it is possible to entirely turn off that new feature and thus have the current behavior, but then you basically have the choice between two bad options and it feels like malicious compliance to a request to improve discoverability.
*the dev explained to me on the Matrix chat that there are some technical reasons for that, but it reeks like a convenient shortcut to a difficult problem, that causes more harm than good.