Need help with wally3k.github.io?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

WaLLy3K
432 Stars 28 Forks MIT License 261 Commits 2 Opened issues

Description

Repo for Firebog hosting

Services available

!
?

Need anything else?

Contributors list

# 6,996
PHP
Shell
CSS
Raspber...
230 commits
# 79,497
Nim
Firefox
Django
sony
3 commits
# 23,682
Python
octopri...
iot-app...
GraphQL
2 commits
# 71,250
CSS
HTML
blockli...
quantum...
2 commits
# 11,318
Python
pihole
python3
Raspber...
2 commits
# 195,286
raspber...
CSS
HTML
hostsfi...
2 commits
# 594,026
CSS
HTML
hostsfi...
blockli...
2 commits
# 52,266
PHP
ant-des...
entity-...
pihole-...
1 commit
# 370
HTML
Bootstr...
css-fra...
Jekyll
1 commit
# 207,930
Android
Kotlin
HTML
Shell
1 commit
# 186,125
Docker
persona...
Linux
syncthi...
1 commit

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. :smiley:

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.