We're adults here, if we can't take critique without crying foul - the internet isn't for us.
In my experience when people ask for a critique of something completely new, they're asking (usually without knowing it) for the high-bit: Does this completely suck, or should I keep working on it? Unfortunately people too often respond with only the low-bits, forgetting to add "but these are nit-picks, the overall idea doesn't suck, and you should keep working on it". At best that's frustrating, because you only hear low-bits when you wanted the high-bit. At worst it's a disaster, if you misread low-bits as high-bits and give up on something promising.
It is possible to get good public critique but it has to be handled carefully. There is an art to it. And even if you know what you are doing, it can still go very wrong. But how you frame it matters. Having an account here and the ability to request feedback does not guarantee that one knows how to ask effectively.
In my experience when people ask for a critique of something completely new, they're asking (usually without knowing it) for the high-bit: Does this completely suck, or should I keep working on it? Unfortunately people too often respond with only the low-bits, forgetting to add "but these are nit-picks, the overall idea doesn't suck, and you should keep working on it". At best that's frustrating, because you only hear low-bits when you wanted the high-bit. At worst it's a disaster, if you misread low-bits as high-bits and give up on something promising.