Skip to content

Remove built-in YouTube link previews#138

Open
thomasbuilds wants to merge 1 commit into
GrapheneOS:mainfrom
thomasbuilds:patch-1
Open

Remove built-in YouTube link previews#138
thomasbuilds wants to merge 1 commit into
GrapheneOS:mainfrom
thomasbuilds:patch-1

Conversation

@thomasbuilds

Copy link
Copy Markdown
Contributor

The conversation screen special-cases YouTube links. When a message contains a youtube.com or youtu.be URL, it renders an inline preview whose thumbnail is auto-fetched from https://img.youtube.com as soon as the conversation is viewed. This happens with no tap and for received messages too, so merely opening a conversation that contains a YouTube link discloses the viewer's IP address and read time to Google, with no opt-out. YouTube is the only special-cased host (there is no generic link-preview mechanism); the logic is a leftover from the legacy AOSP YouTubeUtil.

This removes the feature so the app never fetches remote content from message content. Links stay fully tappable via the existing on-device TextClassifier link handling, which is unchanged.

@RankoR RankoR self-requested a review June 5, 2026 21:12

@RankoR RankoR left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@thomasbuilds it should be configurable in settings (off by default), not fully removed

I suggest adding a sub-screen - "Privacy" and add it there as a toggle, with a short description that enabling it may reduce privacy

@thomasbuilds

Copy link
Copy Markdown
Contributor Author

I don't see any reason to special-case this third-party website?

@RankoR

RankoR commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

@thomasbuilds it might be extended to other services in the future, especially if we manage to make RCS work one day. Plus, it's a pre-existing and compact (in terms of LoC) feature that improves UX (for those who want to keep it turned on), there's no reason to remove it if it will be opt-in.

But I agree that having it on by default (especially without the ability to turn it off) is a privacy issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants