Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

add homeUrlMirror or similar

See original GitHub issue

This one will likely be a very narrowly applying issue report, but it’s worth a shot. Most likely contingent on #696 being resolved first.

CloudFlare’s 1.1.1.1 DNS service, seems like a very probable candidate to be added to FilterLists.com once DNS addresses become eligible to be added as “lists” to the site. However, that service is notable in that it’s the only FilterLists-desirable site to currently also have an .onion domain: https://dns4torpnlfs2ifuz2s2yf3fc7rdmsbhm6rw75euj35pac6ap25zgqad.onion. As I used Tor Browser for a few months last autumn to do tests for Tor Redirector List, I can confirm that their .onion domain does work.

As it currently stands, only one URL may be added as homeUrl in filterlist.json. This means that only https://1.1.1.1/ (which is their homepage as well as their DNS server, a rare double-duty among DNS servers) could’ve been used as homeUrl, and not also https://dns4torpnlfs2ifuz2s2yf3fc7rdmsbhm6rw75euj35pac6ap25zgqad.onion.

The application of homeUrlMirror (or homeUrlAlternateDomain or something like that) doesn’t have to be limited to .onion addresses. If another filterlist server turns out to e.g. mirror its non-raw content across two domains, then homeUrlMirror could very well be used for that too.