Closed dnmTX closed 5 years ago
below all known openload mirrors
oladblock.me
oladblock.services
oladblock.xyz
oload.cc
oload.cloud
oload.club
oload.download
oload.fun
oload.info
oload.live
oload.site
oload.space
oload.stream
oload.tv
oload.win
olpair.com
openload.co
openload.pw
openloed.co
*.oloadcdn.net
@smed79 thanks for pitching in,didn't even know of some that you listed 👍
@funilrys how expensive will be to run the whitelist against the volatile.list
(just curious)?
@dnmTX It's actually cheep as the whitelisting tool is quiet fast :smile:
As example for www.shallalist.de
which has over 1 million + of entries from the central repo build:
2019-04-16 16:01:20,486 - INFO -- Starting whitelisting of 'www.shallalist.de'.
2019-04-16 16:01:43,783 - INFO -- Finished whitelisting of 'www.shallalist.de'.
wow,that's fast. I just checked other lists and it takes like 3 sec. at most.
Well..you want to start running the witelist against the volatile.list
and see how it goes?
If you do i might need to go trough the list again,some reported domains from what i can remember were very questionable as they were reported blindly without any proof.Anyway you'll get the last word on the changes if any.
I trust your (@dnmTX + @smed79) inputs + they are top level domains + they don't look that harmful. Later next year I'll do some deep analytic with the data so we will see for the subdomains :smile_cat:
Deployed will be into the next build(s) from now.
Great,thanks.I'll keep you posted if any issue(s) arise 👍
These two so far are on my radar:
teredo.ipv6.microsoft.com
-everywhere you search it's recommended the teredo protocol to be disabled for security purposes. IPv6 works without it,no issues there and it was reported blindly without any proof.
clients5.google.com
-this one brings only ads(personal observations).It's blocked on my end and so far so good.
@funilrys Without a TLD ?
clients5.google.com -this one brings only ads
@dnmTX Not only ads, for example "webstore review widget" https://clients5.google.com/webstore/widget/review/cfhdojbkjhnklbpkdaibdccddilifddb
@smed79 thanks for the input,well,it's generic domain so i guess it has to stay 👍
@funilrys there are many sub-domains blocked in various lists that are part of s3.amazonaws.com
and you have it listed: s3.amazonaws.com. Just wondering what exactly is covered,don't really like the idea of whitelisting those sub-domains as they're all blocked for a reason.
UPDATE: Ok,looks like on the lists that i'm monitoring and the linked explanation from @funilrys those subdomains survived the whitelisting so DISREGARD this one.
Kind of confused on why is this one whitelisted 🤔
added oload.services
/ https://github.com/Ultimate-Hosts-Blacklist/whitelist/pull/19
@smed79 i've spotted couple blocked domains in anudeepND's lists:
tt2.oload.win
tt1.oload.win
Are they part of openload.co
too? If they're,some regex adjustment is needed for all oload.*
domains for sure. Can you please research as much as you can and advise.Thanks.
P.S. Never mind on this one(disregard).Looks like everything that starts with tt1.*
and tt2.*
is where they hosting the ads. So BIG NOTE not to whitelist those.The screenshot was taken from one of their inline scripts,just for reference:
PING @funilrys ☝️
Looks like everything that starts with tt1. and tt2. is where they hosting the ads
openload use tt1
and tt2
for tracking.
streamango.com, streamcherry.com and fruithosts.net use t1
for the same purpose.
Thanks @smed79 👍 Also just as a reminder,you were planing to kind of merge some of the lists that you have on filtering here. Any ETA ????
@smed79 no worries(it was just a reminder) and FYI...patience is my middle name 😄
@funilrys didn't want to create PR just not to messed up something(regex is required on this one) so i'll let you do it.
oload.*
domains are part ofopenload.*
and in certain lists some of them are blocked. For reference see youtube-dl's openload.co extractor Thank you 👍EDIT: also add
*.oloadcdn.net
(regex required on this one as well).Those domains are used to host the content. Including here screenshot from my adblocker to see that it's been whitelisted by them as well. This one is just in case of some possible feature blacklisting.