• 16 Posts
  • 66 Comments
Joined 8 months ago
cake
Cake day: November 20th, 2024

help-circle
  • Just to add on to this, the web ui for piefed is the native client and basically every feature comes to the web ui first. The api that other frontends/clients is very much a work in progress and only exposes a subset of piefed’s features (so far).

    In addition to this, these other clients are basically only using the same api routes that lemmy has since that is what they were designed for. So, they don’t really have many (or any) features that are piefed-only.

    Edit: The PWA for piefed is quite usable and I have put a lot of effort into the UI changes I have contributed to make sure that the interface reacts well down to small screen sizes. So, give that a shot to get the full piefed experience.








  • I get it…

    When you read manga, you can go at your own reading pace and fly through a story. So, a plot point that drags on and on doesn’t feel as painful (the exception is if it stupidly drags on past the point of plausibility…looking at you Rent a GF). However, the anime format makes you sit through the whole thing, warts and all.

    Your point about flashbacks I have found to be less of a problem in recent seasonal stuff. Flashbacks are pervasive in shows that are continuously airing during their run (Pokémon, One Piece, Naruto, etc). Usually, the flashbacks are a way to take up time and save animation budget. However, shows that just run for 12-24 episodes and wrap up do this a lot less.

    If you want to see a show that does flashbacks the right way, I would point to Frieren, where flashbacks add new things to the story.
















  • I could see this maybe being useful at a moderator or admin level to aid in moderation decisions, but I feel like the average user wouldn’t really gain much from this information in exchange for a more complicated UI.

    Just as an aside, in the dev chat we have been talking about this a lot and the UI has been one of the harder pieces. The main competing paradigm for the UI of this feature is to have two upvote and two downvote buttons (one set for public votes and another for local-only votes). Here is a mockup I made of the voting buttons for that:





  • Is this where that happens? I am having a hard time untangling all the AP stuff in the codebase.

    For what it’s worth, I don’t think this is the case any longer. I have been spinning up new dev instances a ton with docker and the trusted instances list is empty. The one place that piefed.social is listed in the admin panels I found is in the “Warn if new account banned from these instances” box:

    I have been on a bit of a mission to try to make a lot of the more opinionated moderation tools in piefed optional at an admin level or remove them (so far rimu has been receptive). So, if this is in the code, I would want to make a PR to remove it.



  • Edit: In addition to what I write below, there were huge issues with Cloudflare today (which a lot of instances, including piefed.social, use as a WAF).

    Are you talking about piefed.social specifically or a different piefed instance?

    There was a bug with federation of moderation actions for some time today. There wasn’t a codeberg issue made due to the potential sensitivity of it. That should be fixed now though. (Huge shout out to the user that reached out about it directly). I don’t know the details of the issue/fix, but it is possible it was impacting other federation activities as well.


  • The scale of LW is impressive as always.

    Is the post_read table where info on what a user has or has not read is stored? I am wondering now if a huge db like that is the cost of implementing features like marking unread comments or posts.

    …not that I have a great idea of how to do that since I don’t know js at all, but db size is something to keep in mind when the intention is to have federated instances, each with their own infrastructure.