Snowflake issueshttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues2024-03-13T06:57:03Zhttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/32677Find a way to notify deployed proxy-go instances of updates2024-03-13T06:57:03ZCecylia BocovichFind a way to notify deployed proxy-go instances of updatesWe've had a few people run proxy-go instances in the past and express interest in running them. These instances should be updated periodically or when there is a critical reason to do so. Right now we don't have a good way to notify depl...We've had a few people run proxy-go instances in the past and express interest in running them. These instances should be updated periodically or when there is a critical reason to do so. Right now we don't have a good way to notify deployed instances of updates.https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/31085Make an Android extension or app for people to be a snowflake (AMO or proxy-go)2023-07-13T14:59:01ZcypherpunksMake an Android extension or app for people to be a snowflake (AMO or proxy-go)https://addons.mozilla.org/en-US/android/https://addons.mozilla.org/en-US/android/Sponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibethttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/29863Add disk space monitoring for snowflake infrastructure2023-07-31T02:23:24ZCecylia BocovichAdd disk space monitoring for snowflake infrastructureWe've run out of disk space at both the snowflake bridge (legacy/trac#26661, legacy/trac#28390) and the broker (legacy/trac#29861), which has caused snowflake to stop working. We've set up rotating and compressed logs but it would be nic...We've run out of disk space at both the snowflake bridge (legacy/trac#26661, legacy/trac#28390) and the broker (legacy/trac#29861), which has caused snowflake to stop working. We've set up rotating and compressed logs but it would be nice to have some disk space monitoring to alert us if/when this happens again
Also, as discussed on IRC, we should eventually move the broker to a TPA machine.Sponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibethttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/29260Should Snowflake proxies have a way to identify themselves to the broker2022-07-25T17:59:44ZAlexander Færøyahf@torproject.orgShould Snowflake proxies have a way to identify themselves to the brokerWould it make sense for us to have an identity key (or something similar) for Snowflake proxies to allow them to identify themselves to the broker service.
This would allow us to later build reputation systems for the proxies and distri...Would it make sense for us to have an identity key (or something similar) for Snowflake proxies to allow them to identify themselves to the broker service.
This would allow us to later build reputation systems for the proxies and distribute snowflake proxies in a smart way based of stability/uptime. The downside from a privacy perspective is that the broker can follow the Snowflake proxies' movements on the internet, which means we might want to make it optional.https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/25591Pass STUN information from Broker to WebRTC Client2023-08-02T00:02:28ZArlo BreaultPass STUN information from Broker to WebRTC Client> The clients may be in filtered regions where common ICE servers may be unavailable.
>
> May need to revise the Configuration interface of go-webrtc while figuring this part out.
\\ Migrated from https://github.com/keroserene/snowflake...> The clients may be in filtered regions where common ICE servers may be unavailable.
>
> May need to revise the Configuration interface of go-webrtc while figuring this part out.
\\ Migrated from https://github.com/keroserene/snowflake/issues/3
We had some discussion [in a recent meeting](http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-12-05-18.00.log.html) about the original intent of this ticket.
I think to address the need of "default STUN servers are blocked for the client", it would be more interesting to pursue ways in which NAT punching information for the client could be sent over the domain-fronted connection to the broker. Some discussion on legacy/trac#30579 laid out reasons why a more private way of getting ICE candidates is desirable.