>Why can't it just co-exist with other "acceptable" content?
Do you really think the critique of Only Fans is aimed at the consumers' experience, rather than contributing to the norm that it's OK for men to pay women to do what the men want?
Try reading the GTD book. What could have been a flowchart, maybe bundled with some potential downsides/gotchas-and-how-to-avoid-them, somehow became this nonsense 300-page sleeping pill.
If the goal is to either reduce the number of open issues, or make it easy to find the most recently reported/recently active issues, it could be accomplished in other ways. What about:
- not having "TOTAL issues" as a counter, but "TOTAL RECENTLY ACTIVE issues", for some value of "recently"
- defaulting to only showing the RECENTLY ACTIVE issues when searching for them (or finding them through other views)
- displaying a warning such as "this issues is dusty, consider it not being prioritized highly"
As with all other bug reporting systems, having slices/views to work with seems to be preferred to closing issues. Someone supporting the product might really want to find the issues being "most reacted to" recently, the planning "product manager role" maybe only wants to see the high level "epics/initiatives/visions" in a certain order, etc.
I think much of this comes down to all issues being on the same "level" in a Github issue tracker, i.e. "tagging is enough", which some projects solves with a huge taxonomy, and some don't.
The author also published a tool for PBT:nif web front ends which sounds interesting.