Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: "R.Wieser"
Newsgroups: comp.mobile.android
Subject: Re: ebook-reader permissions - no explanation given
Date: Tue, 28 May 2024 10:00:51 +0200
Organization: A noiseless patient Spider
Lines: 23
Message-ID:
References:
Injection-Date: Tue, 28 May 2024 10:01:11 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="63358c9a0b0197ea9a48143445c53fae";
logging-data="552024"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18X2kjDVHEXJV7cpff5oNYZ0blQAFd8fTiGQD+UlnzAqA=="
Cancel-Lock: sha1:CrCq4LChgn+Ch4/oo2BL5Skepbs=
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
Bytes: 1737
Andy,
>> "modify or delete the contents of your shared storage
>> Allows the app to write the contents of your shared storage."
>>
>> No idea why it would need to do that(1).
>
> Annotate, or remove books?
I did not consider the former (which is possible, but not expected of a
simple reader), but was thinking of the latter too.
But in that case, why would it need access to the *whole* shared storage,
and not an app-specific data subfolder ?
.... I just realized I should also take a peek at what the Graphene OS
considers to be "shared storage", and how it (possibly) can help curb
over-zealous (or just not quite trusted) apps.
Regards,
Rudy Wieser