@torproject Q: I wish there was a similar tool test #Bridges, as https://bridges.torproject.org/scan/ is not that good and I don't want to hammer it with dozens of addresses, cuz at best that's quite antisocial if not possibly trigger responses assuming this is an intelligence gathering operation.

• Ideally sone standalone binary that one can just give a list of #TorBridge|s in a text file (similar to the way one can just past them in at #TorBrowser) would help.

I.e.

bridgetest -v4 obfs4 203.0.113.0:80 …

bridgetest -v6 webtunnel [2001:DB8::1]:443 …

bridgetest -list ./tor.bridges.list.private.tsv 

• But maybe #onionprobe already does that. In that case please tell me to "#RTFM!"…

Similarly there needs to be a more granular way to request #TorBridges from #BridgeDB (as it's basically impossible to get #IPv4 #Webtunnel addresses nor is there an option to filter for #ports like :80 & :443 to deal with restrictive #firewalls (i.e. on public #WiFi)…

• there are flags like ipv6=yes but neither ipv4=yes nor ipv6=no yielded me other resultd than #IPv6 webtunnel bridges…

And before anyone asks: Yes, I do have a "legitimate purpose" as some of my contacts do need Bridges to get beyond a mandatory firewall and/or do use #TorBrowser (through an #SSH tunnel) to circumvent Tor & #VPN blocks and maintain privacy (as many companies do block sometimes entire #Hosters' ASNs due to rampant #scrapers…

@tails_live @tails @torproject plus support for meek, snowflake, webtunnel and non-#obfs4 #Bridges seems missing in #Tails.

• It would also help if #BridgeDB allowed to actually select #IPv4 and not just #IPv6 and select ports (i.e. 80 & 443) on top of that.

Cuz to this day I've to yet see an IPv4-#webtunnel #bridge…

Right now the problem with @torproject #BridgeDB is that I can't get #webtunnel bridges on #IPv4 even when I try to specify those by setting ipv6=no at the URL:

https://bridges.torproject.org/bridges?transport=webtunnel&ipv6=no

And no, removing IPv6 from the URL doesn't yield any IPv4 results either.
https://bridges.torproject.org/bridges?transport=webtunnel

It would be better if #BridgeDB would have a radio button / switch to choose IPv4 & #IPv6 for this reason.

Just a friendly reminder that @torproject needs more volunteers to run #WebTunnel bridges.

If you're a #fediverse admin, you can safely run a WebTunnel bridge behind your Nginx web server in order to help people access the open internet.

https://community.torproject.org/relay/setup/webtunnel/

@ActuallyAubrey That depends on the juristiction in question, the plan & provider in question as well as used hardware in question.

• In case of even remotely suspected #Stalkerware I do recommend to get personally-owned, controlled, secured and hidden hardware to enable unsurveiled comms.

Consider telephony & SMS inherently & unfixably insecure.

• If in doubt get a new Android with an anonymous prepaid SIM that has affordable data options and use @torproject / #TorBrowser and #Orbot with #TorBridges on ports 80 & 443 which use #meek & #webtunnel transports, so any surveiling party will only see non-suspicious HTTPS traffic.

OFC a maliciously configured CPE/Router can log & report all pachets that travel through, but #DNS & #HTTP or any unencrypted comms are susceptible.

@dragonarchitect @DeltaWye this also is the advantage of #TCPIP: Only the #endpoints need to be able to reach each other: All the complicated #Routing is transparent and thus changing routes don't result in lost connections.

• You can see this with @torproject / #Tor traffic using #webtunnel #bridges: It smoothly shifts between #WiFi & #WWAN and back...

@torproject And yes, I do need some with the ability to filter as contacts in #Russia that want to #flee basically have no other option than #Tor as #Roskomnadnozr systematically bricks #VPN's and #Proxies and only allows like #Webtunnel and #SSH connections [the latter one propably for Russia's #CyberWarfare] to pass through.

So even if they had like #GMail or #RiseUp that wouldn't fix their issues nor would it solve that need.

So please @torproject allow people - if you don't want to change the UI for https://bridges.torproject.org - to at least craft requests that allow users to select #IPv4 and/or #IPv6 #Bridges as well as #Transports [regardless inf #vanilla, #meek, #snowflake, #obfs4 or #webtunnel] and #ports [i.e. 443 & 80] are often the only known working ones!