Every app has access to an api that asks your phone to verify your fingerprint against the ones stored for the lockscreen. The phone then asks for your fingerprint and tells the app if it passed or not.
As the commenter pointed out, it's not an image of your fingerprint either. It's a hash that is stored on your phone that is likely unique to that device.
Or perhaps commenting asap so that you have to wait the longest after commenting.
Why would you think like that? No one on the internet (especially OP) would apologize for potentially being wrong smh.
And for me: 4. It makes it a lot harder to accidently turn my camera on in meetings (a different form of privacy)
For me it was much simpler to just add it as a line in the field in my router settings than trying to find a launcher that was better while looking decent.
I also like the look of the launcher minus the ads as well, so that might play into it.
I'm not worried about it breaking any features tied to the ads, and I haven't had any problems in like 2 years I've used it.
(On the shield 2019) If you block this domain with your dns ad blocker, the default launcher will only show ads for the YouTube, Google TV, and Google Play Store apps (not individual shows). I find these to be far less annoying as they use muted tones.
androidtvwatsonfe-pa.googleapis.com
If you have already setup your device and currently see ads, you need to reset the android tv home application data to get rid of them. This will temporarily show you the old dashboard, but the new one will load eventually (without ads).
Try blocking this domain manually and see if it works (it wasn't part of my native lists in my router's adblock)
androidtvwatsonfe-pa.googleapis.com
If you have already set up your device and currently see ads, you need to reset the android tv home application data to get rid of them. This will temporarily show you the old dashboard, but the new one will load eventually (without ads, in its place it shows a dark "Google play, Youtube", and something else that isnt very intrusive).
I like to describe this as a game of peekaboo.
Where's the vulnerability?
There it is!
Where's the vulnerability?
(Not opening eyes) Huh, I guess there are none!
This is what I have ended up running with nextcloud as the server.
I also have home assistant syncing to CalDAV so that I can automatically create/remove tasks.
Fun fact for shield owners:
If you block this domain with your dns ad blocker, the default launcher will only show ads for the YouTube, Google TV, and Google Play Store apps (not individual shows). I find these to be far less annoying as they use muted tones.
androidtvwatsonfe-pa.googleapis.com
If you have already setup your device and currently see ads, you need to reset the android tv home application data to get rid of them. This will temporarily show you the old dashboard, but the new one will load eventually (without ads).
While this definitely wasn't an okay response, I still prefer this transparency over every single response having to go through a filter/PR representative. At least we are closer to knowing what he is actually thinking.
Is this the straw that leads to LTT going full corporate mode?
If you live in the US, you can get your mail sent to your email inbox every day you are getting something that is directly addressed to you (i.e., not spam). It's called USPS Informed Delivery.
It doesn't always work if they get your address slightly off (say they put STE instead of APT), but it's a lot better than nothing.
If I had to guess, communities being deleted, instances going offline/being defederated etc
I use endeavorOS btw (arch fork)
Even if lemmy itself doesn't support it, there are plenty of ways to log visitors ips and correlate that data with lemmy to figure out who the user is.
EX: Using a revese proxy like cloudflare or nginx, which are both very common.
Even if lemmy itself doesn't support it, there are plenty of ways to log visitors ips and correlate that data with lemmy to figure out who the user is.
EX: Using a revese proxy like cloudflare or nginx, which are both very common.
Even if lemmy itself doesn't support it, there are plenty of ways to log visitors ips and correlate that data with lemmy to figure out who the user is.
EX: Using a revese proxy like cloudflare or nginx, which are both very common.