wingman-jr-addon / wingman_jr

This is the official repository (https://github.com/wingman-jr-addon/wingman_jr) for the Wingman Jr. Firefox addon, which filters NSFW images in the browser fully client-side: https://addons.mozilla.org/en-US/firefox/addon/wingman-jr-filter/ Optional DNS-blocking using Cloudflare's 1.1.1.1 for families! Also, check out the blog!
https://wingman-jr.blogspot.com/
Other
35 stars 6 forks source link

Does it make sense to leverage Cloudflare's DNS 1.1.1.3 somehow? #53

Closed wingman-jr-addon closed 4 years ago

wingman-jr-addon commented 4 years ago

https://blog.cloudflare.com/introducing-1-1-1-1-for-families/

Perhaps this could be used as a partial stopgap for video? Or some other usage as a blacklist?

wingman-jr-addon commented 4 years ago

Think it might be possible using the DNS over HTTPS provided by Cloudflare. See here for API example and here for the endpoint Note I need to try the family endpoint to make sure it supports the same query.

wingman-jr-addon commented 4 years ago

I tried this and it does seem to work. For example, here's the normal resolver against a known bad site:

> curl -H "accept: application/dns-json" "https://cloudflare-dns.com/dns-query?name=pornhub.com&type=AAAA"
{"Status": 0,"TC": false,"RD": true, "RA": true, "AD": false,"CD": false,"Question":[{"name": "pornhub.com.", "type": 28}],"Authority":[{"name": "pornhub.com.", "type": 6, "TTL": 2531, "data": "dns1.p06.nsone.net. hostmaster.nsone.net. 1581001896 43200 7200 1209600 3600"}]}

Now, if we check against the "family" sub-domain for filtering:

> curl -H "accept: application/dns-json" "https://family.cloudflare-dns.com/dns-query?name=pornhub.com&type=AAAA"
{"Status":0,"TC":false,"RD":true,"RA":true,"AD":false,"CD":false,"Question":[{"name":"pornhub.com","type":28}],"Answer":[{"name":"pornhub.com","type":28,"TTL":60,"data":"::"}]}
wingman-jr-addon commented 4 years ago

Released in 1.1.0