Ok, I added it. A brand new guideline is a rarity. We should have a ceremony.
I worded it more concretely: "Please don't complain about website formatting, back-button breakage, and similar annoyances [etc]" I find that giving concrete examples and inviting the mind to generalize them works better than giving an abstract rule and inviting the mind to instantiate it. I learned this trick from spreadsheet development.
I was about to complain bitterly that the guidelines are now too long and there isn't a single one that can be taken out...but then I saw one that could be taken out, and I took it out. That was "Please submit the canonical URL. Avoid link shorteners." It's covered by "Please submit the original source." We added it a few years ago to try to convey that link shorteners are banned on HN, but it can be pushed out of the constitution and down into case law. It's the ones that aren't derivable from other guidelines that are hard to remove.
The list still feels too long to me. The longer it gets, the less people will take in, and I really want to avoid the mistake of accruing a big list of rules over time. They've grown like tree rings (and about as slowly) as we've learned about what feedback helps regulate the system. But the longer the list becomes, the more it starts to feel like a bureaucratic artifact rather than, let's say, a philosophical one, and that is out of sync with the intended spirit. https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...