6 ms·
Well, if you're comfortable with sending your youtube view history to another website. https://github.com/Anarios/return-youtube-dislike/blob/5c73825aadb81b6bf
by Gigablah 3y ago
Well, if you're comfortable with sending your youtube view history to another website.
https://github.com/Anarios/return-youtube-dislike/blob/5c73825aadb81b6bf16cd5dff2b81a88562b6634/Extensions/UserScript/Return%20Youtube%20Dislike.user.js#L403 https://github.com/Anarios/return-youtube-dislike/blob/5c738...
- Dig1t 3y agoha wow, thanks for pointing that out. I just uninstalled.
- sebzim4500 3y agoHow did you think it was working exactly?
- hxugufjfjf 3y agoPeople often use technology without thinking about or knowing exactly how it works.
- Dig1t 3y agoBy talking directly to YouTube, instead of this other random website.
- emodendroket 3y agoHow else could it work? I guess maybe a one-way hash would provide some level of anonymity but that's the best I can think of.
- pests 3y agoHow would a one-way hash even work? They already have a database of views for a video by its ID. If they hash those beforehand that solves nothing. They have the actual ID for that hash - they have to, cause they need to provide you data on it. It could work similar to how haveibeenpwned works - send a prefix of the video ID and respond with a list of all matching IDs with that prefix. The server only knows the list not the actual video. The client can pull the correct ID out of the list. (this was how HIBP worked before at least, IIRC)
- emodendroket 3y agoThey'd have to key the votes by the hash.
- pests 3y agoA lot of trust they don't keep a map from hash->id behind the scenes though for data they already have. Hell, a YT ID is 11 characters in a base64 character set. While a lot of possibilities, I do think the entire domain can be precomputed for some amount of costs.
- emodendroket 3y agoI didn't say it was a wonderful or even good scheme; I said it was the best I could think of.
- girishso 3y agoWell, YouTube already has it.
- zo1 3y agoThat's not a very honest way of phrasing whats happening there. Sure it "leaks" that you are retrieving this VideoID from this IP, but you make it sound like it's sending your youtube viewing history to some random website. Either way, I'm fine with this type of "leak" of data, as it's fundamental to an open web and can't be easily solved without cryptographic/hashing hoops. What's next, you want anonymity from the server that you're requesting content from, really?