▲ | nharada 5 days ago | ||||||||||||||||
What do you think they should have done instead? | |||||||||||||||||
▲ | actsasbuffoon 5 days ago | parent | next [-] | ||||||||||||||||
At a bare minimum there needs to be some way to understand how close you are to these limits. People shouldn’t be wondering if this is going to impact them or not. | |||||||||||||||||
▲ | arach 5 days ago | parent | prev [-] | ||||||||||||||||
It’s tricky without seeing the actual data. 5% of a massive user base can still be a huge number so I get that it’s hard to be surgical. But those power users are often your most creative, most productive, and most likely to generate standout use cases or case studies. Unless they’re outright abusing the system, I’d lean toward designing for them, not against them. if the concern is genuine abuse, that feels like something you handle with escalation protocols: flag unusual usage, notify users, and apply adaptive caps if needed. Blanket restrictions risk penalizing your most valuable contributors before you’ve even discovered what they might build | |||||||||||||||||
|