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.
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?
@[email protected] - you will need to edit your post again to put the proper markdown back in for in-line spoilers. The brief period of time it was broken meant that the markdown syntax was replaced by html which won't display right.
This should be working again.
Here is a sentence with a || spoiler ||.
Seems like rimu broke it last night. I just submitted a PR to fix it, but it will probably be another 12 hours or so before it gets pushed live due to timezone differences.
This is how it should look:
Hidden | Hovered/Tapped |
---|---|
![]() |
![]() |
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.
I was referring more to responsiveness and page loading time than overall resource usage. I don't know enough on the sysadmin or database side of things to really speak authoritatively about things at scale. I just mean that it's usually postgres instead of the language of python that limits what I have worked on.
From my experience contributing to Piefed, the bottleneck is almost always the database. So, doing optimization on that front has yielded improvements. I suspect that the db is likely the main bottleneck of lemmy as well (though I know network speed/latency has been an issue in the past).
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:
I have created a codeberg issue for restoration of posts/replies.
To really be consistent with lemmy, this instance info is displayed only when a community is remote and remains hidden when a community is local. I added some css classes to make that distinction possible as part of the PR. So, to achieve that, here is the css you would want: