A new INI option would be really useful for me right now - CookiesToDelete.
Currently there's a CookiesToSave option but the inverse of this would be really useful - being able to define cookies to remove in the INI file versus the current option which defines cookies to save.
Seems like it could be fairly easy to do - just do the inverse of what is currently being done.
One option would have to take precedence over the other I suppose.
Seems like it could be fairly easy to do - just do the inverse of what is currently being done.
not really because the program deletes anything not in the cookies to save, but a cookies to delete would have every cookie ever deleted (including ones that you may not want people to know were ever on your pc)
i.e how would the ini know what to do if I had only visted a site for the first time? What about the billion or so cookies that are for sites I've never been to (3rd party and 3rd party advertising cookies)
So if this option is set, why can't it assume to save everything except for the cookies identified in the option? Sorry...I guess I'm missing it. Thanks for the reply.
[opinion]because a list of 25-40 (a likely # for a cookies to keep list) is less than one of billions of cookies (a likely # of websites that exist that someone might not wish, or better yet, have no need, to keep); this in turn would result in a gigantic ini in your option [/opinion]
the developers do take any viable suggestions into account so this may still happen