[Longitude] Proposal

[Mikolaj Habryn]

It looks good to me! A bunch of the later meterstones could be done in
parallel, but I'm sure it'll evolve by the time we get there.

m.

On Tue, Jul 30, 2013 at 2:27 AM, Rubin Abdi <rubin at starset.net> wrote:
> https://github.com/longitude/core/wiki/v1-proposal
>
> I kind of highjacked that doc and turned into into general design of the
> thing. Should I rename it to something else? Anyhow, that's the just of
> what I was trying to explain over the meeting.
>
> The idea with this is to have a framework to do these three things...
>
> * Current location input, from a tracker app or other web service
> (FourSquare, Twitter, etc)
>
> * Management of location history, access control for input apps, access
> control from output apps and web services, access control for sharing
> with friends, all with rules such as geofencing or location fuzziness
>
> * Current location or location history output, to friends, apps (mobile
> or desktop), other web services (FourSquare, Twitter, etc)
>
> The first step to work on is building a server that can deal with simple
> input GPS with time stamp, store into a history of locations, retrieve
> and output last known location. Step two is build a simple tracker to
> update said location. Strep three is build something to map last known
> location. No security or access control, no fancy databases.
>
> Sound about right?
>
> --
> Rubin
> rubin at starset.net
>
>
> _______________________________________________
> Longitude mailing list
> Longitude at lists.noisebridge.net
> http://www.noisebridge.net/mailman/listinfo/longitude
>