On Thu, Dec 6, 2018 at 6:26 AM bo0od wrote:
> - Connecting to Youtube directly , then you are putting your security on
> the SSL/TLS encryption. Whereas using in invidous hidden services your
> security is through the Onion hidden services design
>
One of the points made earlier though, is that
Im not the operator of the service but here are the advantages:
- Youtube is made by a dick company to humanity called Google, which is
funding their services by stealing/collecting users data. So the JS
which is closed source in case of YB prevent you from watching the
videos unless you allow the
I agree with Seth, this particular YouTube frontend/proxy seems to be
more focused on offering an alternative viewing experience rather than
privacy.
One interesting thing I have noted which may improve privacy (but still
does not outweigh the risk involved) is that this site provides video
playba
Seth David Schoen writes:
> if its operator knew a vulnerability in some clients' video codecs,
(or in some other part of Tor Browser, since the proxy can also serve
arbitrary HTTP headers, HTML, CSS, Javascript, JSON, and media files of
various types)
> it could also serve a maliciously modifie
bo0od writes:
> This is another front end to YouTube:
Hi bo0od,
Thanks for the links.
This seems to be in a category of "third-party onion proxy for clearnet
service" which is distinct from the situation where a site operator
provides its own official onion service (like Facebook's facebookcore
This is another front end to YouTube:
Clearnet:
https://invidio.us
Onion V2 Mirror:
http://kgg2m7yk5aybusll.onion/
Onion V3 Mirror:
http://axqzx4s6s54s32yentfqojs3x5i7faxza6xo3ehd4bzzsg2ii4fv2iid.onion
Special Thanks to Omar Roth for making this happen.
Source Code:
https://github.com/om
