Technology

37742 readers

500 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

alyaza@beehaw.org

TheRtRevKaiser@beehaw.org

gyrfalcon@beehaw.org

rs5th@beehaw.org

coldredlight@beehaw.org

Los@beehaw.org

SemioticStandard@beehaw.org

TheRtRevKaiser@kbin.social

remington@beehaw.org

183

Google’s new Topics API makes users vulnerable to fingerprinting attacks (www.theregister.com)

submitted 1 year ago by RagnarokOnline@reddthat.com to c/technology@beehaw.org

34 comments fedilink hide all child comments

Google has stated it plans to address developers’ concerns by “making web publishers promise not to abuse the API”.

Google’s new browser-based tracking functionality available via their “Topics API” has sparked numerous concerns recently, including fear that the heightened communication of web browser history could lead to “fingerprinting attacks” which could be used to track users across devices by profiling recent web history.

When prompted with this issue, Google started their short-term solution is to have web developers who enroll in the new Topics API platform take pledge that they will not abuse the new tool, whatever that means.

you are viewing a single comment's thread
view the rest of the comments

[–] ConsciousCode@beehaw.org 33 points 1 year ago (7 children)

Daily reminder that Firefox is customizable to the point of removing Mozilla's telemetry and making it look and feel almost like Chromium. And no, de-Googled Chromium probably isn't enough because preliminary code for implementing WEI has been pushed upstream (basically they added the code which makes it possible for WEI to be implemented, strongly suggesting they're intending to actually implement it upstream and not in Chrome)

load more comments (4 replies)