On Jan 3, 2014, at 4:39 PM, Chad Weiner wrote:
> Thanks, Chris. Fwiw, there have been discussions on this topic and that
> group of decision makers you noted is meeting early on Monday to try to forge
> consensus. But this is very helpful!
If you need input or answers from me, Richard, Ryan
On Jan 3, 2014, at 4:12 PM, Richard Newman wrote:
>> 2) In Fx29, we lay what technical groundwork we can for a future sunset
>> date, e,g, deprecation messaging channels.
>> 3) In Fx29, we lay what technical groundwork we can for future transition
>> strategies and upsells, e.g., starting to r
Hi Chad,
On Jan 3, 2014, at 4:39 PM, Chad Weiner wrote:
> 1. I think part of the hold up in agreeing to a "let 'em be" route has been a
> question of the "costs" of maintaining current and new sync. Some of those
> costs are what you identify as open questions around UX that need to be
> ans
> Yup. The FxA process ends with a (Persona) certificate, which gets
> submitted to the tokenserver to get the token that the Sync servers will
> consume. The Sync master key is derived from FxA's "kB" key. No changes
> to the Sync protocol (either the encryption or the schema / poll / merge
> / da
On Jan 3, 2014, at 5:02 PM, Brian Warner wrote:
>
> I don't know as much about the tokenserver (design or deployment) as I
> should, but if current-Sync is using it, then I imagine that we could
> run a single tokenserver that understands both old and new/FxA schemes,
> it will have a DB with a
On 1/3/14 4:42 PM, Toby Elliott wrote:
> It also raises the question of what FxA Sync is under this model.
> Simply the same Sync backend, with FxA auth and key stretching
> replacing the secret key?
Yup. The FxA process ends with a (Persona) certificate, which gets
submitted to the tokenserver t
On Jan 3, 2014, at 3:59 PM, Chris Karlof wrote:
> Hi all,
>
> I see today listed as the deadline for a decision on a transition plan. I
> haven't seen significant discussion on this over the last day or two.
>
I've also been asking for some clarity and getting a lot of different answers.
Th
Thanks, Chris. Fwiw, there have been discussions on this topic and that
group of decision makers you noted is meeting early on Monday to try to
forge consensus. But this is very helpful!
As I read over your plans, these are the questions that immediately jump
to mind.
1. I think part of th
> 2) In Fx29, we lay what technical groundwork we can for a future sunset date,
> e,g, deprecation messaging channels.
> 3) In Fx29, we lay what technical groundwork we can for future transition
> strategies and upsells, e.g., starting to record the Firefox version of
> connected sync clients.
Hi all,
I see today listed as the deadline for a decision on a transition plan. I
haven't seen significant discussion on this over the last day or two.
What I've seen is:
- https://wiki.mozilla.org/User_Services/Sync/Migration
- https://services.etherpad.mozilla.org/sync-migration
-
https://www
10 matches
Mail list logo
