Re: Firefox Developer Dashboard

This is one of the most popular Google developer service: https://developers.google.com/speed/pagespeed/insights/ You might want to check what looks like a really extensive offering from Google. Some of it is server side, but at the very least we should have similar services for web pages. On

FxA Q3 in Review

Hi All, As we prepare to ship the first FxA train of Q4 2015, let's also take a moment to look back at Q3 and what we achieved. It can be easy to lose sight of this when most of our meetings are about what's coming next, but we covered a *lot* of ground in Q3. Over the course of seven

Re: Improvements to how and when we decide to use cached FxA credentials

Hi, > After a user logs into Sync, many users expect to be able to log into > other FxA relying services (e.g., Hello, Pocket) without re-entering > their password. I am wondering if access-token could help us fix this issue in some ways. 1. You log into Firefox using your FxA credentials and

FxA Web Coordination meeting moved to Tuesday

Today is Thanksgiving in Canada and half of our team would/should be celebrating with friends/family. We have moved the FxA Web Coordination meeting & bug triage until tomorrow, Oct 13th, at 09.00 Pacific, 17.00 London. Shane ___ Dev-fxacct mailing list

RE: What's New in FxA: train-47 edition

You're welcome. I'm looking forward to continue contributing to Mozilla projects. Cheers, Nelson Pestana -Original Message- From: Ryan Kelly [mailto:rfke...@mozilla.com] Sent: 12 October 2015 05:07 To: dev-fxacct Cc: m...@nelsonpestana.net Subject: Re: What's

Re: Firefox Developer Dashboard

The pagespeed page is neat and all, but I think that pages like http://term.ie/oauth/example/client.php or https://developers.google.com/oauthplayground/ are closer to what we need to offer. When I think "Mozilla Developer Dashboard", I'm thinking something very different. We have a number of

FxA train 48 dev cycle

We are now 3 days into train 48, and as always, we have lots of interesting work scheduled. The full list of GitHub issues we have committed to this train is available on our Waffle board [1] in the columns labeled "now", "in progress", "in review", and "blocked". We have several ongoing,

Re: Android 6.0 and Auto Backup

+dev-fxacct, since this impacts the mooted Device Manager, and will be of interest. On Mon, Oct 12, 2015 at 11:46 AM, Michael Comella < michael.l.come...@gmail.com> wrote: > To recount today's Frontend meeting, we briefly spoke about conflict > between Firefox Sync & auto backup. We came up with

Re: Android 6.0 and Auto Backup

> > We certainly have the infrastructure to do this: we do something like this > on every device right now in order to recover the Android Account across SD > card manipulations. We would want special support to do this across > devices, and I'm not sure we want to. > To go a step beyond Nick's

Re: Improvements to how and when we decide to use cached FxA credentials

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/10/2015 19:51, Rémy Hubscher wrote: >> After a user logs into Sync, many users expect to be able to log >> into other FxA relying services (e.g., Hello, Pocket) without >> re-entering their password. > > I am wondering if access-token could

Re: Android 6.0 and Auto Backup

On 13/10/2015 09:08, Richard Newman wrote: > We certainly have the infrastructure to do this: we do something > like this on every device right now in order to recover the Android > Account across SD card manipulations. We would want special support > to do this across devices,