[ufmace]

That's kind of the trouble with Gemini now. Since you can't send significant amounts of text to the server, you can't really make a message board kind of thing in pure Gemini. The content submission has to be done via HTTP or a terminal interface to the server.

But then, if HTTP is the simplest and most secure way to allow posters to make submissions, then is there really a point to allowing the messages to be read over Gemini? Might as well make a simple HTTP layout and have the whole thing run over HTTP.

[krapp]

>That's kind of the trouble with Gemini now. Since you can't send significant amounts of text to the server, you can't really make a message board kind of thing in pure Gemini.

Given the aggressive anti-complexity stance of Gemini, isn't that supposed to be a feature? A messageboard isn't a static text document, it doesn't belong there.

[ufmace]

It's on the protocol designers and promoters to determine what it ends up being of course. It seems like a bit of a mismatch to me right now. The client cert support as the exclusive way to identify users is a really cool feature of the protocol IMO, but it doesn't seem like it's very useful without dynamically rendered pages. It's certainly possible to do dynamically rendered pages now, but they're also of much more limited use without the ability to send complex data to the server using the same protocol.