1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-12-25 18:22:09 +00:00

new note: clarification on google page annotations

This commit is contained in:
Seirdy 2024-12-01 16:22:44 -05:00
parent 1feaf07878
commit 7017dbf175
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479

View file

@ -0,0 +1,15 @@
---
title: "A clarification on Google Page Annotations"
date: 2024-12-01T16:22:44-05:00
replyURI: "https://solarbird.dreamwidth.org/2018814.html"
replyTitle: "googles latest fuckery: if you write online, read this"
replyType: "BlogPosting"
replyAuthor: "solarbird"
replyAuthorURI: "https://solarbird.dreamwidth.org/"
---
I agree wholeheartedly with [Google's Page Annotations](https://support.google.com/websearch/thread/308719098/page-annotation-in-google-app-browser-for-ios?hl=en) being an absolutely *awful* antifeature, and recommend that others opt-out and/or protest the feature. I want to make a clarification that doesn't invalidate your main points:
Clicking annotations doesn't navigate away from your site to a Google search; it triggers an overlay with infoboxes about the term you selected. It's similar to the iOS "Look Up" option for selected text. It's wrong to do because this obfuscates what is and isn't a link the author placed on the page. Inserting what appears to be links into the page crosses the line from user-agent interventions, such as adblocking or turning off certain unsafe features (acceptable) to editing an author's words in a way that isn't required for people to read them (unacceptable).
Editing page contents is fine if it's necessary for people to read them, e.g. translations or the [WAI-Adapt standards](https://www.w3.org/WAI/adapt/). Both ideally inform the user that the page has been modified. Page Annotations go well beyond that.