Hi Markus,
I can certainly provide the code to consume that interface in a standalone patch with stubs. I am already in there, so I can commit to that.
I have been looking at the filter format. The filter format is actually fairly complex. It supports regular expressions, and has features that cannot be translated formally to regular expressions, so it isn't like they could be translated to regular expressions for processing.
Perhaps a subset could be supported easily, but the full format probably needs a library, or at least a significant number of SLoC. I wonder if libjirara even supports the full spec. Perhaps some of their code could be reused and converted to a standalone library easier than rewriting entirely.
For reference:
https://adblockplus.org/en/filters
Ben
Original Message
From: Markus Teich
Sent: Monday, January 26, 2015 2:29 PM
To: dev_AT_suckless.org
Reply To: dev mail list
Subject: Re: [dev] surf alternatives for Adblock Plus, Privacy Badger, Self-Destructing Cookies, BetterPrivacy
tautolog_AT_gmail.com wrote:
> My patch adds a decidenavigation() callback, which is exactly where that
> interface would need to be called. I can add it to my branch with minimal
> effort, and even make a separate patch, but handling the dependency would need
> to be done in a way that conforms to the suckless philosophy. What do you do
> for that? Do you just offer it as a patch and let people solve the build
> porting themselves? Is there an example I can look at?
Heyho,
my plan was rather to adopt the two files by rewriting them to get rid of their
dependencies. They only seem to need some kind of list struct, so it should not
be too hard. Including libgirara just for adblocking is not acceptable imho.
--Markus
Received on Tue Jan 27 2015 - 01:49:14 CET