1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-12-25 18:22:09 +00:00
seirdy.one/content/notes/a-clarification-on-google-page-annotations.md
2024-12-01 16:35:55 -05:00

1.8 KiB
Raw Permalink Blame History

title date replyURI replyTitle replyType replyAuthor replyAuthorURI syndicatedCopies
A clarification on Google Page Annotations 2024-12-01T16:22:44-05:00 https://solarbird.dreamwidth.org/2018814.html googles latest fuckery: if you write online, read this BlogPosting solarbird https://solarbird.dreamwidth.org/
title url
The Fediverse https://pleroma.envs.net/objects/e6af9a73-ccc4-42a2-837e-cac2806794fb
title url
BlueSky https://bsky.app/profile/seirdy.one/post/3lcbkjdyrzk2z
title url
The Mojeek Discourse https://community.mojeek.com/t/a-clarification-on-google-page-annotations/2032

I agree wholeheartedly with Google's Page Annotations 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. Both ideally inform the user that the page has been modified. Page Annotations go well beyond that.