[15:43:28] https://geneva.cs.umd.edu/ [15:43:35] This thing looks really amazing to me [15:43:57] I wonder if we can collaborate with them to make Wikimedia servers censorship resistant [15:45:08] Maybe we can deploy some of their interventions at server side [16:39:50] >Geneva cannot be used to circumvent blocking of IP addresses. [23:52:21] diskdance[m]: Geneva is an interesting project for sure and it's also very promising [23:52:36] as for adding something like this to our servers, it gets a bit more challenging [23:53:03] first of all, while Geneva has been there for quite some time and is making steady progress (actively updated, maintained), that can't be said for most academic projects that come out in this field [23:54:02] there is also the question of how much something like this can be adapted for our stack and how properly upstream will be maintaining it, for it is a game of cat and mouse after all [23:54:36] we simply don't have the time or resources to put the effort into something like Geneva, for it to be stopped maintaining or dropped. (this is not about Geneva but using it as an example) [23:55:08] our censorship response has to include standardized protocols with sufficient client and server implementations that we can maintain and provide for everyone, not just some unique cases [23:55:38] and in this case of course I am talking about the Geneva server-side engine, not the client side, since we can't expect users to understand how to use it just to circumvent censorship to our websites [23:56:09] for those purposes, V2Ray and Shadowsocks are far more suitable and actively maintained [23:56:33] on the server side, these tools need to have support for the things we use (haproxy in this case as the TLS terminator) because we don't have the resources or even the skills to maintain these tools [23:57:49] so while there are many such projects (and even for Android), we really can't implement them unless they fulfill the above requirements