this post was submitted on 27 Jul 2023
66 points (100.0% liked)

Technology

37712 readers
251 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

Also, Android users will soon begin seeing notifications for unknown item trackers that are traveling with them — no separate app downloads or installs required.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 12 points 1 year ago (4 children)

Is this saying that Google will get every device to log every Bluetooth device it detects, just in case one of them is then reported as missing? Like, what in the holy overreach stalker BS is this?

[–] [email protected] 8 points 1 year ago (2 children)

Remember that Google Streetview cars were sniffing Wifi networks back in 2010.

[–] [email protected] 3 points 1 year ago (1 children)

For what purpose? And also what does sniffing mean in this context? Just like.. finding them, or trying to connect to insecure ones or what?

[–] [email protected] 7 points 1 year ago* (last edited 1 year ago)

From what I recall they were saving all the packets being broadcast as they drove past. (as opposed to only logging SSIDs)

Edit: Yup, it is as I had thought - but also it was more intentional than I had remembered: https://www.wired.com/2012/05/google-wifi-fcc-investigation/

(unpaywalled link) https://12ft.io/proxy?q=https%3A%2F%2Fwww.wired.com%2F2012%2F05%2Fgoogle-wifi-fcc-investigation%2F

load more comments (1 replies)