From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@yhbt.net>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id 061CC1F5AD;
	Tue, 21 Apr 2020 23:07:28 +0000 (UTC)
Date: Tue, 21 Apr 2020 23:07:27 +0000
From: Eric Wong <e@yhbt.net>
To: meta@public-inbox.org
Subject: browser history and cookies
Message-ID: <20200421230727.GA29392@dcvr>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
List-Id: <meta.public-inbox.org>

Hey all, just wondering how many public-inbox WWW consumers
preserve browser history and cookies between sessions.
(I don't)

I'm not sure if it's worth my free time to do or even consider
further, but we could try experimenting with storing per-user
state as cookies so users can keep track of and easily skip over
messages they've already read.  No logins (ever) or extra server
storage required, though caching might be a tad more tricky.

It'll be non-intrusive and opt-in, so GPDR-compliant.  There'll
probably an extra "cookies" link next to the search bar where
"help" is.  Definitely no popups or JS needed.  Though HTML5
<summary> + <details> might be useful...

And somebody will have my eternal gratitude for implementing
<summary> + <details> in w3m :)