mirror of
https://git.sr.ht/~seirdy/seirdy.one
synced 2025-02-25 15:50:05 +00:00
Switch to archived link after original got 404'd
This commit is contained in:
parent
c974a840da
commit
7e93db4f8d
1 changed files with 1 additions and 1 deletions
|
@ -15,7 +15,7 @@ syndicatedCopies:
|
|||
url: 'https://community.mojeek.com/t/a-clarification-on-google-page-annotations/2032'
|
||||
---
|
||||
|
||||
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:
|
||||
I agree wholeheartedly with [Google's Page Annotations](https://web.archive.org/web/20250126115122/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).
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue