-
Notifications
You must be signed in to change notification settings - Fork 527
Possible issues when fetching accounts restrictions #986
Comments
I would not go with marking such submitions as if accounts were not restricted. because then all accounts will be unprotected after fetching. i think it's better to have them at default restricted and if necessary manually allowed. |
A nice touch would be to save the account type (Google, Facebook, Whatsapp, On 20 December 2013 00:34, kaizokan [email protected] wrote:
|
Contacts and application restrictions could pose a problem too. |
I will work on this this weekend. |
I can work on finding the account type(s) to save, and implementing some sort of indicator, if you like. |
The next version of XPrivacy will submit if there were accounts, applications and/or contacts allowed. The crowd sourced restriction server has already been adapted to store and use this info, so even older versions of XPrivacy will get the correct restrictions. If anything is allowed the corresponding category will not be restricted to prevent problems. The function exceptions are fetched, so it is easy to allow an account and restrict the category with the correct exceptions. The crowd sourced restrictions web site has also been adapted to show the new information (column exceptions) |
Submiting account restrictions that are set to deny with only one account allowed could cause the voting system to set accounts restrictions to deny for users fetching these settings, which would make certain apps inoperable (WhatsApp for example) as acvounts need to be unrestricted to setuo the account.
Suggestion: Either mark such submitions as if accounts were not restricted or don't accept these submitions
The text was updated successfully, but these errors were encountered: