Best way to add site specific filter?
|
Aug. 10, 2008, 08:51 AM
Post: #1
|
|||
|
|||
Best way to add site specific filter?
Should I add JS keys, comments keys, host keys to the block files?
OR I should create a filter specific for the site? Which way is better ? |
|||
Aug. 11, 2008, 07:13 AM
Post: #2
|
|||
|
|||
RE: Best way to add site specific filter?
Exactly what do you mean by "keys"? Do you mean a filter whose function can be altered by hitting a certain key on the keyboard?
|
|||
Aug. 11, 2008, 04:00 PM
Post: #3
|
|||
|
|||
RE: Best way to add site specific filter?
i believe s/he is referring to the .ptxt/.txt files (AdKeys, AdComments, AdHosts, AdDomains, et cetera)...
me personally, i keep the .ptxt (which i rename to .txt per OS-based preference) files as-is, as sidki officially released them as (the only file i edit is the IncExc-U file)... of course, that also means that my sidki config is 305 KB, where my sidki-based every-day-use config is 459 KB (my config with all of my site-specific add-ins)... ie, just shy of 51% larger... |
|||
Aug. 12, 2008, 12:44 AM
Post: #4
|
|||
|
|||
RE: Best way to add site specific filter?
Yes, but our Guest is wondering what to put in those Ad_____ files.
I'm thinking that Proxo's configuration file provides a clue: Code: In = FALSE The title of the third line seems to be the focal point here, no? Oddysey I'm no longer in the rat race - the rats won't have me! |
|||
Aug. 12, 2008, 05:38 PM
Post: #5
|
|||
|
|||
RE: Best way to add site specific filter?
thanks for responses.
@ProxRocks: Although the total size of the config set maybe larger than reusing sidki's matching structures, I think this is the better way. Thanks for sharing your experience! |
|||
« Next Oldest | Next Newest »
|