Or perhaps commenting asap so that you have to wait the longest after commenting.
Or perhaps commenting asap so that you have to wait the longest after commenting.
It’s so useful you see it mentioned on every other thread
And for me: 4. It makes it a lot harder to accidently turn my camera on in meetings (a different form of privacy)
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).
Last I checked, Joplin does not use a folder structure that is easy to port over. Their files are all id’s instead of usable file names, so without Joplin, you won’t be finding anything.
They are still plaintext .MD files though.
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.
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.