This will be my last post on this suggested *improved feature*.
A couple of you seem to be on the thing about the size of the storage of the database for the names of the cookies. Woow! 2/3 of window users dont know how or if they even could turn off Windows File Indexer which stores every filename and directory on every partition in a database. You know how small of storage and fast it is to store say 1000 cookie filenames. The average person im sure has over a 200 gig hd, which is why the amazements of why it would be more of burden with harddrive space.
Disagree and agree is one thing, but when your scringe about the space in a database to store the cookie filenames is something else. I would remove all microsoft stuff except the barebones to make some space, but anyways...
Atleast it got mentioned that it would be ran by the devp's.
If its implemented fine, if its not, fine too. I just think after people see how well it works, it would make there life faster and easier with full cookie control.
My proposal to show the developers is this.
==================================================================
1. 'Keep' panel - Selected cookie names to keep. (stores cookie names)
2. 'Delete' panel - Selected cookie names to delete. (stores cookie names)
3. 'New' panel - All cookies go here until manually processed. (stores nothing - read from cookie directory each time)
4. A cookie process button to process the cookie system only.
~ All new cookies go into the 'new' panel (read from cookie directory).
~ Choose weather you want to keep or delete for future processing.
~ If your unsure if you want to keep or del a cookie, then just leave it in the 'new' panel it will be reread next time of program loading.
Press the process button:
~ All cookies in the 'Keep' are not deleted.
~ All cookies in the 'Delete' are deleted.
~ All cookies in the 'New' are not processed. (not deleted or added to the database.)
==========================================================
Here is why this system works so good and convient:
If you just visited 20 sites, which in turn you have 20 cookies and you want to keep 2 out of the 20 and you know you dont want any of the other 18 ever again (ad, stats, unknown sites, etc...cookies). Put your 2 in the keep and the 18 in the delete and hit the process button. Of course its going delete the ones you put in the del plus add them to the delete in the database along with adding the 2 to the keep (as it already does) . Now comes the great part of this design. Say next time you visit 20 more sites and theres 1 cookie (an auto login forum) you want to keep, but only 5 are new sites from the previous 20. Load up program and it rereads the cookie directory and removes the cookies that you have previously decided what you wanted to do with them from the 'new' panel automatcally, so now your new panel only shows 5 cookies and then you choose the 1 that you want to keep and put others to del. No more looking at all the old 18 cookies you wanted deleted the first time, so now your only picking 1 out of 5. Overtime this system will very much be appreciated for full cookie control.
CCleaner already does cookie control, so why not make it do full cookie control.
Note: I programmed this cookie system (its not a hard system to figure out) in java long time ago and it worked great for the few sites with cookies you want to keep. Trends Micro Antivirus has the exact same system implemented. They go one step further though. They actually have a database of ad trackers, stats, etc... and when you load up there cookie control, they have known unwanted cookies highlighted in red, so you automataclly know to put those in the delete. I switched to kis, so i lost the cookie system.
For the users that dont want to keep any of your cookies:
The system of cookie control you want is already built into Interent Explorer, which you load every day and does it on each exit and for the person that said that what if i came back in a month and checked my cookies, then there would be 100's, well you must not be too worried about those cookies being on your system or you would set internet explorer to delete them on exit and not wait a month or a week or so to load up CCleaner to delete them.
CCleaner is already a nice program and its purpose it to maintain your system as easy and convient as possible and implimenting a full cookie control system would be good.
Note: After i stopped using Trensmicro, i was told to come here and get CCleaner and it would do the same, but it doesnt and im not installing java or c++ developers programs, just to program this, which it could be in the CCleaner which i now use for the other things.
CCleaner is a really nice little system cleaner program.
When i was given the name CCleaner and was told it did what i wanted, i thought it stood for Cookie Cleaner. ahaha. Its just the first thing that came to mind after seeing the name. Im not real for sure what the 'C' means nor have i thought about it since, but not important.
Thanks for atleast going to take this to the coder department.
ps. Im not saying any of you repliers in this suggestion topic that want all cookies deleted are paranoid porn people that want all the porn cookies deleted and not stored in a database, so someone could load up and see what you want deleted, but if you are and they implement this, then just suggest a password protection to view the cookie part of CCleaner. The rest of us wont even know why your suggesting it. ![;)]()