I just subscribe to YouTube premium to support my favorite application out there. I learn so much from the people who spend hours and hours making videos every month that I am more than happy to pay a measly $13 or whatever it is every month to YouTube.
Block YouTube ads on AppleTV by decrypting and stripping ads from Profobuf
381–390 of 659 posts
Re: Block YouTube ads on AppleTV by decrypting and stripping ads from Profobuf
#382Earlier quoted context omitted.
But who pays for the medium? Someone needs to. And YT offers an alternative where you can be the customer not the product.
That's a good question, and I think we haven't explored alternative solutions enough. As for me, I'm happy to pay for Netflix, Nebula, my VPN, and other services. I still pay, but I'm disappointed in Spotify, who is pushing more and more soft ads even on supposed ad-free plans. But a YouTube Premium subscription would be financing this ad machine and the decisions that come with it. Have you watched Shorts? No thanks…
Re: Block YouTube ads on AppleTV by decrypting and stripping ads from Profobuf
#383Earlier quoted context omitted.
There's no reason to allow arbitrary traffic in either direction other than convenience. If you want a more secure network, you block everything by default and narrowly open as needed.
That means I'll stop 99% of all outgoing traffic. Still interested in how to force all traffic to a proxy though.
Re: Block YouTube ads on AppleTV by decrypting and stripping ads from Profobuf
#384Earlier quoted context omitted.
Not a CF employee but I am pretty sure it's working as intended as they built and use this: https://github.com/cloudflare/mitmengine
Here's hoping that, if they do it, they'll start blocking corporate TLS mitm regimes too.
Re: Block YouTube ads on AppleTV by decrypting and stripping ads from Profobuf
#385I just subscribe to YouTube premium to support my favorite application out there. I learn so much from the people who spend hours and hours making videos every month that I am more than happy to pay a measly $13 or whatever it is every month to YouTube.
Re: Block YouTube ads on AppleTV by decrypting and stripping ads from Profobuf
#386Earlier quoted context omitted.
Here's hoping that, if they do it, they'll start blocking corporate TLS mitm regimes too.
Why? This isn't the 90s any more. You shouldn't use your employer's systems for anything other than work.
Re: Block YouTube ads on AppleTV by decrypting and stripping ads from Profobuf
#387[flagged]
We should only post stuff that is pro ads as ads support individuals!
You're really picking sides with the whole, no to Youtube, yes to Hulu. At the end of the day they are all corporations. If one corporation passes along some of the profits. It doesn't make it a good corporation. It just means their business model is that. If Google could not pay people it 100% would. They are not paying people because they are super kind, they are doing it as it attracts people to make videos. Which attracts people to watch ads...
Re: Block YouTube ads on AppleTV by decrypting and stripping ads from Profobuf
#388Earlier quoted context omitted.
Privacy might be what you're after. Open source and cross platform.
(With thanks to your grandchild) https://github.com/barre/privaxy seems definitely worth a look - thanks!
Re: Block YouTube ads on AppleTV by decrypting and stripping ads from Profobuf
#389Earlier quoted context omitted.
Pihole is still a wonderful application. I use it on my home network. One drawback that the pihole has vs pfSense is pihole cannot do anything about devices that have hard coded DNS ips (aka 1.1.1.1 or 8.8.8.8 etc).
The hardcoded issue is more of a consumer router limitation than a pihole issue. Any router that can redirect DNS request + dnsmasq can do what pf-blockerng does. You just don’t see it since pfsense does this in the background. All my ubiquiti stuff or Opnsense uses pihole fine with hardcoded DNS including chromecast (I use NextDNS instead of pihole but essentially the same thing).
Re: Block YouTube ads on AppleTV by decrypting and stripping ads from Profobuf
#390Earlier quoted context omitted.
Not a CF employee but I am pretty sure it's working as intended as they built and use this: https://github.com/cloudflare/mitmengine
> We consider an HTTPS connection to be intercepted when there is a mismatch between the expected client request signature corresponding to the browser identified by the User Agent, and the actual client request fingerprint of the request. Sounds like something that would be "trivial" to defeat, by means of "emulating" other TLS implementations more closely?