Closed ilyaigpetrov closed 2 months ago
When I enable RUAdList, the only resource I see blocked at https://antizapret.prostovpn.org:8443/
is https://mc.yandex.ru/metrika/watch.js
.
Please provide more details about uBOL configuration and what exactly is being blocked as per network pane in dev tools.
Can't reproduce as of now.
@gorhill, could you, please, try with https://antizapret.prostovpn.org/proxy.pac
. This address is blocked in Russia so I always get timeout error with or without uBOL. If you get 403 then it works as intended (blocked for non-Russian clients).
Here are all the addresses that are tried and fail with installed uBOL:
https://e.cen.rodeo:8443/proxy.pac
https://antizapret.prostovpn.org:8443/proxy.pac
https://antizapret.prostovpn.org:18443/proxy.pac
https://antizapret.prostovpn.org/proxy.pac
uBOL conflicts with my anti-censorship extension, here are the logs from it:
https://gateway.pinata.cloud/ipfs/QmX5EgEy9c1vNCasj8SEwtXWbC2GvGXge4L3YjyoMh1az7/proxy-ssl.js
is blocked by client.
gateway.pinata.cloud
is in this filter: https://github.com/uBlockOrigin/uAssets/blob/9204a0be5a5ee8d007c88e4b104ec1794bf80dbf/filters/badware.txt#L3143.
pinata.cloud
is an ipfs-pinning service (https://ipfs.io), where any user may distribute any file through it's gateway at https://gateway.pinata.cloud.
Should I report the blocked address to them so they can ban it from the gateway? Is it enough to report just here?
@gorhill
cc @Yuki2718
https://antizapret.prostovpn.org
is an anti-censorship tool for Russia.https://antizapret.prostovpn.org/proxy.pac
is its pac-script that returns proxies for censorship circumvention. It also provides access on non-standard ports, e.g.,https://antizapret.prostovpn.org:8443/
.uBOL on Chrome blocks
https://antizapret.prostovpn.org
and doesn't block it on FireFox. I think uBOL mustn't block it. I believe it's a false positive which I report here.