@[email protected]

This is probably due to the fix that allowed for bold words to show up twice in the same sentence. I don’t have a good solution for this at the moment except maybe preprocessing the markdown in some way to escape this.

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:

Just to be clear, this feature doesn’t prevent federated votes coming in from other instances, it just prevents your vote from federating out unless you want it to. So, brigading from other instances could still happen (barring the use of any of the other tools available to a piefed admin).

Piefed (and lemmy I believe) do have options to have a local-only community though. That community is only interactable by local members of that instance, which would prevent the brigading scenario. This is set on a per-community basis though.

IIRC it is intentional that world isn’t there to help spread out users to other instances.

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.

That would do it. Thanks as always Blaze!

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.

…diligently taking notes…

I am going to take a closer look at 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).

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.

Hey, wanted to follow up on this and let you know that I finished this up and it is now live. 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.

Should be fixed now. The only issue I can still see is that if a community has a really long display name it will overflow the menu on very small screens.

edit: and it got broke again with a later update…stay tuned

edit edit: works again, and rimu fixed the long name issue

Should be fixed now. The only issue I can still see is that if a community has a really long display name it will overflow the menu on very small screens.

edit: and it got broke again with a later update…stay tuned

edit edit: works again, and rimu fixed the long name issue

Looks like @[email protected] was listening: https://piefed.social/post/875579

I’ll try to take a look at this over the coming week. I recently added support for animated gifs as image posts, so I imagine a similar approach would work for other places. The root issue is that the image library pillow just doesn’t have great gif support.

If I understand correctly, this would just apply to the intermediate level of compact layout? It doesn’t really make sense to be right-aligned on the expanded media view.

I think this would likely need to be a change implemented on the templates rather than just css (but I am far from a css whiz).

Yeah, I’ll fix that up. I missed that the css class wasn’t inherited to the child elements, so I will just need to apply the breakpoints to the submenu items.

The submenus are a good point that I missed when doing this really quick. I am traveling most of today, but should be able to make an improved PR for those tomorrow. It’s the same fix, I just missed that applying the css class to a parent element wouldn’t translate to the child ones in this case.