Exciting, and thanks!
Disappointed that this is such a low priority
me (n8fr8 nathan@freitas.net)
(tested on Orbot/Android)
Here's a patch that fixes it
@shelikhoo I just realized I am still seeing this issue on Android when we try to be a Snowflake Proxy (aka "Kindness Mode" in Orbot v17).
The changes you made were only within the client webrtc logic.
Can we implement the same fix under the proxy webrtc logic?
cc @cohosh
Agree, @cohosh. Brilliant solution.
Shipping limited permission API keys in binary apps is definitely something that people do.
Thanks for the update and excited to see you investigate this.
The authenticated access of the client is something that I was concerned about. I know with Amazon S3 there is a way to generate some kind of limited access tokens to enable one-time direct upload, so I thought that approach may be viable here.
Once you introduce some other server/gateway/dependency into the mix, the value of being able to access the direct sqs.amazonaws.com endpoint is lost. That said, the fact that SQS queues could work access regions, and be unified on the back-end is still very useful and interesting.
github.githubassets.com is working for our users who previously reporting blocking before.
The issue now is that the circumvention API still returns foursquare.com, so even though in our static default build we use github, if we start refreshing the config based on what is reported by Tor, then they will revert to foursquare.
Thoughts, plans, on migrating everyone over to github?
Didn't you say you had made some progress on this?
I think we have either entirely moved away from, or only show the captcha as a fallback to a fallback, so deprecation is fine by me.
Catching up on all of this... we do target Android 13 already for Orbot v17-beta and 12 for the v16-maintenance branch, so definitely will be an issue for us, if not already.
From quick smoke testing and recent dev testing however, Snowflake does connect still.
Could it be due to us still being on Snowflake 2.5.1?
User story:
"User messages Tor's new WhatsApp support channel asking for a bridge. The response contains a friendly message and a bridge://?foo link. They tap on this and TBA or Orbot pops up to offer to handle this with an appropriate UX explaining what this is, and asking if they want to add this bridge to the current pool of bridges"
Fun idea of the day: Encode bridges or bridge URIs as "Ecoji" plain text as emoji to make copy and paste and sharing in social mechanism more fun, slight safer, and slightly more resilient to censorship
https://github.com/keith-turner/ecoji
obfs4 178.27.102.182:40771 7080F2280EE04AE94F2792D569E0362192674202 cert=cz5iBFFkdUxFJ4HLLElPcjWCb/RU+aL4JGj1d/fkJQRbs3mH/TLTee9oGY1mlJI9XCVIMw iat-mode=0
base64: b2JmczQgMTc4LjI3LjEwMi4xODI6NDA3NzEgNzA4MEYyMjgwRUUwNEFFOTRGMjc5MkQ1NjlFMDM2MjE5MjY3NDIwMiBjZXJ0PWN6NWlCRkZrZFV4Rko0SExMRWxQY2pXQ2IvUlUrYUw0SkdqMWQvZmtKUVJiczNtSC9UTFRlZTlvR1kxbWxKSTlYQ1ZJTXcgaWF0LW1vZGU9MA==
ecoji: