From: Eric Wong <e@yhbt.net>
To: meta@public-inbox.org
Subject: browser history and cookies
Date: Tue, 21 Apr 2020 23:07:27 +0000 [thread overview]
Message-ID: <20200421230727.GA29392@dcvr> (raw)
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 :)
reply other threads:[~2020-04-21 23:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200421230727.GA29392@dcvr \
--to=e@yhbt.net \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).