wjs018

This next month's update will be big. There have been a ton of contributions and even more issues. As lots more people have been checking out piefed and spinning up their own instances, they have been helping identify lots of issues that have been lurking.

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.

If you know rust, then you can take a crack at it.

😉

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.

...diligently taking notes...

I am going to take a closer look at this.

It's a different piece of fediverse software, like lemmy or mbin. Users on a piefed instance can subscribe to lemmy communities and vice-versa (like you commenting on a piefed community/post). See here for more info.

It should work in comments too. || Like this! ||

Yeah, I think this is doable. I recently did something very similar when I added the oldest first sorting. The only tricky bit would be getting the list of just moderated communities, but there is a function for that iirc.

Honestly, finding a spot for it the UI and making sure it's responsive might be trickier.

Also, is there a way to pass a fedilink to resolve, like Lemmy resolveObject?

I don't think so yet...I think this issue is tracking it.

I can't really help with the others, but you might want to hop on the piefed matrix chat (#piefed-general:matrix.org). @[email protected] hangs out there and would have much better answers (during kiwi hours anyway).

So, I have opened a PR to add this sort option for comments (give it a day or so for rimu to review it). Piefed doesn't yet have a user setting for default comment sort (only default post sort). So, the comments will still load initially with the Hot sort.

Here's an image from my dev instance:

Hey, wanted to follow up on this and let you know that spoiler flairs are now a thing. Community mods, when they are making or editing the post flairs in their communities, can toggle whether a post flair should blur the content or not. So, as a concrete example, I created a flair called Spoiler in [email protected], and if a post is tagged with that, then the images will be blurred.

Right now, this feature only works on piefed because lemmy doesn't support post flairs at all. Additionally, there are some complications about post flairs that crop up when a community's home instance is a lemmy instance. Basically, lemmy doesn't federate out post flair at all. So, even if I am assigning post flair from piefed.social, it doesn't federate out to other piefed instances because it isn't federated out by the community's home lemmy instance.