There’s been an influx of content surrounding lemmy here. Some of it is open ended:
- “What kinds of things from reddit would you like to see Lemmy avoid as the user base grows?”
- “Lemmy, what do you call users of Lemmy?”
And these are a-ok! There’s also been a lot of questions like
- “How do I block a user?”
- “How do I join a community on a different instance”
These aren’t open ended (at least, relatively). They are objective based, and just need a resolution, rather than discussion. These sort of questions are more relevant to !lemmy_support@lemmy.ml.
I know there’s also questions like “What are you guys doing when there’s multiple communities for the same thing across instances?”. I’m inclined to let those stay, there is lots of opportunity for discussion. It’s a game of discretion from a moderation perspective, but I assume most can easily guess what is cold hard support.
At least from me, moderation of support posts has been sporadic at best, despite the long standing rule. I will begin redirecting these questions to !lemmy_support@lemmy.ml, however I’m of course willing to listen to the community here if that’s not what is wanted, as well as other feedback.
edit: support posts will now be removed, not locked
Hi, a post was just deleted asking about how and why the subscriber counts were different between instances. This seems to be a post that would help many understand the differences between Lemmy and non-federated networks, and quality content. It was not a support request, and fit into the first category of bullets above. Can this action be reversed and more clarity placed on rule 3 for users and mods (if needed)? Thank you.
For posterity, the post in reference is this
Why are community subscriber counts different when watched from different instances?
I created two accounts on two different instances and all the communities I see have different subscriber counts depending from which account I look. Why does that happen and how can I see the real subscriber count?
i’m having trouble understanding how this isn’t a support request. It’s a
(Why|How) <confusion with lemmy that has a single answer>.. This seems to be a post that would help many understand
Yeah, all the support posts are like this. We get the same five over and over, but this community is not for support. I wouldn’t keep questions about knitting in !woodworking@lemmy.ca because they are helpful. This is simply not the place, unfortunately.
Why do you think it’s not a support post?
I work in IT and users will get upset if you give them the “Please put in a ticket” line. So for the people that might grumble at this stance but there is good reasons for it in addition to not clogging up this community it’s good for QA. I’m new to Lemmy so not sure if the SAs and Devs frequent !lemmy_support@lemmy.ml but I suspect they do and driving support questions to a common spot will help analyze need for new features, UI changes, bug fixes, etc.
Just my 2 cents but I like your stance.
except for supporting our trans comrades 💖
As long as it’s in the form of a question
We support our trans comrades?
The ghost of Alex Trebek has entered the chat
I think They mean that this
subredditCommunity is for asking on Lemmy and not asking about Lemmy.Maybe They clarify the description. 🙂
“Lemmy, what do you call users of Lemmy?”
“Lemmings” is the obvious answer
As a new member of the lemmy.ml admin team I’ve also been removing a lot of posts from here which belong in lemmy_support, which I think is worthwhile for preventing this community from becoming a boring list of support questions.
To the many people who are flagging them: please read the examples above and don’t flag every post that is about lemmy; only flag ones that are actually concrete support questions. And do feel free to actually answer these questions before flagging them, so that the person asking doesn’t necessarily need to re-post it.
Thanks!
It would be cool if there was a way to move a post from one community to another, so the poster gets notified and maybe the old link redirects. Some BBS systems support this.
