It was thus said that the Great colecmac at protonmail.com once stated: > lel wrote: > > [...] but no one had formalized anything about it yet [...] > > This, and the rest of the paragraph, is correct as far as I know. I'd like to see > more discussion around the gemini write / titan protocol, so that we can get something > that people can agree on, and clients and servers can actually implement. > > I've talked kensanata / Alex, who created CommunityWiki on IRC, and we've discussed how > he was experimenting and pushing things ahead, but I don't think I'm alone in saying that > there should definitely be more discussion, an official spec, Solderpunk chiming in, etc. Not to put words into solderpunk's mouth, but I suspect he'd stay out of this conversation and as long as it isn't pushed as something that's mandatory, he'd be fine with this. As per more discussion, Alex is basing his work off this message to the list: gemini://gemi.dev/gemini-mailing-list/messages/001657.gmi with the slight change in that the path parameters are all separated by a ';', not a leading ';' and '&' for the others, which, okay, I'm fine with it. So to update it a bit: titan://example.com/post-handler/endpoint?size=1234&mime=text/plain titan://example.com/path/to/new/resource;size=1234;mime=text/plain titan://example.com/path/to/remove;size=0 The logic goes something like this [2]: if the request has a query, it's an upload of data---accept data. if the request has no query, and the path parameter (marked by ';') doesn't exist---error. if the request has no query, and the path parameter exists: if size==0, delete the resource if size>0, accept data and make the resource available. The 'size' parameter is mandatory; the 'mime' parameter is mandatory for non-delete requests, there may be other parameters that are specific to a host or implementation. I was also thinking that a request like: titan://example.com/path/to/resource with no query string or path parameters, *might* return meta information about the resource, like: size (mandatory) MIME type (mandatory) creation time (optional) modification time (mandatory) author (optional) version (optional) etc. (other, optional fields) Just an idea. > Don't get me wrong, I'm happy that there's real code and stuff that works. Same here. -spc
---
Previous in thread (4 of 5): 🗣️ colecmac (a) protonmail.com (colecmac (a) protonmail.com)