> "Bring my concerns to the people I have concerns with in private before having to talk about it in public" is just the right way to talk to people about problems.

Yes, it typically is. However making non-falsifiable public accusations that individuals are doing "dirty shit" is not keeping things "private" and is even worse than making a concrete public statement about a concern you may have.

Perhaps it isn't and it's actually good not to go very confrontational right from the start?

(I was aiming at "not telling everything" is a friendlier tone than telling everything and possibly losing all trust)

I get that but tweeting "they've also taken steps to marginalize the core team. and some other dirty shit I won't say rn." is the kind of statement that burns bridges pretty hard.

Sure, I understand that, but the tweetstorm is very non-specific. The only reason why I share your concern is because you built an amazing personal brand.

I tried to be very specific in my issue with what is public knowledge: Amazon has outsized influence in the project, and is continuing to wield it to gain more. I even cited specific ways in which that is happening.

I was also vague about other things because they're secondary concerns to the main one. If Amazon stops trying to be in total control of Rust, I'll be happy.

You're talking in public now and bring the discussion into the public in the least professional way possible.