It's because these apps that work in Android Auto also work in Android Automotive, which is Google's in-car OS that uses similar app design.
Hmm, not there for me. I subscribed for a month already so maybe that's why.
Yeah, I had already done that. I had the notification when I woke up, but it didn't play any sound.
I had already done that. The notification was there in the morning with DND on, but it still didn't make any sound.
Last night in my area we had a bad storm when we were sleeping, and because I keep my phone in DND mode at night I didn't receive any sort of audible alert despite having the "Override Do Not Disturb" checked.
This is because the Wireless Alert technically doesn't have a notification sound, it has some other type of sound (not media either) that is being blocked by DND.
You can't adjust these notification settings, as the OS prohibits you from changing Wireless Emergency Alert settings.
This is potentially a big issue - I don't want to miss and incoming Tornado alert because my phone is on DND mode. Google needs to sort this out.
Last night in my area we had a bad storm when we were sleeping, and because I keep my phone in DND mode at night I didn't receive any sort of audible alert despite having the "Override Do Not Disturb" checked.
This is because the Wireless Alert technically doesn't have a notification sound, it has some other type of sound (not media either) that is being blocked by DND.
You can't adjust these notification settings, as the OS prohibits you from changing Wireless Emergency Alert settings.
This is potentially a big issue - I don't want to miss and incoming Tornado alert because my phone is on DND mode. Google needs to sort this out.
This is crazy. Google is delaying a competitor to Apple's network so Apple can support it better? Of course they're going to slow-walk it.
The Find My Device (FMD) network was originally supposed to launch this summer, but Google is now delaying it over...
New? Nearby Share has been around for at least a year. The issue is no one knows about it, because as usual Google is horrible with branding.
They should have just called it "Google Beam" or something like that.
One note I noticed about USB-C dongles and headphones is that they need to be powered, whereas traditional headphones do not. So the headphones draw power from the phone, which then hurts battery life.
If there is one thing Google is committed to, it's being unstabally committed to all of its products.
Probably because the cat is already out of the bag there. Hard to reign them back in and they'd have tons of bad press if they do that.
For exactly the reasons you state - Google doesn't want ad blockers in their browser.
TWiT is definitely in trouble. The last time I listened to them, one of their advertisements was for... doing advertisements on TWiT. They were also pushing their subscription every chance they got.
Their whole network comes off as a bunch of boomers complaining about technology. I don't think they'll be around much longer.
I'm sure they have all hands on deck trying to recover the site, but yeah some communication from the admins would be appreciated.
Just be careful with it. It doesn't confirm that your code is correct before enabling it, and the way it gets set up doesn't work on a number of different authenticators (such as Authy).
Best way to do it is to enable it in settings add it to your app, and then while the settings screen is still open, open an incognito tab and try to log in.
When logging into lemmy.world the banner now says "Israel - ni**a style" (full word unredacted) and it starts linking to lemon party and a bunch of other NSFW sites.
It may be an isolated incident, but it would have been avoided had Lemmy confirmed the 2FA code before enabling it on the account. Like standard practice.
Besides, this issue refutes your entire premise - that automated 2FA set up is flawless.
See this thread: https://lemmy.eus/post/190738
It's an issue with many different authenticators, and it's an issue with the way Lemmy sets up its 2FA and doesn't do a confirmation afterwards. This needs to be fixed.
That doesn't address the issue. Yeah, that makes setting up a code easy on your device - but the code still should be verified and confirmed as working by the website before 2FA is enabled on the account.
Case in point: I used your revered "automated 2FA key implementation" for Lemmy in Authy. It set up the account in my Authy list, and 2FA was supposed to be working. I opened an icognito tab, went to log in, put in my 2FA code and... it didn't work.
Luckily, I still had my settings open in my other window and was able to deactivate 2FA.
The code should be tested and confirmed by the site before it's enabled. Otherwise you can easily get locked out of your account. This is standard practice when implementing 2FA on websites.
Right now, 2FA is half-baked. You can enable it and it gives you a link to sync it to an authenticator app, which only works on mobile. But there's no confirmation required to enable it, so you may think it's working with your code but it doesn't take. This will lock people out of accounts.
It really should be disabled until it's fully fleshed out. In the meantime, give us the option to send 2FA codes to the verified email on file.
UPDATE: Read this post here: https://lemmy.sdf.org/post/405431
It's clear that the Lemmy implementation of 2FA is flawed as it a) doesn't work with all authenticator apps, and b) doesn't verify the code is working before it enables 2FA on the account.
It needs to be disabled until this is fixed.
