💾 Archived View for gemi.dev › gemini-mailing-list › 000044.gmi captured on 2024-06-16 at 12:38:06. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-12-28)
-=-=-=-=-=-=-
This way the files themselves are still effectively plain text andit's on the browser to render text formatting Maybe it's one of those 'thigns that don't matter' things, especially when we're in an early stage of 'hey we are only sorta getting the bare basics working' but I felt it was worth considering for when rendering becomes more of a focus. Also hi, I'm new here. I unfortunately don't have any real technical background. I just like the idea of a sort of middle ground between HTTP and Gopher that's still 'advertising and bloat hostile.' Given my poor vision and my interest in low bandwidth networking a text centric thing suits me. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20200228/6702 6577/attachment-0001.htm>
On Fri, Feb 28, 2020 at 01:02:43AM -0600, Andrew Singleton wrote: > Also hi, I'm new here. I unfortunately don't have any real technical > background. I just like the idea of a sort of middle ground between HTTP > and Gopher that's still 'advertising and bloat hostile.' Given my poor > vision and my interest in low bandwidth networking a text centric thing > suits me. Welcome, glad you like the goals of the project! I had actually been planning to make a spec change this weekend, which would add to the text/gemini definition the verbatim text block idea (since nobody spoke out strongly, or even weakly, in opposition to it after my last email on the subject) as well as a *subset* of the strictly optional extra features we discussed, including e.g. headings beginning with # and non-nested unordered lists with *, both as per CommonMark. Further, after making that change I plan to decree "absolutely no spec changes for at least six months (or maybe three, let's see how extreme I'm feeling on Sunday), unless some kind of horrible serious problem is discovered (I can't imagine what that could be)". I don't even want to seriously *discuss* possible spec changes for that long. The reason for this is that we are operating far too much in a vacuum. There is still very little original content in Geminispace, and even less of it which isn't *about* Gemini. There are plenty of features in the current spec which nobody has used yet, as far as I know, or have not been used for anything other than fun little tests. We have multiple server implementations, multiple client implementations and now even a search engine! I have offered free Geminispace at gemini.circumlunar.space to anybody who wants it. It is high time for us to actually build stuff with what we have achieved so far. Cheers, Solderpunk
On Fri, Feb 28, 2020 at 11:44 AM solderpunk <solderpunk at sdf.org> wrote: > I had actually been planning to make a spec change this weekend, which > would add to the text/gemini definition the verbatim text block idea > (since nobody spoke out strongly, or even weakly, in opposition to it > after my last email on the subject) as well as a *subset* of the > strictly optional extra features we discussed, including e.g. headings > beginning with # and non-nested unordered lists with *, both as per > CommonMark. If you are adding a good portion of CommonMark to the specification, then why not make take a sub-set of CommonMark? For example:
It was thus said that the Great Ciprian Dorin Craciun once stated: > > Why not add a version like `text/x-gemini-2020-03`? > > Moreover section 6 of RFC 2046 (governing the MIME types) states: > > https://tools.ietf.org/html/rfc2046#section-6 > > ~~~~ > A media type value beginning with the characters "X-" is a private > value, to be used by consenting systems by mutual agreement. Any > format without a rigorous and public definition must be named with an > "X-" prefix, and publicly specified values shall never begin with > "X-". > ~~~~ RFC-6648 deprecates that practice (surprised me too when it was pointed out to me). So either: text/x-gemini-2020-03 or text/gemini-2020-03 would be fine. -spc
solderpunk <solderpunk at SDF.ORG> writes:
> The reason for this is that we are operating far too much in a vacuum.
> There is still very little original content in Geminispace, and even
> less of it which isn't *about* Gemini.
Definitely some of this is my bad. Life has really caught up with me.
Now that there's a search engine, I may start publishing my blog/phlog
to my Gemini capsule, rather than keeping my capsule separate. I can't
rely on security-through-obscurity to hide stuff I don't want on my
public web page anymore.
--
Jason McBrayer | ?Strange is the night where black stars rise,
jmcbray at carcosa.net | and strange moons circle through the skies,
| but stranger still is lost Carcosa.?
| ? Robert W. Chambers,The King in Yellow
---
Previous Thread: An outsider's view of the `gemini://` protocol
Next Thread: Regarding `gemini://` over NaCL (replacing TLS)