💾 Archived View for rawtext.club › ~sloum › geminilist › 001659.gmi captured on 2020-11-07 at 02:22:38. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2020-09-24)

-=-=-=-=-=-=-

<-- back to the mailing list

gemini+submit:// (was Re: Uploading Gemini content)

case me at case.codes

Sun Jun 14 04:50:59 BST 2020

- - - - - - - - - - - - - - - - - - - 

On June 13, 2020 2:56:35 PM MDT, solderpunk <solderpunk at SDF.ORG> wrote:

A couple of thoughts on this new line of discussion:
3. Dear God, when/where/how does it stop?! This was supposed to be a
simple, humble, protocol of limited scope!

To me, this is key and exactly where the web went off the rails. If this is embraced by the community it becomes a defacto standard; clients that do not support it will be considered less. This is what happened to mosaic and Netscape.

6. Does anybody else feel like we are just instinctively
re-implementing
the familiar history of the web without much caution or critical
thought?

Yes!

Why does this have to be a part of or associated with gemini at all? Why not build a separate protocol and client and build a community of authors around it?

In my mind gemini is a passive reader's tool. It gets all of the noise out of the way, advertising, comments, likes, social media distractions, incentives to grow audiences etc...

How about a protocol extension that says user input MUST NOT be persisted by servers?

Cheers,Case

-- Email domain proudly hosted at https://migadu.com