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.

Where do you find that?

I had already done that. The notification was there in the morning with DND on, but it still didn’t make any sound.

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.

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.

Can we just get a new Pixelbook instead?

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.

🙄

Make cargo shorts cool again

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.

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.

Because you want to verify 2FA is set up correctly before you log in again. What if it isn’t, and now you’re locked out of your account with no backup code?

It may be automated on the OS end, but does it confirm back with the website to make sure the codes are the same?

Except you didn’t confirm your 2FA codes to enable 2FA. You also don’t have backup codes you can download.

It may have worked for you, but that doesn’t mean it’s working properly.