If you want a "transparency workaround", it may help to know that Lemmy is kind of a wrapper for Mastodon, with Lemmy "communities" just being Mastodon users who "boost" some comment (Lemmy "post") and the subsequent replies. Check a Lemmy discussion from some Mastodon servers, and you may notice not all of them honor Lemmy removal requests, leaving copies of posts, comments, discussions, etc... even copies of some CSAM.

Yet it was civil and in line with beehaw site rules, so there is no sensible reason to be as disruptive as to suppress conversation in that thread. When something is off topic for the community timeline, it’s merely an organizational problem of clutter.

If you want to contribute some code, an idea would be enhancing the cross-post feature, and allowing posts to get "moved" from one community to another (from Mastodon's point of view, a simple matter of a different "Lemmy community" user boosting the same post).

[–] debanqued 2 points 9 months ago* (last edited 9 months ago)

I appreciate the background & history.. and the workaround sounds quite useful until Lemmy evolves more.

If you want to contribute some code

Let’s not get ahead of ourselves. I would have to fork it just to get it out of MS Github and into an ethical work environment. And from there I would have to learn 2 or 3 new languages IIUC. I’m merely a user, or tester at best, trying to just get an understanding of the problems.. not even yet at the stage of digging through existing bug reports. When I wrote what you quoted, I did not even know yet if the tool was limited or if it’s malconfigured, or if a mod wasn’t making full use of the software. PenguinCoder hinted in another thread there is a thread hiding option in one of the Lemmy forks but did not elaborate. Superficially that sounds like a more appropriate mechanism for an off topic thread if it works the way it sounds.