All Projects → WaLLy3K → Wally3k.github.io

WaLLy3K / Wally3k.github.io

Licence: mit
Repo for Firebog hosting

Projects that are alternatives of or similar to Wally3k.github.io

additional-hosts
🛡 List of categorized undesired hosts
Stars: ✭ 13 (-96.96%)
Mutual labels:  blacklist, pi-hole, hosts, hostsfile
hosts
冷莫(trli)的规则唯一一个提供全球比较全的库Cold Mo (TRLI) rules is the only one to provide a global comparison of the library.
Stars: ✭ 4 (-99.06%)
Mutual labels:  blacklist, pi-hole, hosts
1hosts
DNS filter-/blocklists | safe. private. clean. browsing!
Stars: ✭ 85 (-80.09%)
Mutual labels:  pi-hole, hostsfile, blacklist
Blacklist
Curated and well-maintained hostfile to block ads, tracking, cryptomining, and more! Updated regularly. ⚡🔒
Stars: ✭ 492 (+15.22%)
Mutual labels:  pi-hole, hosts, hostsfile
hosts
🄯Curated lists of hosts files with various domain blocks.🄯
Stars: ✭ 15 (-96.49%)
Mutual labels:  blacklist, hosts, hostsfile
Neodevhost
The Powerful Friendly Uptodate AD Blocking Hosts 最新强大而友善的去广告
Stars: ✭ 336 (-21.31%)
Mutual labels:  hostsfile, blacklist
no-amazon
Completely block Amazon and its services
Stars: ✭ 42 (-90.16%)
Mutual labels:  pi-hole, hosts
Hosts
Python解析域名生成Hosts文件
Stars: ✭ 45 (-89.46%)
Mutual labels:  hosts, hostsfile
CyberSecurity-Box
Firewall-System based on OpenWRT or Pi-Hole with UnBound, TOR, optional Privoxy, opt. ntopng and opt. Configuration of the AVM FRITZ!Box with Presets for Security and Port-List. Please visit:
Stars: ✭ 20 (-95.32%)
Mutual labels:  blacklist, pi-hole
hostsfile
go tool for working with /etc/hosts files
Stars: ✭ 120 (-71.9%)
Mutual labels:  hosts, hostsfile
hostman
A hosts file manager
Stars: ✭ 19 (-95.55%)
Mutual labels:  hosts, hostsfile
anti-anti-AD
为什么不应使用antiAD去广告列表,以及选择更多优秀的替代品
Stars: ✭ 338 (-20.84%)
Mutual labels:  pi-hole, hosts
local-cname
Helper script to emulate a local CNAME DNS by writing to /etc/hosts
Stars: ✭ 44 (-89.7%)
Mutual labels:  hosts, hostsfile
pornhosts
Pornhosts a hosts-file formatted file of the RPZ zone file
Stars: ✭ 33 (-92.27%)
Mutual labels:  hosts, hostsfile
hosts.whitelists
Collection of whitelists hosts. See also hosts.extras [ https://git.io/J3b5A ] and StevenBlack's hosts project [ https://git.io/Je0XR ]
Stars: ✭ 27 (-93.68%)
Mutual labels:  hosts, hostsfile
porn-domains
A collection of domains used for explicit adult content like porn websites.
Stars: ✭ 97 (-77.28%)
Mutual labels:  pi-hole, hosts
autohosts
Automate hosts file updates on Linux and MacOS. Block Firefox telemetry, Google snooping and web trackers at the root.
Stars: ✭ 69 (-83.84%)
Mutual labels:  hosts, hostsfile
DNS-Sinkhole-Lists-A2
A DNS Sinkhole List for testing purposes. (not for use in production systems) - UUID: 0f90ca2c-4b0a-4fbe-b659-449ab30c4284
Stars: ✭ 19 (-95.55%)
Mutual labels:  blacklist, hosts
Youtube ads 4 pi Hole
YouTube script to add the new Ads list for Pi-hole
Stars: ✭ 1,151 (+169.56%)
Mutual labels:  pi-hole, blacklist
hosts
Generated hosts files from HostsZ goes here
Stars: ✭ 17 (-96.02%)
Mutual labels:  hosts, hostsfile

WaLLy3K's GitHub pages repo

This content is for my domain https://firebog.net as well as my Big Blocklist Collection.

Why use this over other sources?

Due to my DNS sink-holing experience (which I've been running on my very active household network since roughly 2013), I've been able to get a good feel for what lists cause issues and which don't. This experience lets me categorise the lists and, more importantly, provide easily accessible recommendations for you to implement into your network.

There's also the fact that there are very few sources of original blocklist content out there. A considerable percentage of lists I've seen is essentially the "I made this" meme, which leads to the following issues:

  • Cessation: Consolidated lists deprive the original list maintainer of visits.
    • If their visit count falls, it's reasonable to expect one would stop updating the list because their efforts are no longer appreciated
    • Lack of maintenance can lead to even less original blocklist content
  • Centralisation: You're letting one entity essentially dictate what can and can't be blocked
    • This puts a lot of workload on a single person to maintain changes to their consolidated list, potentially bringing into question how long a consolidated list will be maintained for, which could become an issue due to the "set and forget" nature of DNS sink-holing
    • The consolidated list maintainer may not always be up-to-date with the original list source
    • Additions and removals may not be passed upstream to the maintainer of that original list, benefitting more people overall

My goals are to:

  • Credit other maintainer's high-quality content by way of "direct hits" on their content
  • Make that content as easy to access for others as possible
  • Not require payment or to nag for donations
  • Have a transparent changelog thanks to GitHub's commit history

These goals ensure every interested individual or group can have better control over their Internet experience.

On a related note, I have zero interest in maintaining content inside various blocklists, except for the handful of domains I put into my blocklist which have cropped up here and there over the years because it was quicker to add to that list than submit to anyone else.

Found a false positive, but don't know which list contains it?

Run pihole -q blockeddomain.com, and it will return the URL of the block list.

Know which list contains the false positive?

Click on the big blue "Toggle List Maintainer Sources" button to show the source of a particular blocklist. Via the source page, you should be able to find the contact details for the list maintainer. Get in touch with them to remove the false positive - if you're not able to find the maintainer's contact details, please feel free to reach out to me.

Unable to find the list maintainer; they're unresponsive or have another issue?

Open a ticket here, and I'll be happy to see what I can do.

I attempt to reply to GitHub tickets and mentions as soon as soon as I notice open tickets, so by all means please ping me anywhere else that I frequent that's convenient for you. Also, note that if a ticket is closed, you are welcome to comment on it still if you have any question, comment or concern. 😃

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].