Geminisphere

[Alex // nytpu]

> If clients would send referers, servers could collect (cache) and
> present those to clients asking for links _to_ the current page
> ("backlinks" in wiki parlance), thus creating an interconnected
> gemini sphere.
I'm gonna call a no on one of the worst parts of http. While we're at it
lets add cookies so servers can preserve state across sessions, which is
very useful functionality and definitely not something that already is
possible to do without substantial privacy invasions. It's funny
because http actually had client certificates first too (TLS RFC dated
August 2008) and then decided that cookies were definitely needed
(Cookies RFC dated April 2011).

> A more Gemini-style approach would be to have the client keep this
> information and add backlinks to the top or bottom of a text/gemini
> page when it displays one. That would give each page three kinds of
> links: a backlink, a forward link (one that the user has followed
> already), and a blue-sky link (one that the user has never followed).
This is an excellent idea, and you don't even need to extend the spec
for this.

I feel the need to reiterate this again: there are lots of creative
things clients (and servers) can do, that don't require *any* changes to
the spec. Caching? Done. Backlinks? Of course! Even if you can't code
I'm sure some client authors would welcome nifty and creative
suggestions like this.

-- 
Alex // nytpu
alex at nytpu.com
GPG Key: https://www.nytpu.com/files/pubkey.asc
Key fingerprint: 43A5 890C EE85 EA1F 8C88 9492 ECCD C07B 337B 8F5B
https://useplaintext.email/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201114/0fba99c5/attachment.sig>