11 ms·
Here is how I am using this: 1. Install the add-on. 2. Panic that it has deleted all "not open now" websites' cookies. 3. Choose the option to "Suspend Opera
by dotmanish 13y ago
Here is how I am using this:
1. Install the add-on.
2. Panic that it has deleted all "not open now" websites' cookies.
3. Choose the option to "Suspend Operation" via the add-on icon.
4. Repeatedly "Undelete" all cookies until it's all done.
5. Keep the add-on suspended.
6. Now, for the next few days, I will browse like normal, but will remember to "whitelist" the websites I like to stay logged-in (Hacker News, Webmail, etc.) by clicking on the add-on icon. Remember, it is still "Suspended".
7. After a few days of usage (and when I've re-visited enough number of my regular websites), I will "Resume Operation" on the add-on, where it can start destroying the rest of the cookies like anything.
I think the "Training Period" above in point 6 should have been by default. Somehow.
- ove 13y agoThank you for your feedback. I agree that the first-run experience makes for quite the adventure. Until a few months ago, I also considered the idea of starting the add-on in a paused state a no-brainer. After supporting my add-on for some time, however,I'm not so sure about that any more. There's a huge portion of users (probably not HN readers) that would not realize that the add-on is paused. Pop-ups, etc. only go so far. It's really about managing expectations and expectation mismatches. I hope that the portion of users who care about their pre-existing cookies overlaps with the portion of users who read the "What just happened to my cookies" blurb that pops up. I haven't had too many angry complaints since I added the undelete feature, so it might be working.
- medde 13y agoMaybe you could show a popup, only once after the addon is activated, with a list of the most popular websites and a check-box that could be checked if you want to keep current and future cookies for any selected one? and maybe a search box to add non-common ones