I have not read your past back-and-forths and interaction with the folks, but it sounds like this is already escalated situation and there is a lot to unpack from the past. Is that correct?

In that case it's hard to point at this very last situation/case (this specific request on github) and you can't really expect us to try assessing the situation just based on the last post.

So just couple of high level observations: The title of your post (both here and github) are unnecessarily triggering. When people read it, they will immediately create a picture about you and that reduces your chances to actually make them listen carefully. Your posts are very long, bringing many points, many different pokes and punches. In escalated situation - the less text is often much better. With long text the reader immediately tries fighting individual points and nuance and that's the last thing you need. Just focus on the point where you need alignment, find the common ground with the other side and focus on that. The rest can be discussed later, separately, when the heads cooled down. That way you would have much more success.

I'm not saying you are wrong or correct, I'm saying that this communication style and behavior usually has this type of reaction and we see it again and again. If you communicate with this style I think unfortunately the outcome is quite predictable. Last time I observed Jeremy Rubin was missing couple of communication skills like this and he ended up very frustrated.

I can offer one more perspective. Communication is a skill like any other skill. When someone asks you to learn Rust, then you know exactly what to do, right? Like read some docs and quick tutorials, you try a demo project, you watch Youtube video about it, maybe you read a book about it. With communication it's exactly the same and the approach is also the same, but somehow people don't think that way. Watch youtube videos, read a book, find some articles and tutorials, try getting better on some "demo" situations...