You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Visit the marketplace at
https://market.android.com/details?id=org.ttrssreader
2. View permissions
What is the expected output? What do you see instead?
The "phone calls" permission is listed which allows the app to determine the
phone number of a device, serial-number of a device, whether a call is active,
and the remote-phone-number of the call. I expected that ttrss-reader wouldn't
actually need that information to operate.
Is that permission actually required, what is it used for? If it's not needed,
can it be eliminated from the list?
What version of the product are you using? On what operating system?
0.9.3, information gleaned from the marketplace
Please provide any additional information below.
One of the reasons I run my own tt-rss instance is to maintain the privacy of
my feedlist, and I'm likewise interested in the permissions requirements of
apps that I install on my device.
Original issue reported on code.google.com by m...@nyu.edu on 25 Mar 2011 at 7:15
The text was updated successfully, but these errors were encountered:
Hi,
the permission was used ti store the IMEI of phones when people entered their
mail-address as a "Donators Mail-Address" a while back when I provided some
features only for donators. The mail-address was appended and the complete
String was hashed and the hash was sent to my server to check it against a list
of known hashes.
Since I removed the limitations due to a lack of interest in the features by
the users this permission is no longer required nor used anywhere in the
application and will be removed with the next update.
Greetings,
nils
Original comment by nils.braden on 26 Mar 2011 at 12:16
Original issue reported on code.google.com by
m...@nyu.edu
on 25 Mar 2011 at 7:15The text was updated successfully, but these errors were encountered: