this post was submitted on 22 Oct 2024
812 points (96.1% liked)
People Twitter
5108 readers
2370 users here now
People tweeting stuff. We allow tweets from anyone.
RULES:
- Mark NSFW content.
- No doxxing people.
- Must be a tweet or similar
- No bullying.
- Be excellent to each other.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Meanwhile, Google's like, "We're removing the ability to silently check your notifications using your Pixel Buds. You have to use the voice command now. No, we don't care that you primarily use them in public spaces. And we really don't care that our voice recognition has a 15% success rate."
That's shitty but I fail to see how the course of action there would be to start using the voice commands instead of just, you know, silently pulling out the phone and checking the notifications with your eyes.
Wow bummed for you on that
Someone raised the question of whether Google might have had a security concern. Since you can pick up ~~unpaired~~ headphones and listen to notifications from a locked phone. Though Apple does have a similar feature with AirPods: Announce Notifications.
Edit: not “unpaired”
I feel like I'd rather give hackers free access to all my devices than jump through all the security hurdles that are put in place to stop them.
I might not go that far but I feel that sentiment.
Ooh they could announce 2FA/MFA codes… maybe that could be toggleable
To be fair touching them also has about a 15% success rate to do what I intended it to do.
I dunno, I didn't have much of a problem with them unless my hands were wet. Occasionally couldn't make the triple-tap work, and maybe some issues with accidentally adjusting the volume. I found the "push and hold to play notifications" function to be super reliable, though.
90% of the time it triggers some random function for me when I am just trying to push it back into my ear (pause, skip forward, some sort of tutorial crap, notifications,...)