3

What does your feature entail? What is it for? How will it affect existing workflows or user experience?
One thing Brave nailed recently is Forgetful Browsing:
https://brave.com/privacy-updates/25-forgetful-browsing/

The idea is you can make the default to "forgetting" and then make positive exceptions for the sites you want to keep as you as surfing (via Shields ui in their case, likely per site Settings in Kagi). They nailed the UX IMO. It's reasonably straightforward yet powerful.

What are the exact ways that you see a user using your proposed feature? Please go into as much detail as possible, and provide examples of how other browsers/apps implement this feature, if applicable. If your feature suggestion adds on to an existing feature, how would it work into it to extend its usefulness?
Minimize the longevity of all unwanted cookie activity, but, without breaking sites.

  • Vlad replied to this.
    5 days later

    spicysalmon Please describe the requreired changes in the context of UX/UI.

        9 days later

        Well, here's how Brave does it, and I think it's fairly intuitive. You can flip the Forgetful Browsing feature on via "Forget me when I close this site" in overall preferences:

        Then, on a per site basis, you can override it if you want certain sites to remember you after tab close. See the "Forget me when I close this site" option here in their per site Shields UI:

        So for Kagi, at the moment, the equivalent is likely a setting in Settings -> Privacy and then a checkbox in the per site Website Settings to allow override.

          No one is typing