SebastianVerified account

So I spent time satisfying their constraints which would turn out to not be relevant. Again, this can be mitigated if you have a more cohesive community where everyone is mostly on the same page.

Another point is around inclusivity. I don't want anyone to feel left out. No matter how wide you cast the net, there's always going to be someone valuable you've left out. Performing value judgements on people is gross and not really something I want to have to do.

Especially since position in the community, which most use as a measure of relevancy, doesn't necessarily yield the most useful feedback.

I've never received private feedback that wouldn't have been more valuable to have publicly. Once your community reaches a certain size that can be extremely noisy though.

Also depends on the release position of the project. Rome would probably be released as an alpha or beta. Opportunity to change anything, which is typically the purpose of early access.

I feel as though I have the necessary experience and context to build a functional MVP. Any public or private feedback during that time would be unlikely to be unproductive.

Anyway, I hope that cleared some things up that were ambiguous from my original tweets. I'm very interested in discussing the higher level points, but I'm uninterested in debating specific scenarios (comparisons are fine).

Well reasoned FWIW (probably nothing ) I think this is the best approach Curious how you plan to deal with the nosiness you mentioned.