this is definitely undesirable in a number of contexts, but as far as we're aware this is a Lemmy thing we can't change and don't really have control over.
this post was submitted on 20 Feb 2024
9 points (100.0% liked)
Beehaw Support
2796 readers
6 users here now
Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.
A brief FAQ for lurkers and new users can be found here.
Our September 2024 financial update is here.
For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
Hate to be the Linux-ass guy, but you do have control over Lemmy as far as you can submit Issues or (even better) Pull Requests over on github.
If there is something you want or need from Lemmy, don’t be shy about joining the discussion. Of course be respectful/read the room etc. but unlike reddit we’re not powerless towards dev direction.
We've extensively tried to interface with lemmy devs to take the platform in directions which would help our community and our users. We've even had people from our instance do exactly what you are talking about. Throwing out advice like without asking if we've even done any work feels kind of dismissive.
If you feel strongly about making this platform better, hop on the discord or matrix channel and chip in. We'd love the help and I'm sure plenty of other folks would too.
don’t be shy about joining the discussion.
I think you're arguing in bad faith. We aren't powerless when it comes to Beehaw, but certainly when it comes to Lemmy software overall. That is in fact, part of the problem. We aren't shy, we collectively have identified, fixed, contributed to and organized a ton of Lemmy shortcomings and bugs. Yet other bugs/requests and solutions go ignored or 'closed' due to the Lemmy devs not agreeing that certain things are a problem, or inline with what we need for community standards or administrative controls.
It gets very very tiring trying to improve a product you use constantly, just to be told to GTFO "We don't see it as a problem"
Go look at the PRs and issues we've raised for Lemmy. In addition, observe the attempts at solving the identified problems, not just complaining about them.
the UI is broken enough to render a dysfunctional reply mechanism.
100% Agreed, a lot of dysfunctional with regards to the UI and BE interoperability. I'll add your specific issue into my list of Lemmy annoyances to try and fix for Beehaw.
Removed threads should still be reachable and interactive
Personal opinion; Nope. Utterly no. Defeats the point of removing a topic from discussion. Difference between hidden and removed and even deleted. You want the first. Admin or mods removing a thread, should not be accessible to anyone else. Maybe a certain subset of admins for review/restoration as needed. But certainly not the public facing internet, where even if it's hidden on a timeline, a direct link still gives access to it. That should not be the case.
What’s the point in blocking a discussion that’s no longer visible from the timeline?
The point is in removing said 'discussion' from the platform. This is not censorship, this is how we keep the purpose of Beehaw inline with the ethos.
I agree with your reasoning here.
Difference between hidden and removed and even deleted.
Does Lemmy give those three different actions?
I can imagine that something that’s illegal would be deleted in the fullest extent to support legal compliance. I can imagine that an uncivil shitshow would be removed, whereby the content is still reachable to admins but not to users. And I would expect something that is off topic for a community would be hidden, assuming that means just not visible in the timeline but still accessible by users who have the link.
Is my understanding of the 3 actions correct? Why would an off topic post be removed and not hidden?
The point is in removing said ‘discussion’ from the platform.
Does that mean a site-wide rule was broken? Because in the case at hand, it’s simply a matter of a civil conversation that was started in the wrong community.
Who benefits from the disruptive suppression of a conversation when the conversation is no longer cluttering the community where it was off topic? I can only see this making sense if the discussion were breaking sitewide rules independent of the community it started in.
Difference between hidden and removed and even deleted.
Does Lemmy give those three different actions?
Not in its native form no.
Why would an off topic post be removed and not hidden?
Say this again to yourself and thunk about it.
Does that mean a site-wide rule was broken?
Not going to play rules lawyer with you.
a civil conversation that was started in the wrong community.
Thus the item was removed from that community. What is the problem here?
Thus the item was removed from that community. What is the problem here?
You may be talking from the confines of the software’s capability. But in effect the thread was more than removed from the community. The only meaningful tie a thread has to a community is the link appearing in the timeline. The URL in fact excludes the community name. If you simply remove the timeline link there is theoretically no technical or social reason a civil sitewide-rules-compliant conversation cannot continue. And no reason it should not continue.
There is likely a code limitation here. Lemmy was designed by folks who are overly gung ho on suppression (judging from how they ran dev.lemmy.ml, the deliberately hard-coding of the slur filter, their reputation, etc). I’ve not kept track of Lenny and other forks so it’s unclear if any of them offer more graceful functionality without the overbearing interventionalism for handling off topic posts. It certainly needs to evolve more in this regard because I’ve yet to see any Lemmy et al instances that enable a mod to move a thread to a more fitting community.
I received a reply that I could not reply to.
Welcome to the club: https://beehaw.org/post/7638652
I've commented with the workaround on your other post, you can see on this one how it works.
Thanks for pointing that out. I added your link to the post.