- cross-posted to:
- newcommunities@lemmy.world
- cross-posted to:
- newcommunities@lemmy.world
With a 10:3 ratio in support for migrating the community off of lemmy.world as suggested by @Blaze@sopuli.xyz in this post, we will run a trial period of migrating the community over to !football@lemm.ee
Trial period
We will run a trial period of 2 months on lemm.ee to see how stable the instance is. Since all of you who discussed potential instances only had good things to say about the instance, expect the trial period to just be formality though.
Locking down football@lemmy.world
The FootballAutoMod has been configured to automatically lock down any new posts and tell the posters to repost in the new community. While I could lock the community completely, I think this solution might help inform those of you who maybe don’t check in on the community regularly.
Why lemm.ee
It’s a moderately large EU-based instance with little to no drama as far as I know. The admin team seems to be competent and maintains a neutral stance with few defederations across the fediverse. The instance also got multiple recommendations amongst our users.
I was just about to say this is the first I’m hearing of this and I have serious reservations about this idea, because moving communities is always tough.
But then I saw the automod tag everybody, and that’s a really nice solution you’ve come up with. I would say maybe send out a few more pings over the next couple months and also post about it on !newcommunities@lemmy.world, just to make sure that everyone gets the message.
Assuming that most users hear about this and subscribe, I think lemm.ee is a great choice for a new home.
Assuming the FotballAutoMod works fine with the code I’ve pushed, anyone who posts to this community now will have their post locked + a reply from the AutoMod that the community has migrated. Hopefully it will work well.
Just tried, nothing happened 😅
Yeah, found the bug.
If you’re curious about the details. When the script gets the list of most recent posts from lemmy, pinned posts are at the start of the list. Since I had the script break the loop once it discovered a post older than last time it checked for new posts, it would always break the loop on the first post since the migration post is pinned. Should be fixed now.
Great, thanks!
I want to try ha ha
Very interesting