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

  • 20 Posts
  • 223 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.


  • Alright, I need to step away to do actual work that pays the bill at this point, but wanted to drop what I found here before doing so.

    • Summit seems to be 403-ing for piefed.social. However, I was able to log in to other piefed sites (feddit.online, piefed.ca, my dev instance) with Summit, so it’s probably just piefed.social I guess?
    • I tried both Boost and Voyager and they were both able to log into piefed.social.
    • I was able to confirm that Summit wouldn’t trip any of the user-agent related filtering in the codebase (to try to keep scrapers out of certain things).

    My guess at this point is that there might be something wonky going on at the infrastructure/WAF-level. If so, then this status quo is going to stick around until @[email protected] can dive into it. My sysadmin skills are not the best when it comes to this kind of thing.




  • It’s unlikely to be an IP ban. Within the piefed software, an IP ban basically coincides with a site ban. At the infrastructure level, your IP may be banned because it was doing some pretty heavy DDOS’ing and got swept up that way. Since your user isn’t banned, try switching between a mobile network and a wifi connection to see if that resolves things since your IP would have changed.

    Are you trying the mobile browser or one of the mobile apps? If it is the mobile browser, try clearing the site data for piefed (cookies, etc.). There have been some cases in the past where a browser’s local cache is not being refreshed properly and weird stuff starts to happen, like the CSRF tokens mismatching and whatnot.




  • Been a bit since I last popped into one of these threads. The main thing that happened recently was that we wrapped up the Anime awards for last year (post here). I definitely need to do some rethinking of how that was run, because participation was way down compared to a year prior. To the community’s credit, there was lots of good feedback in that thread.

    Otherwise, the [email protected] community is getting ready for a new season to come in April.

    My other communities:

    • [email protected] - Has managed to stay somewhat active despite my not being able to read/post much in recent weeks.
    • [email protected] - Not too active since there aren’t any active gundam series going right now. We do get occasional history/lore and gunpla posts though, so that is fun.
    • [email protected] - Pretty dead…but that is to be expected really. The show has ended after not really living up to its own hype and the manga doesn’t really have a consistent release cycle (at least in English), so it has been some time since there is any new content.


  • Yeah, I suspect this is why rimu made the initial version of private communities just local and not federated at all. Once things that are meant to remain private start traveling across the network to other servers, it’s questionable how private that information can remain, especially if other software is involved.







  • 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 @[email protected]?


  • I had a scroll through the recent exceptions thrown by piefed.social and I might have a guess as to what is happening, but I can’t really prove it, and it is rare. I just pushed a fix and backported it to the 1.6.x branch. If @[email protected] updates and this is still happening, then it is some other issue (a stack trace would be helpuful if you are able to grab one). This issue would be separate from the auth issues described by @[email protected]. More technical details below.

    From my sleuthing, there are certain posts that, if they are present in the returned list of posts, will cause the API to throw an exception. This is due to the python library we use to validate our API schema (marshmallow), having too strict of a set of requirements on how urls should be formatted in Url fields of the returned json. I have changed the API schema to just be a string instead so that it isn’t validating against its url requirements.