IP Leakage Fears Plague YouTube Privacy Advocates: 'It's Not Enough to Just Block Cookies'
Many tools discussed—Invidious, NewPipe, yt-dlp—are noted for blocking the YouTube user interface, but commentators repeatedly state this only mitigates cookies, leaving the user's IP address exposed.
The divide pits absolute security against perceived adequacy. One strong view, voiced by 'rune', demands users define their 'threat model' to determine if IP blocking is enough, or if protection from 'intermediaries knowing who you are' is required. Conversely, 'RogueBanana' pushes 'Grayjay with always on VPN and no account' as a 'good enough' setup. Others, like 'Gradually_Adjusting', question the sufficiency of mixed tools for archiving content.
The prevailing takeaway is skepticism. The raw consensus is that most solutions fail to address core IP visibility risks, regardless of which specific toolset is used to bypass YouTube's front end.
Key Points
#1Most popular privacy tools only block the visible YouTube user interface.
Commenters agree that blocking cookies does nothing to shield the user's underlying IP address.
#2Privacy hinges on defining the specific threat model.
'rune' emphasized that users must decide if stopping YouTube from linking activity to an IP is the goal, or stopping third parties from learning identity.
#3One technical setup is being promoted as a functional compromise.
'RogueBanana' specifically recommended 'Grayjay with always on VPN and no account' as a satisfactory path to privacy.
#4The complexity of the landscape suggests no single answer works.
The core arguments show a deep rift between those demanding complete data isolation and those accepting 'good enough' workarounds.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.