Just to address this point, while I anticipate John and Ian's findings: > Richard, you said we will have "a growing forest of things that sync". It > would make our life easier if we avoid that when we can. Syncing is hard, and > it would be easier to build future services as cloud services or things that > interact with other cloud services. IMO, Fx Reading List is a natural fit for > a cloud service, even though that's not how it's currently built (it's a > local service, that we're talking about syncing - yuck) . Pocket is a > conventional cloud service -- it's not a syncing service like Dropbox or > CouchDB.
I agree. One of the things we need to think about (which this thread encapsulates) is how users manage the growing forest of *services*. (Forgive me if I sometimes say "syncing thing" when I mean "identity attached service". I don't view a Sync feature with a new user choice as being that much different to a new service that perhaps handles the same data type, which I think is a part of our different perspectives.) This is one of the conceptual gaps we need to think about: what are the differences between pushing pages to Delicious (a service) and pushing pages into my cloud-stored Firefox bookmarks (a feature of the Sync service), and why -- if we go that route -- do I get to choose whether to 'link' the former on each device, but not choose whether to check the box for the latter? And what if they converge still further, and the Delicious service plugin does bidirectional sync? _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
