-
-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add homeUrlMirror or similar #697
Comments
Hmm, in general, I would say we should decide on a single declarative home url if there seems to be more than one. But, a |
Yes! FilterLists.com’s very own .onion address - ❤️❤️❤️ |
@existential-fallacy Now that you mention it, I have been able to not only apply DomainVoider's .onion address as a regular viewUrlMirror, but also to make its subscription button green (since green seems to be one of Tor's signature colours). On the other hand, the .onion address for iVOID doesn't seem to work, my best guess for why being that its 0xacab project seems to currently be a private project. FYI. |
The iVOID repo is currently non-existent. Also they's got SSL going now so https: links function |
If we added a new field like |
If that's a major concern of yours, it is of course also possible to just use |
We now have a db field for |
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
infilterlist.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 ashomeUrl
, and not also https://dns4torpnlfs2ifuz2s2yf3fc7rdmsbhm6rw75euj35pac6ap25zgqad.onion.The application of
homeUrlMirror
(orhomeUrlAlternateDomain
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, thenhomeUrlMirror
could very well be used for that too.The text was updated successfully, but these errors were encountered: