This was a good weekend of progress for side projects and learning. A couple weeks ago, I released FilterLists mainly to scratch my own itch because a similar resource was not available anywhere online. This weekend, the project got a tiny bit of publicity, and I began working on a first major new feature for the directory, learning a bit of Jekyll, PHP, and WordPress plugin development along the way.
Raymond Hill (Gorhill)
Gorhill is the maintainer and primary developer of uBlock Origin, an alternative to Adblock Plus with many more features, better performance, and a “better” business model (free, no donations sought, no paid whitelisting). I was tipped on Saturday afternoon that Gorhill had discovered FilterLists and was considering linking to it in the official uBlock Origin wiki. Raymond suggested, however, that it would be preferred if FilterLists was open-source.
I spent several hours on Saturday fiddling around with Jekyll, a static blog-aware site generator with official support by GitHub Pages. If I could migrate FilterLists to a Jekyll site hosted on GitHub Pages, it would allow me to offload server maintenance, and better crowdsource the upkeep of FilterLists. I was able to get a quick mock-up on a local development server with Jekyll, but I quickly realized that losing the many features of a dynamic CMS like WordPress would sacrifice too much functionality for the FilterLists roadmap. Additionally, since the content of a WordPress install is stored in a database, I am not sure that I could effectively open source the WordPress site on GitHub as it stands. FilterLists is theoretically still open source, however, as the code for WordPress, the plugins in use, and the actual HTML content are all freely available.
Instead, I decided to use my remaining free weekend hours to begin adding a new feature to FilterLists that I think users will find beneficial. While FilterLists aims to be comprehensive, many of the lists are no longer actively maintained. I thought it would be useful to be able to see, at first glance, the last modified date of the lists.
There were four different methods I brainstormed for acquiring the last modified dates of the lists.
Parsing the “Last-Modified” HTTP response header.
- Con: Most of the .txt files are not served with a Last-Modified header.
Scraping the “Last modified: ” date as reported on the list.
- Pro: Executed (ideally) asynchronously server-side.
- Con: Not all lists contain “Last modified: “.
- Con: Dependent on reported date in the list, not actual last modified.
- Pro: Most consistently available version of date from all lists.
- Con: Would seemingly require some weird, likely impossible cross-site scripting.
Maintaining a cache of all of the lists and comparing them to the most recent version from their origin server.
- Pro: The most accurate method for active lists.
- Con: Most time-intensive to develop.
- Con: Most resource-intensive to retrieve, cache, and parse all of the lists at regular intervals.
- Con: Non-functional for lists already stale/inactive.
For my first attempt, I opted for an easier version of the second option described above. In the first pass, I built a simple shortcode WordPress plugin, Link Last Modified Checker, to retrieve the provided URL and parse out the reported “Last-modified: ” date. This is currently working and live in alpha for the first five lists on FilterLists.
The problem is that, as it stands, when a request arrives at the server for the FilterLists directory, the server goes out to each list, parses the date, and compiles the final HTML response all in real-time. For five lists, this works in a reasonable amount of time, but if I enable it on all lists, the request would either take forever or likely timeout. I have a live question over on the WordPress Development StackExchange as to how to do this asynchronously which already has a solid answer that I hope to follow this evening.
In summary, FilterLists is now featured on the uBlock Origin Wiki, a new product feature is well underway, and I am more familiar with Jekyll, PHP, and WP plugin development.
Leave a Reply