Most of the use-cases you outline seem to suggest 'privacy' is the main 'feature'. I think we should be careful running with this as the **primary** user value proposition. As Ari said: *'users want candy, not vegetables'*.
1. What 'candy' can we offer them that they cannot already get through existing channels? 2. Can the underlying transports align with what FlyWeb is trying to do? --- IMO Mozilla could flourish in this space; we have two main tasks: 1. Create a safe, scalable, interoperable developer platform that applies lessons learnt from the web (giving us a head start). 2. Launch a shiny product that introduces the platform to consumers. --- Although, if the platform is **that** good, third-parties will want to build on it and Mozilla might not have to launch any user-facing products :) Wilson *W I L S O N P A G E* Front-end Developer Firefox OS (Gaia) London Office Twitter: @wilsonpage IRC: wilsonpage On Wed, Dec 16, 2015 at 8:37 AM, David Rajchenbach-Teller < [email protected]> wrote: > I'm not clear on the specifics yet, but I generally like this direction. > > Do I understand correctly that your proposal would be a combination of a > local cloud, a private cloud, interaction with third-party clouds, and > stuff that tracks which third-party clouds have your data? > > Cheers, > David > > On 16/12/15 08:42, Fabrice Desré wrote: > > Indeed, let me try to explain better what this is about... > > > > A web browser is also called a User Agent because we rely on it to > > access documents and code from remote, untrusted sources. It's great > > that you can trust your browser that nothing bad will happen when you > > load a page that includes a random <script src=...> element. However, > > your browser doesn't give you much control on the data that you produce > > online. One could even argue that it facilitated the emergence of > > massive silos of data that make little case of user control. > > So, I believe that beyond the browser, regaining control of our online > > activity calls for a new kind of User Agent. It will need to provide > > guarantees that your data and the code processing it are loosely coupled > > and under your control. It will also need to be designed so that we can > > access our data from anywhere, and allow 3rd party to write apps just > > like any other website (no store, no gatekeeper of any kind). > > > > Some use cases: > > - I want to store the data from my activity tracker, either on my local > > network or on a remote server I control. However, I'm fine with using > > 3rd party apps to get visualization & analysis of my data. That means > > pulling their code to run it on my data, instead of pushing my data to > > them. Also, that means getting the code to run in a sandbox that doesn't > > leak back to the 3rd party. > > - Once in a while, I create photo collages to print them. I'd like to > > use a service that does just that, but will not get access to the raw > > data of my pictures. Knowing which camera I use, the exact date, > > location etc. which is in the exif data is none of their business. > > - If I had a "smart" thermostat, I would like all the historical data to > > be stored in my database. And I want to be able to run algorithms on > > that data from different providers, to select the best one for instance. > > > > The FoxBox is the piece that would sit in your home network, gathering > > data from sensors and sending them commands, along with managing the > > storage part. It may also be able to display content on an attached > > device, stream sound to a remote speaker, etc. > > We'll build a way to access your data from 3rd party sites, both from > > the local network or outside of it. We'll let "background" processes > > process the data. > > > > There are still many pieces to fully figure out, and many choices to > > make. Comments and suggestions are welcome! > > > > > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
