Re: [tor-talk] Setting up own meek servers
A very interesting example is the GAE proxy software XX-Net (formerly GoAgent) One Google account can be used to register for up to 10 instances, but you can lookup at their public AppID list: https://github.com/XX-net/XX-Net/blob/master/code/default/gae_proxy/local/proxy.ini Thousands of public AppIDs are contributed by users. ยป len(public_appid.split('|')) 1727 -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] Setting up own meek servers
On Wed, Mar 8, 2017, at 10:20 AM, Jonathan Marquardt wrote: > So, when meek-google was suspended, one of the recommendations for people > was > to set up their own apps in AppEngine as meek servers. > > https://lists.torproject.org/pipermail/tor-talk/2016-June/041699.html > > Wouldn't it be a good idea to encourage people to do so, but in a way > that > everyone and not just themselfes can benefit from that? Perhaps they > could > make them public or these things make themselfes public just like with > any > other bridge? Has this idea been discussed before? > > Individual supporters running these reflectors could also cut down on > costs. > And in the case of Google AppEngine, these bridge adresses could perhaps > be > distributed using bridges.torproject.org and GetTor, so Google doesn't > instantly notice them. > I completely agree with this. There should be a push for community hosting of all Meek cloud services type, and not just Google. +n -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
[tor-talk] Setting up own meek servers
So, when meek-google was suspended, one of the recommendations for people was to set up their own apps in AppEngine as meek servers. https://lists.torproject.org/pipermail/tor-talk/2016-June/041699.html Wouldn't it be a good idea to encourage people to do so, but in a way that everyone and not just themselfes can benefit from that? Perhaps they could make them public or these things make themselfes public just like with any other bridge? Has this idea been discussed before? Individual supporters running these reflectors could also cut down on costs. And in the case of Google AppEngine, these bridge adresses could perhaps be distributed using bridges.torproject.org and GetTor, so Google doesn't instantly notice them. -- 4096R/1224DBD299A4F5F3 47BC 7DE8 3D46 2E8B ED18 AA86 1224 DBD2 99A4 F5F3 signature.asc Description: Digital signature -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk