Spare time nerd, interest in infosec and privacy, F1 fan, appreciator of watches.
Avatar by Loading Artist https://loadingartist.com/character
Feeling nostalgic with today's choice of #watches and finally got round to playing with my camera again.
This is my Seiko Kinetic Arctura 5M42 which I bought new and wore daily for many years. It's now in far from perfect condition but has been well worn. The style is very much of-a-time so it doesn't get too much wrist time anymore but still runs well.
I was interested to learn this model made it into the Seiko Museum so it must be interesting! https://museum.seiko.co.jp/en/collections/watch_latestage/collect050/
I found out today that my (previous year) flagship #Samsung android device now requires a Samsung Account in order to keep the many pre-installed Samsung apps updated via the Galaxy Store. I don't need any "benefits" of a Samsung Account and certainly don't need the additional privacy disbenefits and extra (highly privileged) attack surface. I won't be associating a Samsung Account with my device.
Summary of the changes to the Galaxy Store policy are here if you're interested or may be affected by this: https://www.androidauthority.com/samsung-account-galaxy-store-access-3484730/
This is obviously unnecessary and seems like a really dumb idea from a security / vulnerability perspective.
Could anyone who has knowledge of how Android permissions work help me understand how an app's access to Web Browsing History works in practice?
When checking the Data Safety section on Google Play, some apps state that they collect Web Browsing History - would this be limited to Web browsing via the app itself (eg. Links clicked or browsing history via the in-app browser), or would the app be granted access to the DNS Resolver history of the device itself?
