My main blog is now an "anonymous" gemlog. I use the kineto http proxy to provide a website version as well. I wrote a little deploy script that scrapes my posts and creates an atom XML feed (static doc) that kineto serves for those few people who want to stay up-to-date. Once a quarter, I batch up the recent posts and bcc a bunch of folks I like to keep in touch with. Some of them respond. This is what I do in place…
i installed Kristall to try this all out. Seems nice. Should I stick to it or is there a better client you'd recommend?
Project Gemini
191–194 of 194 posts
Re: Project Gemini
#192Earlier quoted context omitted.
The different experience is largely thanks to different content, not different protocol. The protocol just serves a gatekeeping role to keep the community small enough.
That's true to some extent, but it's also true that the side-effect of the protocol is that it results in a very different community. It's a bit like saying that the camping experience has nothing to do with not having access to electricity. Well, true but also not true.
In that sense, I suspect that OP is right and they could have achieved the same on top of, say, HTML 2 (https://www.rfc-editor.org/rfc/rfc1866).
Re: Project Gemini
#193Earlier quoted context omitted.
Are clients permitted/expected/tolerated to run off and fetch the contents of image links for inline display, once a page containing such links is retrieved?
Not really, in fact they're forbidden - those clients are spec-uncompliant.
1. gemini://geminiprotocol.net/docs/protocol-specification.gmi
2. gemini://geminiprotocol.net/docs/gemtext-specification.gmi
Re: Project Gemini
#194Earlier quoted context omitted.
Not really, in fact they're forbidden - those clients are spec-uncompliant.
Do you have a citation for that? I checked the protocol[1] and gemtext[2] specs but couldn't find it. 1. gemini://geminiprotocol.net/docs/protocol-specification.gmi 2. gemini://geminiprotocol.net/docs/gemtext-specification.gmi