I loved this show. It was so needlessly well produced. Probably one of the darkest comedies I have seen in some time.

The manga is great as well.

Would this enable something like Lemmy Webhook or other kinds of automod plugins then if I am understanding this right?

Just following up on this that stickied posts should now show up at the top of communities even if you sort by New. Additionally, the double bold problem should be solved now without breaking anything else. Feel free to reach out in this community or on codeberg with issues if they come up.

PS - post and comment previews should show better formatting as well, including blockquotes and code blocks.

The lemmy-style spoiler syntax is a huge pain tbh, and very limiting in that for something to be a spoiler, it needs to be a separate paragraph. Adding || in-line spoilers || was one of my first contributions to piefed because I found it so annoying (that won’t render as an in-line spoiler on lemmy).

The markdown-parsing library used by piefed supported using the same syntax as telegram/discord, with || spoiler here ||, so that is what I used for the feature even though I prefer the reddit/stack overflow style spoiler syntax better.

Just to follow up on this. A fix for this has been merged and should roll out in the next 24 hours or so to the site.

Yeah…this led me down a bit of a rabbit hole. I had initially written up a big post about how to restore a deleted comment, but then realized I was testing it out on an account that was a community moderator. So, trying again, here is what I found:

• Restoring a deleted comment as just a normal user (not a mod or admin) is currently not possible. This seems like an oversight and I think it should be a relatively easy fix.
• Restoring a comment as a mod/admin works as expected. You need to expand the deleted comment with the arrows and then select restore from the three dots menu.
• Purging a comment literally removes it from the database. This prevents it from ever being restored ever again as it basically doesn’t exist from the server’s perspective any longer.

I have created a codeberg issue for restoration of posts/replies.

It would certainly be possible, but I don’t think there is a way to do so right now. I would imagine the most straightforward way of doing this would be to have a page for the community that lists the tags. So, you could have:

https://piefed.social/c/action_movies/tags

and that would bring you to a page with all the tags that have been used in that community. Maybe a button on the sidebar somewhere to take the user to that page.

I went ahead and made a codeberg issue for the idea.

Apologies for reading too quickly. I believe that tags are solely up to the OP and can’t be modified by the mod or admin. As for question 2, when it comes to many different tags, that shouldn’t be a problem really. Only the 30 (I think) most-used are displayed in the sidebar, but there could be many, many more. Here are all the tags used so far on piefed.social for instance.

1. Yes. A community mod or admin is able to add flair to somebody else’s post. This is especially useful when the OP is not on a piefed instance and unable to use flair at all. One caveat to this is that if the community is from a lemmy instance, the mod-assigned flair will not federate out to other piefed instances. You should see a little flair icon on the post previews in your community (next to the three dots menu) that opens a flair assignment menu.
2. I don’t remember there being a limit to flair for the community, and yes, all of them will be shown. So, it makes sense to keep the flair list somewhat limited in scope with broad categories. Something like hashtags make more sense for more specific categories. The community with the most flair that I know of is !fediverse@piefed.social if you want to see what a lot of flair looks like.
3. I actually don’t know. I do know that tags from microblog posts are picked up, but I don’t know about the body of piefed or lemmy posts.

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.

@rimu@piefed.social

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.

Still lots of things to do :)

Lemmy has been at it for years at this point while piefed only started up a bit over a year ago I think? In any case, I have only been a contributor for maybe a couple weeks, so lots of catching up to do!

Relevant issue: https://codeberg.org/rimu/pyfedi/issues/665

tl;dr - it’s an issue with the pillow image library in python. It’s on our radar though. I got posts working, but you have to click through, the thumbnail still isn’t animated.

The user that created the community is treated differently in that they cannot be removed by the other moderators. I belive that user is referred to as the owner in the code. I haven’t looked into it yet, but I think there is a way to transfer ownership of the community. If not, then there should be.

As far as I know, that is really the only difference between the owner and the other community moderators.

Thanks! It seems the markdown is saved and federated out correctly, so lemmy’s markdown to html is parsing it as intended. What is going wrong is piefed’s markdown to html parsing in this specific case.

Wait, so what is that issue? If you bold something in two different places it gets messed up?

Edit: it sure does…I will take a look at that when I look at formatting comment previews correctly.

I don’t know enough about how the JS works to say whether the VPN would cause it, but @innermeerkat@jlai.lu was already working on this because their browser was messing it up and insisting they lived in Reykjavik. So, it clearly isn’t such a rare case that we can ignore it. We think it might be a privacy feature of some browsers that they don’t want to give away a tz.

On piefed

They both appear stickied just fine to me. Something that is different with sticky posts on piefed is that if you sort by New, then the sticky posts are no longer at the top of the page. That is different than how lemmy does it. This has led to confusion in the past, and even has a codeberg issue about it.

On lemmy

I am guessing that federation had not yet been established between that lemmy instance when you created and stickied that initial welcome post. I just tried an experiment now where I subscribed to your community from a test lemmy instance I have and forced federation of one of the sticky posts, and it didn’t come over stickied. So, there might be some weirdness there.

What you can do to try to resolve this is to unsticky it and then resticky it. That should send out the correct actions via activitypub so that the other instances know that the post should be stickied. To be on the safer side, give it a minute or two between those two actions so that you are sure the first action had been sent out fully.

The height of notifications does vary a bit depending on the type of notification. Some of the admin notifications in particular are a bit taller than the others, but I did try to tame them. The nice thing about how the notifications were re-architected by Jolly is that each one is a separate template file. So, if we want to tweak a specific type of notification, it is easier to do now compared to before.

Raw markdown in the notification is good feedback. This isn’t something I had tested when working on how these display, I can take a look at 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: