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

  • 1 Post
  • 37 Comments
Joined 1 year ago
cake
Cake day: November 20th, 2024

help-circle

  • Growing up in the US, other responders are correct that school systems vary a lot depending on what state/district you live in. Over the course of my K-12 education, I attended 10 different schools across three states because my family moved a lot. There were times where I would switch schools and suddenly be way ahead in some subject and have completely skipped over some other topics. As an example, I never took a course in world history, but ended up having three separate US history courses because the different districts taught those subjects in different grades.

    I do take issue with some of the commenters painting all US schools with a broad brush as terrible. There are excellent schools in the US and excellent school systems. As an example, I currently live in Massachusetts, and if you took it as its own country, it would be one of the best school systems in the world. In general, the states that prioritize education and pay teachers well end up with better educational outcomes. It’s not that surprising really, but a huge portion of the country seems to ignore that fact or spend money in less efficient ways.



  • discuss.online is doing it right. There is a significant overlap between discuss.online and lemmy.world’s admin teams, and I generally think they handle it about as well as could be expected of a general-purpose instance of their scale.

    As for piefed, I think the primary things that help users filter their experience are the additional blocks that are at their disposal; blocking communities with a word in their name, blocking posts that match keywords, blocking posts that point to certain domains, etc. However, it can only help if a user actually goes through the effort of setting them up.





  • The reputation score (sum of upvotes - downvotes) is something that only admins can see. I absolutely agree with a lot of the criticisms people have with reputations systems like this or reddit’s karma, but at the same time, it is one of the most reliable and highest signal to noise indicators of spam/scam/etc. accounts out there. If we were to remove it entirely, it would take away a powerful tool for flagging accounts like that to admins earlier rather than later. Oftentimes, we can spot accounts like that even before they get reported by other users because users are much more likely to downvote/block than go through the trouble of creating a report.

    To address your other reply in the same place, ngrok is not affiliated with X’s (twitter’s) Grok. ngrok is a service that provides https tunneling much easier than manually managing domains. Developers often use this for proof-of-concept stuff or testing features that need SSL because ngrok addresses can be created and destroyed easier and quicker than manually managing your own dns.

    In actuality, I didn’t even realize that ngrok was a sponsor. Or, was a sponsor at some point. Is this still accurate @rimu@piefed.social?





  • Some of the other bigger instances out there federate with one or both just fine

    I mean, the same is true for other PieFed instances. piefed.zip, for example, is federated with both (same admin team as lemmy.zip).

    Like I said, this is inherently opinionated as any kind of defaults would be (themes, colors, user settings, etc.). I just don’t agree that just because an instance is old and active means that it is a positive influence on or provides a positive experience for the average user. Just like I don’t think forums like 4chan should be looked at positively just due to its age and activity. I know there are many that disagree with this, and there is nothing wrong with that.

    Specifically, the piefed.social instance is a bit more opinionated than most other instances out there because rimu has pretty strong feelings about social media. Some of my contributions to the code have been to make PieFed less opinionated or to take some of those very strongly opinionated options/filters and make them configurable or optional at an admin level. So far, rimu has been pretty receptive to this kind of contribution.

    At the end of the day, I am glad that all three threadiverse software platforms exist (people too often forget about mbin) and have been able to maintain a cordial working relationship. They each have different opinions, defaults, and features that might appeal to some users over others.


  • Here is the list of defederated instances when a fresh install happens. This is editable in the admin UI after installation is complete. So, if you really want your instance to federate with the good folks of cum.salon, you are more than welcome to.

    This is really just intended to provide what we think of as a good set of defaults for a typical user. Of course this is somewhat opinionated, just like something like an operating system has a set of opinionated defaults for stuff like default programs, window styling, etc.



  • The language really doesn’t have much to do with things like performance; at least not at the scale that most fedi instances operate at. For PieFed we are using the Flask framework and the overhead of an interpreted language and rendering jinja templates is absolutely negligible compared to the speed of the postgres database. Most of the performance optimizations we have had to make have been related to crafting better db queries or moving things like federation tasks to background workers.

    Might Flask have trouble scaling to the size of reddit? Sure, but I don’t think that we necessarily need to optimize for a use case that may never happen and can also be alleviated by scaling out (more instances) rather than up. I know that rimu is already feeling like piefed.social is too big compared to other PieFed instances and has thought about closing registrations because of it. It is one of the reasons he made the built-in instance chooser, to try to move new users to other instances.

    I wrote more about my thoughts on the pros/cons of python/flask in another comment.






  • 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