Fwd: [webdev] Blog Post: Privacy and Google Analytics

Hi, Here is a set of good practices in the usage of Google Analytics. I believe we should implement these for the loop-client webapp, which is relying on GA currently. — Alex Forwarded Message Subject:[webdev] Blog Post: Privacy and Google Analytics Date: Mon, 23

Re: Mozilla Loop Server /registration endpoint for existing user

Hi, The first thing you'll need to do is to complete the FxA OAuth dance. We need to understand what's your client and in which context it work to know how the browser needs to be redirected to the right endpoint after the OAuth dance. Once this OAuth dance is finished, the server will retur

Loop releases schedule

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Folks, I've been asked a few times about the schedule for loop/hello server features, so here is a document that describes what we're planning to do, and when. https://cloud-services-fr.hackpad.com/Loop-releases-schedule-50doMx1GA5n It will be upda

Re: [loop-services-dev] Migration to MySQL for loop-server / hello.

On 23/10/2014 21:36, Adam Roach wrote: > In particular, what I dislike the most is that you're going to > introduce a moment in time where someone generates a URL, and then it > goes away almost immediately. > > So I think it would be good to have a migration plan in place here, at > least for some

Migration to MySQL for loop-server / hello.

(Cross posting to loop-services-dev and dev-media) Hi folks, We're planning to change our database implementation and go from Redis to MySQL in the upcoming weeks / months, in order to have Ops use the scaling properties of MySQL RDS on Amazon. We're not code-ready yet on the server side,*but ar

Re: WebRTC service database selection

(ccing bobm and genew hoping any interesting feedback from them) > As long as we create and maintain a good abstraction for our data store, I > think that we can switch if needs change. …always create and maintain a good abstraction for stuff like this. That's the most important thing. I don't h

Re: WebRTC Service: On temporary call URLs

Le 20/02/2014 18:15, Adam Roach a écrit : > The "version" allows us to transition between schemes in the future, > if we need to change the properties of the URL -- it allows us to > unambiguously change the format of the {token} [2]. For example, if we > decide to re-key the HMAC, we can increase

Re: WebRTC Service: On temporary call URLs

Adam, thanks for starting this discussion, Le 20/02/2014 04:52, Adam Roach a écrit : > Putting this together, what we want is something that semantically > evaluates to: > > http://authority/action/url-format-version/{serial > #,caller,callee,expiration,hmac} As Martin points out, URLs should not