# Category creep and information overload

**URL:** https://meta.discourse.org/t/category-creep-and-information-overload/62493
**Category:** UX
**Created:** [11.Май.2017 08:37:27 UTC](https://meta.discourse.org/t/category-creep-and-information-overload/62493 "2017-05-11T08:37:27Z")
**Posts on this page:** 1
**Showing post:** 16

<div class="post-metadata">

### Author: ![Rob\_Nicholson](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rob_nicholson/32/63483_2.png) [@Rob\_Nicholson](https://meta.discourse.org/u/Rob_Nicholson)
#### Post date: [28.Август.2017 14:56:11 UTC](https://meta.discourse.org/t/category-creep-and-information-overload/62493/16 "2017-08-28T14:56:11Z")

</div>

Not really sorted it aside from possible nagging about keeping the categories under control. Time passes so I can’t remember how long CAMRA Discourse has been running but it’s doing “okay”. @HAWK will be aware of some of the softer issues one raised over on Fever Bee.

Whilst I’ve got used to the way everything is lumped together and non-categorised by default, it does cause the more infrequent visitors a little bit of trouble. But we’re getting there.

I do personally find myself reading topics that I’d prefer not to read because of the way they are presented on the latest timeline.

I random thought just hit me - there are many topics that I’m not really directly interested in but if they got really busy, I might want to re-visit. Muting a topic is too draconian IMO. Maybe a “Mute unless it gets busy”. Yes, I know that’s a very nebulous end user requirement.

In our helpdesk system, I **often** “snooze” tickets. I do want to action them but not right now. So maybe a snooze feature, e.g. mute this topic for N days. For threads that I do want to read when I’ve got a moment spare but don’t want them in my “Latest” list right now.

Just thinking out loud.

---

_[View the full topic](https://meta.discourse.org/t/category-creep-and-information-overload/62493)._