If I understand Ilya correctly what he wants to avoid is (the hassle of) the authorisation step when using OAuth. During this process you need to login to openstreetmap.org with your credentials and then confirm that the app is allowed to access the API on your behalf.
To see what is involved in practical terms you can try to use the HOT task manager, maproulette etc (or on a mobile device Vespucci, I assume Go Map! uses OAuth too, as any current third party app for OSM should). The authorisation is a one time process (per app) and as such I'm not quite convinced that the whole discussion isn't a solution looking for a problem, but Ilya is correct in that it does involve the hassle of people remembering their google/FB/whatever password. Naturally on a mobile device you want to minimize typing in any case so I'm mildly in support of at least investigating what this would entail (it is unlikely that we would use a proprietary solution in Vepsucci though, on other devices and with other apps the trade-offs might be different). The above is a separate but related issue to making the signup process "mobile friendly" see https://github.com/openstreetmap/openstreetmap-website/issues/894 for a longish discussion. Simon Am 24.12.2015 um 15:58 schrieb Greg Troxel: > Ilya Zverev <[email protected]> writes: > >> This can be made a part of a policy for allowing apps to use OSM >> official social accounts. > Can you explain what you mean by "OSM official social accounts"? > Perhaps it is just me that doesn't get it, but I am not following what > you really mean. > > > _______________________________________________ > dev mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/dev
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev mailing list [email protected] https://lists.openstreetmap.org/listinfo/dev
