Aug. 10, 2008, 08:51 AM
Aug. 11, 2008, 07:13 AM
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
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...
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
Yes, but our Guest is wondering what to put in those Ad_____ files.
I'm thinking that Proxo's configuration file provides a clue:
The title of the third line seems to be the focal point here, no?
Oddysey
I'm thinking that Proxo's configuration file provides a clue:
Code:
In = FALSE
Out = TRUE
Key = "Accept-encoding: Allow webpage encoding (out)"
Replace = "gzip, deflate"The title of the third line seems to be the focal point here, no?
Oddysey
Guest
Aug. 12, 2008, 05:38 PM
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!
@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!