this post was submitted on 11 Apr 2025
30 points (100.0% liked)

Lemmy Apps

5994 readers
3 users here now

A home for discussion of Lemmy apps and tools for all platforms.

RULES:


An extensive list of Lemmy apps is available here:

LemmyApps.com

or lemmyapps.netlify.app


Visit our partner Communities!

Lemmy Plugins and Userscripts is a great place to enhance the Lemmy browsing experience. [email protected]

Lemmy Integrations is a community about all integrations with the lemmy API. Bots, Scripts, New Apps, etc. [email protected]

Lemmy Bots and Tools is a place to discuss and show off bots, tools, front ends, etc. you’re making that relate to lemmy. [email protected]

Lemmy App Development is a place for Lemmy builders to chat about building apps, clients, tools and bots for the Lemmy platform. [email protected]

founded 2 years ago
MODERATORS
 

I'm testing a feature in my current dev branch and would like some feedback. The technical side of it is complete, but I'm curious about the human side of it.

When loading a removed comment in the comment section, it automatically fetches the removal reason from the modlog and appends it below 'Removed by Mod" on the comment. The "Removed by Mod" text is also linked to the modlog entry for the item.

Additionally, if you're a mod, it will also append, in a spoiler block, the original comment that was removed. Somewhere between 0.19.3 and 0.19.9, the Lemmy devs decided mods should no longer be able to see removed comments in their own communities, which I think is a huge regression (though thankfully admins can still see them).

Thoughts? Is this asking for drama, or would it be generally beneficial? Right now, in the dev branch, it just does it, but I can make it a user option.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 3 days ago (1 children)

Interesting. Perhaps make it something like click/tap to show reason?

[–] [email protected] 2 points 3 days ago* (last edited 3 days ago) (1 children)

That was the original plan, but I'm trying to achieve four goals with a single API call:

  1. (Optionally?) Show the removal reason for everyone
  2. For mods only, provide the original comment text for reference since the Lemmy devs took that away despite it being useful. The original text is pulled from the same modlog lookup that also fetches the reason.
  3. For admins, continue showing the current comment value (in lieu of "Removed by Mod") since the content is available to them.
  4. Not to over-complicate a feature I'm going to have to re-write anyway when 1.0 comes out and breaks most of the API. 😠

That's why I was thinking that making a user option for the behavior would be the compromise (the same setting toggle would control both 1 and 2 while achieving #4).

[–] [email protected] 2 points 2 days ago (1 children)

That's why I was thinking that making a user option for the behavior would be the compromise (the same setting toggle would control both 1 and 2 while achieving #4).

Looks reasonable to me. Especially given the new API changes. How rough is the prepwork for that looking to be?

[–] [email protected] 2 points 2 days ago* (last edited 2 days ago) (1 children)

How rough is the prepwork for that looking to be?

So far, medium to major PITA. AFAIK, there's still not a full list of things that they're breaking in v3 (haven't even looked at going full v4 yet, but assuming major PITA). So I'm still waiting for the other shoe to drop before diving in. I don't have time to chase a moving target any more than I already am.

[–] [email protected] 2 points 2 days ago (1 children)

I see, in other words I should start getting used to trying apps other than Sync. At least the Lemmy devs seem to appreciate this is a big task and intend to giving ample time.

[–] [email protected] 1 points 2 days ago

Yeah, we'll see. I'd like to have a concrete list of changes/breaks before starting to port things to Lemmy yet again. If only they'd put all their breaking changes in v4, it would be nice.