One thing that @torproject is missing is a way to check availability and reachability of #Bridges with a simple tool.

• This is kinda vital as I do occasionally setup private #bridges and also want to enshure the private #TorBridges list I have is up to date.

Manually adding/removing one #bridge after the other in #TorBrowser and see if those connect is a relatively inefficient process and merely pinging them isn't viable either, espechally on #meek, #obfs4 and #snowflake type bridges.

• Now to make the obvious clear: I'd NEVER publicly list any #TorBridge on my lists.d repo obviously, because that would only harm #Tor...

I'm not even asking for like a fancy tool that is as clean as @micahflee 's #OnionShare but merely a #CLI thing (if necessary I'd build some #bash script) to automatically attempt to connect to said bridge and either spit out an ok or error.

• Something one can just feed with a text file and that'll spit out a different file with ok/working bridges and/or discards the non-working ones from the list.

And yes, this tool is kinda crucial as I want to quickly sift through a load of bridges that work on restricted ports (22, 80, 443) and thus can bypass the #GreatFirewall and #Roskomnadzor filtering...

• So people fleeing can at least safely communicate.

If anyone at #TorProject needs more details, I'll gladly exchange them in a secure manner.

• I also applied for a #gitlab account so I can help improve #documentation (ideally with some nice step-by-step screenshots so even "#TechIlliterates" can i.e. add a #bridge)...