uggly VS awesome-gemini

I first came across Gemini after making my own HTTP alternative TUI-over-the-wire protocol (uggly)[1].

Gemini has the same motives as I had when I started, but I didn't switch to it for all the same criticisms that are mentioned in the article (e.g. TOFU, no visualization support, no stream/data support, no cookies for login support, etc).

I'm really glad to see that the desire for a simpler protocol is still going strong though.

[1] - https://github.com/rendicott/uggly

I'm actually working on this. Component based over the wire TUI system. It's in a decent alpha state but I want to code and host some more sample sites before I start sharing a ton.

Protocol: https://github.com/rendicott/uggly

Client with gif demo: https://github.com/rendicott/uggly-client

> If you bothered writing a spec, it might as well be unambiguous, no?

Sure, people want unambiguous specs. However there is a list of literally dozens of working clients, servers, and libraries that were implemented based on the Gemini spec as is. Perhaps Daniels concerns are, in practice, not as important?

https://github.com/kr1sp1n/awesome-gemini#clients

I would also point out the hell that is the HTTP/1.0 and HTTP/1.1 specs, and that it took ~15 years for the HTTPbis group to remove all the contrary and ambiguous parts of it.

> His point is also to criticize the technical choices but that's fair game too.

Sure, but many of his criticizes are false. Full Stop. (servers and clients DO support TLS resumption. Proxying does work and there are multiple working examples, client's do server certificate validation)

Or don't make sense ("Gemini closes a TCP connection? HTTP figured out keeps-alives in 1996! This is bad design." HTTP has different access patterns. If Gemini had those access patterns it would be bad design. It doesn't)

There is a few gemini links on awsome-genini list.

I haven't tried them out, but usualy, awsome-* lists are good starting points.

https://github.com/kr1sp1n/awesome-gemini#services

oh I really like the concepts behind the Gemini protocol (https://github.com/kr1sp1n/awesome-gemini). Good to see a name drop here.

Firefox doesn't support opening Gemini links by default, but a range of clients capable of this exist, and, possibly, an addon as well. You would provide a certificate file to it as part of the configuration.

=> https://github.com/kr1sp1n/awesome-gemini * Repology has packages by operating system

You can also see if there is already built software on the awesome-gemini repository.

This tutorial will focus on using the simple Agate software to host your own Gemini capsule. There is a plethora of software to host your content, but I have found Agate to be simple and sufficient for my purposes. A collection of all things Gemini can be found here, which includes a list of server software. Let's get started.

For anyone looking for a fast way to dive into the "Gemini Space", I recommend you check out this list of resources (clients and whatnot): https://github.com/kr1sp1n/awesome-gemini.

Now, all you have to do left is to execute docker-compose up -d to start your server. After booting it up, navigate to your domain using a Gemini browser and you should see a nice page saying "Hello world!".