Would you like some pie? Check it out here: https://piefed.ca/
What is PieFed
PieFed follows a similar format as Lemmy and Mbin. Those that are familiar with Lemmy will find it very similar, with some additional features including topic lists, optional private voting, new mod and admin tools, crosspost de-duplication, community wikis, etc. Thanks to how the fediverse works, you can use either lemmy.ca or piefed.ca to interact freely!
We will put together some guides on our non-profit's website at some point. In the meantime, we have created !newtopiefed@piefed.ca for us to learn from each other. There is also the official !piefed_help@piefed.social community which has a similar purpose.
We have done some testing and we are learning as we go, but please bear with us while this new platform gets going 🙂
Other Links & FAQ
- lemmy.ca is not migrating to PieFed. We will run both instances at the same time. You can use whichever one you prefer.
- Learn about the differences between PieFed & Lemmy: https://join.piefed.social/features/
- A tour of the community moderation features in PieFed: https://piefed.social/post/844065
- One of the first mobile apps to implement support for PieFed, with more to come: https://interstellar.jwr.one/
Excellent work folks!
The true power of federation showing itself here. In this case, it's two software packages with the same server/admin team -- which basically future proofs both.
I'd make a recommendation: have some sort of cross-pollination tool. Basically, pull the database of all subscribed communities on Lemmy.ca and have a bot subscribe to the same on PieFed, and vice versa. Probably easy to do if you have server-side access.
Furthermore, in the ideal world, "Local" from the Lemmy instance includes the piefed.ca local commuities. This might be a harder ask. The reason would be to prevent bisecting the Local feeds.
Finally, ideally there is a community migration tool, to cross between Lemmy and PieFed if a community wants to move from one side to the other. This would be a bigger project, but would future proof Fedican even further should either piece of software become badly maintained.
Well, okay, I just created a year's worth of work for a programmer. How can I help?
This is actually somewhat built into PieFed. Users can import from a lemmy account, and admins can do a bulk community import of the local communities on a particular instance (filtering by number of posts and users in the past week in those communities). However, it's buggy. Eventually it would be nice to have tools to synchronize administration between the instances so that we don't need to repeat actions on both instances.
Agreed :) PieFed does have a 'popular' feed, so another solution would be to have a default feed that we have more control over (ex. picking specific instances or communities). As long as the exact breakdown is communicated to the user, perhaps as a 'learn more' button in the existing "Create an account to tailor this feed to your interests.", I don't think people will mind the admins customizing it to fit the instance. We've discussed in the past whether it is better to have the default logged out view be 'local' or 'popular', and this might help with that problem too.
This actually exists for the Lemmy -> PieFed direction! @blaze posted some information about it here: https://lemmy.ca/comment/16976004
It could be better, since right now while the PieFed instance does get a copy of all the posts, the Lemmy instance doesn't know about it. Hopefully the various platforms can coordinate some common solution.
Also happy cake day! 🥳
Whoa! Cakeday on Lemmy! Thanks!
Also, great notes! :D
Yeah, I noticed that the option "local" is pretty much empty on piefed.ca I wonder if we create the same communities there and group them together would work.
Here is their repo, https://codeberg.org/rimu/pyfedi/issues I imagine you can propose some of those ideas there.
I think one of the problems on migrating users right now is how lemmy stores password compared to piefed. https://codeberg.org/rimu/pyfedi/issues/712 - But technically, it should work if you ask the user to write a new password.