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.

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.

Just got another redirect, it's definitely still happening.

Yeah, this just happened to me with Authy. Doesn't work with Authy, but it does work with Google Authenticator.

The fact that Lemmy doesn't require you to confirm the 2FA code before enabling it on your account is nuts. This needs to be fixed.

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.