issue not in app permissions. issue in restriction access to "cloud"
contacts got from 3rd party services, and so on
On 27.01.2014 00:21, Marcin M. wrote:
And wouldn't separate permission for each app solve the thing?
--
Marcin
2014-01-26 Bernd Wachter <bernd.wach...@jolla.com
<mailto:bernd.wach...@jolla.com>>
<christopher.l...@thurweb.ch <mailto:christopher.l...@thurweb.ch>>
writes:
> Hi Sven
>
> I am equally curious:
>
> Reading and rereading Bernd's mail I see
>
> " ..contacts synced to the device from some third party services..."
>
> I entered all the contacts on my phone myself (most via
bluetooth from
> the N9). No third parties are involved at all. So surely my apps
> should have full readonly access.
>
> If the source is an issue, then the source should be an attribute of
> each contact, thus allowing apps access to kosher contacts, and
> barring access to those from third parties.
That's what we're currently working on.
> Surely what an app does with the contacts is more important than the
> source of the contacts?
We need to follow the terms of service from where we sync the
contacts,
or they might revoke our API keys without warning, which then would
affect the whole userbase. In doing so we need to allow for creative
interpretation of the TOS on their end as well -- we're the ones in
trouble if they decide to revoke our API keys after all.
TLDR: Lawyers are making our contacts middleware unnecessarily
complicated, not all features implemented yet.
Bernd
_______________________________________________
SailfishOS.org Devel mailing list
_______________________________________________
SailfishOS.org Devel mailing list
_______________________________________________
SailfishOS.org Devel mailing list
