This is what I've done too. I've tried a bunch of other keyboards from F-Droid, but haven't been 100% happy with any of them. So I'm using GBoard still with all network permissions disabled.
dracs
joined 2 years ago
Yes, the transcoding is done on the fly automatically. Plex automatically transcodes any media that the client doesn't natively support. Turning on burned in subtitles forces it to transcode to add them in.
You should be able to do this. I don't know if the first gen Chromecast supports native subtitles. But even if it doesn't, Plex has the option to burn the subtitles right into the video. It places some extra load on the server as it needs to transcode the video, but it pretty much guarantees compatibility.
O'Brian will unite all the warlords together (in the pattern buffer)
I don't think WebAuthn protects against cookie theft. WebAuthn better protects the login process. But if the result of the login process is still a session/auth cookie, that can be stolen like any other cookie.
I do the two profiles on mine as well. The Google profile isn't allowed to run in the background so it's only active when I'm using an app that really needs it. Down to just a single app now that needs it.
Software cracks leaving a calling card isn't unheard of. Companies before have been caught out before with names of cracking groups showing up in their files.
Edit: found the article I was thinking of. Turns out it was Microsoft themselves!
http://www.techpavan.com/2009/05/24/microsoft-deepz0ne-pirated-cracked-sound-forge-windows-xp-audio/
It's mostly a power efficiency thing. Before push notifications were the norm, most apps used a polling method. They had the application send a request every X seconds asking "anything new". There wasn't coordination between apps, so even every app checked once every 30s, it likely wouldn't be on the same 30s. This caused the device to wake up a lot and never let it switch into low power mode.
A push notifications system like FCM or UnifiedPush means only a single application needs to run in the background. It maintains a persistent connection to the push notification service and waits for a message. When it receives one it wakes up the relevant app and passes it the details.
Signal does have a fallback if FCM is unavailable. It supposedly uses slightly more battery, but I can't say I noticed it. I've swapped to using Molly which is a fork of Signal which implements UnifiedPush (among some other features).
I've never worked directly with FCM, but that's my understanding of the issue. I don't know about WhatsApp. But it may do the same thing as Signal where the notification is just a wake up call and then the app connects directly to the WhatsApp servers to get the actual message.
Anything using FCM will be effected. UnifiedPush which I mentioned I don't believe has an option to encrypt notification content either. Using it you'd already at least have the option of using a provider with a better privacy policy or self hosting it.
Yeah, it's possible to get it to work with password managers. I believe it has to do with ensuring the password field still exists on the page when the username is shown.