Hi,
Fisrt, thanks for allowing the web to be a cleaner space, really appreciate the efforts of everyone here
My service uses a websocket endpoint using .ml extension.
I found out that I now can't access it because of this rule in FR list and EasyPrivacy : .ml^$third-party,websocket
Why such a restrictive rule ? Are all .ml websites that bad ?
Thanks for your answers !
myinterview.com
Hi,
how we can help you without knowing what service are you using and what requests are blocked?!
read
rules#participation
viewtopic.php?f=91&t=2935
how we can help you without knowing what service are you using and what requests are blocked?!
read
rules#participation
viewtopic.php?f=91&t=2935
-
- New Member
- Posts: 3
- Joined: Sun Jan 28, 2018 10:22 am
Hi,
Sorry about this, didn't find how to edit the name of the topic...
Website to reproduce :
Click the "Apply with video" button and you will see in the console
Disabling Adblock makes it work again.
I was wondering why such a restrictive rule, especially on websockets (I don't think other lists have such a policy to block all .ml)
Thanks for your help
Sorry about this, didn't find how to edit the name of the topic...
Website to reproduce :
Code: Select all
https://widget.myinterview.com/demo.html#video-interview
Click the "Apply with video" button and you will see in the console
Inspecting the Adblock tab I see that it is blocked because of this rule :WebSocket connection to 'wss://myinterview.ml/2.12.0/socket.io/?EIO=3&transport=websocket&sid=fvDkgcnZeqycuBhVAAAe' failed: Error in connection establishment: net::ERR_BLOCKED_BY_CLIENT
.ml^$third-party,websocket
Disabling Adblock makes it work again.
I was wondering why such a restrictive rule, especially on websockets (I don't think other lists have such a policy to block all .ml)
Thanks for your help
Same too broad filter in easyprivacy
[mention]fanboy[/mention]
[mention]fanboy[/mention]
-
- New Member
- Posts: 3
- Joined: Sun Jan 28, 2018 10:22 am
Just tested it on the manual list, it's working great !
Thanks
Thanks