Technology

37708 readers

401 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

35 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

[–] OneRedFox@beehaw.org 5 points 1 year ago

Back when Chrome was the new kid on the block and people were switching to it from Firefox, Chrome gapped Firefox super hard performance-wise pre-Quantum/e10s. Firefox was still a single-threaded browser that would lock up if a tab had particularly nasty JS. The extensions also broke all the time because while XUL extensions could do anything, even tie into the actual browser frame, that was a maintenance nightmare that made it difficult to change anything and even harder to parallelize.

In the post-Quantum era here in 2023, you're definitely right that there's no real reason to switch from Firefox to Chrome. The practical performance gap has been closed, the extension system has stabilized and offers more functionality than Chrome's implementation, it's not actively trying to sabotage adblockers and anti-tracking measures, and is just all around better about privacy. It's time to call the powerusers and techies home.