Piefed contributor and part of the piefed.social admin team.

  • 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: November 20th, 2024

help-circle







  • I can confirm that this is something @[email protected] has brought up in the past on multiple occasions. It’s an issue that I am sympathetic to, but so far it hasn’t been a high priority for us to take the time to try to address. One of the biggest complaints we see people have about the threadiverse in general is that there isn’t enough content; that their feed gets stale too quickly. So, having more subscriptions hasn’t necessarily been seen as too much of a “problem” from my perspective.

    What I did work on was making it easier to unsubscribe from communities. If you filter the communities page to just communities you are subscribed to, it should be a simple matter of clicking the buttons to unsubscribe to undesired communities. It used to reload the page each time, which made that task immensely tedious.

    Frankly, now that Skavau has a third party backing up their position, they will be insufferable about it until we try to fix it 😜



  • I run a personal lemmy instance and two personal piefed instances, so I was just doing some comparisons. My instances are mainly used for development and testing, so they are only subscribed to a handful of communities and just have one active user.

    You are correct that when it comes to performance, like snappiness and responsiveness, the database is probably going to be the bottleneck. Unless you are scaling up to a huge degree, I would be surprised to see meaningful differences in the number of requests that could be handled due to language differences between rust and python. Yes, python is an interpreted language, but most of the libraries you are using are basically calling other system libraries written in a language like C, and the program can execute way faster than your database I/O can give it data to process anyway.

    Here is my usage summary. The lemmy instance has been running for about 1.5 years while the piefed instance has been running for just shy of a year now. I have only included the memory usage and disk since I don’t think either is really CPU hungry or bound in my use case.

    Software Memory consumption Disk Usage
    Lemmy ~1.5 GB ~800 MB
    Piefed ~1 GB ~200 MB



  • More people need to make use of the curation tools available to them in my opinion. Too often I see people browsing /all and then complain about seeing tons of stuff that they don’t like. There are tools that are available to them to help them create a more pleasant experience that they just aren’t using. The fediverse doesn’t have some algorithm that learns the type of content that you most often engage with and feed it to you, you have to more proactively do the curation yourself.

    Just as an example, I was in a conversation with one of the lemmy.world admins a while back. We were talking about instance blocks and how infrequently users actually use them. Across all of the users on lemmy.world, only about 700 of them actually created an instance block for the most-blocked instance (lemmynsfw). Only two instances had more than 500 users block it.


  • In Skavau’s defense, they aren’t a programmer, but are probably one of the most active people on piefed’s chat server/matrix room as well as the codeberg repo providing ideas and feedback. So they are volunteering time that way (in addition to being site staff for piefed.social).

    Some of the ideas in this post are good imo, but are currently not possible yet using the piefed api due to it being much less complete compared to lemmy’s. So, it helps us figure out prioritization on what kinds of endpoints would be useful to flesh out next.