Gargoyle Forum

For the search problem: as per the commit notes, we can’t match the extension to the URL, only the domain itself. The extension is only sent after the link is fully encrypted. (It’s also not defined in the list of sites to attempt to skim searches from. So even if searches were unencrypted it wouldn’t show up)

As for blocking YouTube, I had a similar issue as Facebook. I think there’s probably two or three URLs which need to be blocked.

Good tutorial for Facebook. Looks like you found a third domain which I didn’t

Rog66 wrote:ok - even in a hex editor my restrictions.js looks nothing like that for some reason . Have created 2 new rules without editing and youtube is also blocked for both apps and browser by adding "domain contains youtube" Fantastic !!!!

You’ll have the “minified” version.
Still possible to do but very hard to read.
Might be better to replace it with the full version from the source code and then modify it.

Or wait for next build which should have the fix.

Have downloded the raw file and made the change to restrictions.js and rebooted but am still getting the same problem

I've created a rule to block youtube

I have firefox and chrome installed

reboot my PC and use both browsers to access youtube

chrome = unblocked
firefox = blocked

Its like google chrome has stored the encryption key and can no longer be blocked?

not sure its cache - I ran ccleaner to clear all caches and chrome still finds YouTube whereas IE and firefox don't

I wonder if they have hard baked the encryption key into google chrome?

ispyisail wrote:I wonder if they have hard baked the encryption key into google chrome?

It does something; maybe it runs Google DNS on its own because in the past when router based Adblock would kill a website, my sister would always use Chrome to get around the issue.

Yes if I block all external DNS (block port 53) chrome cant get to YouTube. As soon as I remove this Chrome can find YouTube but IE and Mozilla cant. As long as you're using the gargoyle router as your DNS you can block port 53 on the required hosts to overcome this.

Also despite rebooting not fixing the edit code yesterday when I made the changes Lantis suggested - this morning it seems to have resolved itself - must have been user error.

This change has fixed an issue I have had for ages - thanks Lantis !!!

I wonder if this has any effect?



edit: tested, didn't work

Yes if I block all external DNS (block port 53) chrome cant get to YouTube

Can you show us a screen shot of how you did this?

My tests didn't work?