The project is marketed as unblockable, etc and yet we both conclude it is blockable from the start with existing network management tools that are deployed in places like Iran and China.
Block-resistant and censorship-resistant are terminology I've seen used in other projects.
I agree that ublockable and uncensorable are hard phrases to sell here, they kind of immediately beg to be challenged.
> Eschew flamebait. Avoid unrelated controversies and generic tangents.
I very much think resolving this conversation is of the utmost importance, is absolutely core to the topic at hand. There should at least be some idea of what the criticism here is. I would really like to see that.
I have not at all been perfect. But I have tried to surface technics, to get to the heart of the technical matters at hand. To illuminate & increase the information here, in the core topics at hand.
I respect your intervention here dang & agree this is going bad. And I could improve. But I think I am very very very narrowly not-passing here, and this seems like an essential defense to me. I've been wanting very badly to get to the real topic, to affirm & help us to work with the next HN rule after "Eschew flamebait":
> Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something.
The project is marketed as unblockable, etc and yet we both conclude it is blockable from the start with existing network management tools that are deployed in places like Iran and China.
I was asking a genuine question of use case.