[spec] comments on the proposed gemini spec revisions

[Nathan Galt]

Not infrequently I see a proposal float by this list, and I think "You want beautifully clean HTML5 served up over HTTP. There's nothing wrong or even lesser with serving up beautifully-clean HTML over port 443. There should be more of that in the world."

That doesn't keep me from occasionally wanting this or that from the HTML-over-HTTP world on my capsule. The latest feature to cross my mind: capsule-author-supplied fonts.

And then I remember how fantastically *nice* it is to have so many easily-made clients, and how utterly refreshing that is compared to the HTML-over-HTTP world.

On Sun, Oct 17, 2021, at 7:52 AM, Devin Prater wrote:
> I'll own that. It would be nice, but I don't see it ever happening because smoll. I mean I respect it, and I guess we'd have to make yet another spec for one step up from Gemini but not quite HTML/CSS/JS, but too many standards...
> Devin Prater
> r.d.t.prater@gmail.com
> gemini://tilde.pink/~devinprater/
> 
> 
> 
> On Sat, Oct 16, 2021 at 10:56 PM Alex // nytpu <alex@nytpu.com> wrote:
>> I thought I was way overstepping my bounds when suggesting multi-level
>> lists for Gemtext in my post but now people want to de-facto require
>> full-fledged markdown in Gemini clients; my simple and miniscule
>> suggestion doesn't seem so bad now lol.
>> 
>> ~nytpu
>> 
>> -- 
>> Alex // nytpu
>> alex@nytpu.com
>> gpg --locate-external-key alex@nytpu.com
>> https://useplaintext.email/