That seems like a great solution! And “all” didn’t need to show up until you have muted categories or tags.
5개의 좋아요
This is a critically important for my community right now. We have a… very large number of subcategories for a particular category. (Hundreds.) They’re all local communities, so individual categories are irrelevant for the vast majority of users but are of vital importance to those who need them. They’re the cornerstone of our community in many ways. It’s an interesting structure. On our previous software they were “opt in” so they were never displayed unless you specifically subscribed to them. With Discourse, we have to force an opt-out on them and then they have to go hunting for their particular subcategory to unmute it.
I have them all auto-muted by default but that doesn’t do a damn bit of good for people who joined before I did so. (And yes, I entered them one at a time.)
As a side note, it’s also causing some traffic stress on the entire installation itself. We don’t have a better solution for it right now. Discourse wasn’t designed for the number of muted categories we need right now. I’m not sure if the slowness we’re seeing is caused by that entirely, the sudden influx of new users, or a combination of the two. That’s a different issue.
Anyway, all of that to say yes, PLEASE I need to be able to mute categories for a bunch of people.
2개의 좋아요
Why make them all public, then? Why not have group permissions on them from the get-go then add people to the relevant groups?
Also is this being done speculatively? That is, create a thousand subcategories assuming they will all eventually be active.. even when the reality is that only a handful will ever have meaningful participation levels?
3개의 좋아요
That’s a definite possibility for the future. Would it handle that many groups better than the the way we have it set up? I know we broke the About page when we added the managers of these groups to them as moderators. I can discuss this with fellow staff to see if that might be a more viable solution.
Nope. Most of these regions are years old and have substantial participation rates. We create them as locals volunteer to manage them. While no doubt some have fallen more inactive over the last decade or so, the vast majority are quite active. Memberships for regional subcategories can range anywhere from a dozen or so people to thousands. We have areas for these on the main half of the site but we don’t have the forum side linked yet.
It’s a weirdly structured thing. 
2개의 좋아요
I’m not sure that was an answer to my post, but I guess so. If I understood correctly, “ignore” is to not show the posts of the ignored user, even if you read a topic where he posted, whereas “mute” is only to not show notifications and not have the topic appear on the front page when there is a new post from that user (but still be able to read posts when you read the topic). Or did I get that wrong ? If not, my interest is indeed about muting, not ignoring.
@Heather_Dudley Your situation is similar to what I want to do (previous post) on some level. But your problem is about subcategories, mine is about posts from a specific user. Your solution is pretty interesting. I could use that by creating a different user for each topic, then I would be able to do like you, but with the slowing down things you’re mentioning I guess.
In your case, if you mute the whole category, and people start tracking a subcategory in it, wouldn’t that work ? (that was the “priority” thing I was asking about when muting and tracking at the same time)
The solution CodingHorror is proposing seems to have one flaw for you: This would be good for actual users, but wouldn’t it prevent people not part of the group from viewing the topic (visitors, and especially potential new users wanting to join such a group) ? I mean, it’s usually because you had the chance to read that you then want to join …
1개의 좋아요
You could ask some of the sites that use groups instead of muting categories, as discussed here:
5개의 좋아요
확인해 볼 만한 간단한 해결책이 있을 수 있습니다(저도 이 방법을 사용할 예정입니다): 테마(CSS 사용)를 통해 원하는 부분을 숨기는 것입니다. 이렇게 하면 앞면에서 원하지 않는 모든 요소를 제거할 수 있지만, 한 개 이상의 카테고리를 추적하는 모든 사용자의 “읽지 않은” 페이지에는 영향을 주지 않습니다.
앞서 언급한 방법이 작동하지 않는 경우(참고로 저도 그 결과를 궁금해합니다):
한 사용자가 그 분야에서 흥미로운 작업을 수행했는데, 조사해 볼 가치가 있을 것입니다(그 사용자의 문제는 하위 카테고리나 저나 질문자님 같은 일반 사용자가 아니라 그룹에 관한 것이지만, 결국 근본적인 문제는 꽤 비슷합니다):
2개의 좋아요