My first reaction was to remove the module from our project, but that would leave everybody currently using it stranded on the E.T. [1] version. I think we should at least release a version that disables the server side callbacks by default (providing an option to enable them) and go from there.
I am certain Jeanfrancois Arcand doesn't have nefarious motives but frameworks should not phone anywhere without explicit approval. Anybody have other thoughts on the future of wicket-atmosphere? Martijn [1] https://www.youtube.com/watch?v=iyFijjikkeM On Fri, Oct 3, 2014 at 1:27 PM, Martijn Dashorst <martijn.dasho...@gmail.com> wrote: > Due to functionality that tracks atmosphere-framework usage you might > be in violation of EU tracking laws. > > Apparently Atmosphere opens an undocumented server-side connection to > Google Analytics to track Atmosphere usage. At this stage it is > unclear what can be tracked by Google from this connection, but > suffice to say this is troubling. > > Atmosphere's maintainer doesn't see any problem with this phone home > behavior ("it is sent to Google Analytics, not Google") [1] but has > implemented a feature to disable this [2] > > At this moment we can't recommend people using wicket-atmosphere in > production systems until we have updated the atmosphere library and > disabled the phone home tracker. > > Emond & Martijn > > [1] https://groups.google.com/forum/#!topic/atmosphere-framework/RIkB689kExI > [2] > https://github.com/Atmosphere/atmosphere/commit/97993855734903536b046a41b1dbbe3f3558d463 -- Become a Wicket expert, learn from the best: http://wicketinaction.com
