Skip Navigation

What features are missing from piefed, or, why aren't we reccommending piefed instead of lemmy?

Every time I go to the piefed frontpage I'm blown away by how much more polished it is. It has all the bells and whistles that lemmy is sometimes missing.

Whats the catch? Why aren't we recommending everyone goes to piefed instead of lemmy?

App support is one thing I can think of.

158 comments
  • We have data on what it costs to run a sizeable instance of Lemmy and it's not a lot. How does Piefed compare? Anyone starting an instance who envisions it growing large has to contend with this question. Currently it seems it's got a bit under 1000 users across under 10 servers.

    There are now sizeable communities run on Lemmy instances that are reinforced by network effects. There needs to be a significant reason for them to migrate. To that point, the collective project is building communities away from corporate power, not software. The software is a tool to facilitate that. Lemmy has worked well so far in this regard. If someone can show that Piefed can work better and not cost significantly more, it'll probably get adopted for new communities. If the difference is drastic, we may even see migrations from Lemmy.

    • We won't 100% know the answer to that until we get there. But in 2025 fear of a lack of CPU cores is NOT what keeps me awake at night.

      Early performance results are positive. Check these links out:

      https://join.piefed.social/2024/02/13/technical-performance-of-each-fediverse-platform/

      https://join.piefed.social/2024/02/09/comparing-network-utilization-of-lemmy-kbin-and-piefed/

      There are many many ways to ruin web app performance and choice of backend language is not really a big one. It's what you do with it that counts.

      https://piefed.social/ is running on a low end VPS which costs $7.50 per month. Load average is about 1.45 during the busiest part of the day. Most of the load is caused by federating with lemmy.world and that won't increase as more users come on board.

      PieFed is also really efficient with storage. After 16 months of operation, subscribed to every popular community, the piefed.social DB is 30 GB and the media storage is 28 GB. A Lemmy instance would be 10x that. I haven't bothered to add S3 storage code because we just don't need it (yet).

      Anyway, all this focus on costs and downsides is only half the coin. There are massive benefits that come from using Python:

      • Easy and fun
      • Fast development velocity
      • Huge amounts of developers know Python
      • Extensive and mature libraries with good documentation
      • Good readability
      • Cross-platform without re-compiling

      For a FOSS project where volunteer contributions from people play a big part these things are really important. There are many ways a project can fail (not just technical reasons but social & governance too) and running out of CPU is way way down on the list.

    • I second this. Lemmy is written in Rust where as piefed is written in Python. When it comes to running a high-performance webserver, Lemmy has the advantage.

      • While theoretically true, the main bottleneck with Lemmy seems to be the database performance, so with both projects depending on PostgreSQL for that, I somewhat doubt that Piefed being written in Python will have much noticeable effect in reality.

      • Yeah, this would be my concern as well if I had to run it. Sure Python apps can be fast and most time is spent in IO, not compute, and if you're running a profitable operation the exact cost of compute might not matter much. However if you're running a non-profit service and you want it to be as dirt cheap as possible so it can be free for most users, then the cost of compute very much does matter.

    • We have data on what it costs to run a sizeable instance of Lemmy and it’s not a lot. How does Piefed compare? Anyone starting an instance who envisions it growing large has to contend with this question.

      I don't think this is a major concern yet. The largest PieFed instance has 308 active users, 2nd place has 34. They've got room to grow.

      https://piefed.fediverse.observer/list

      People can start posting about PieFed on Reddit and see how the Reddit users react.

      • But how is that not a concern if you're interested in attracting more users? You run an instance with 500 users. Some thread on Reddit explodes and you get 1000-10000 new users in a few days. If Piefed has poor scaling you might be unable to pay the bills for your now much larger instance. That's not gonna be great for you or the new users.

    • Its written in python, but I don't think the overhead is too much because the bottleneck is DB performance.
      It has support for lemmy's protocol, so the network effect really isn't an issue.

  • I think it's good that PieFed is so small, that means they can move faster and innovate more without fearing that things will break for thousands of people. I think it's good that a project like PieFed can try things and see what works and sticks and this is then a good indicator for projects like Lemmy to copy what is good and leave out what is not good.

  • Generally, because I think all server-centric AP software is broken and I want to see a client-first application to browse the social web.

    Particularly in relation to piefed: it seems to be focused on the exact opposite (giving more power to the server admins) and it takes a good page of social engineering / "nudge theory" principles to guide its design. Much like Mastodon, it seems to be strongly opinionated about how people should behave and it kinda gives me an icky feeling about its culture.

    • It may be a bit opiniated, but it's nice to see a different approach from Lemmy devs who don't see the need for any additional moderation tool.

      I brought up mod mail during the AMA, it has been considered too complex to implement. A moderation panel with an overview of the mod queue would be nice too, but not a priority.

      I'm not saying Piefed is perfect, but at least they prioritize that aspect.

      • "moderation duties" and "regular participants" in a forum system have such different use cases, it makes no sense to try to make it work with the software itself.

        It would be better/faster/easier to simply build a separate tool that can be useful for moderators, instead of trying to shoehorn it in the existing API. But I don't really think that this is something that really bothers people enough, given that last time I asked if I could get 20 people interested to sponsor the development of the moderation tool, and to this day only one person showed up.

      • We are working on new moderation features all the time, for example 1.0 will correctly federate instance bans which is quite complicated to get right. There will also be a plugin system which allows for much more flexible mod tools. Its just that our time is very limited for all the work that needs to be done on a project with over 50k active users.

    • [PieFed] seems to be strongly opinionated about how people should behave and it kinda gives me an icky feeling about its culture

      Yea, I get this same feeling. It's not that I mind that culture or being mindful of how people behave and such - I just don't think that is the domain of the software to decide. Individual instances can decide that for themselves, but the software shouldn't influence that kind of thing, I feel.

    • If only activitypub c2s didn't suck.

      • ActivityPub C2S is not the the solution. It still requires a server and it still keeps the admins in control of everything.

        ActivityPods seems to be going in the right direction, though...

  • I never knew what it was because I'm a bit desensitised to new apps / app names.

    Edit: using https://phtn.app/ has made Lemmy extremely pleasant to use too. I haven't had a better experience on any platform.

  • Do we have to recommand it? Do to the nature of the threadiverse, Lemmy content is available on PieFed and PieFed content is available on Lemmy. It is mostly a matter of chosing an instance. We could surely add an PieFed recommendation to our go to threadiverse instance but is there instance culture there yet?

    Shouldn't we recommand it first to active user, the ones that create and animate communities, the ones that would create new feeds making those instances more alive?

    • @pseudo @Irelephant

      Yes we do have to recommend PieFed. While PieFed is already incredible for what it is able to do, there are some missing key features. So we also need to be honnest about PieFed.

      It is a new software so we need to invite more people to give a try. Once they try, sysadmin may give a go after listening to their user feedback.

      Most active user won't create a community outside their main instance. Do you picture myself using Piefed.social for c/pisourd ? I would lose the benefit of my french speaking local timeline. :)

      And yes, all content are federated but the way community are managed is different. I can show you the inside of tarte.nuage-libre.fr or !fediverse@piefed.social

      Don't you want to give a try ? In exchange i will do a promotion on jlai.lu on any software you want to boost. That one will be the next "tour d'horizon" 😊

158 comments