Author here, was a bit surprised to see this here. I thought there needed to be a good zero-JS LLM site for computer people, and we thought it would be fun to add various other protocols. The short domain hack of "ch.at" was exciting because it felt like the natural domain for such a service.
It has not been expensive to operate so far. If it ever changes we can think about rate limiting it.
We used GPT4o because it seemed like a decent general default model. Considering adding an openrouter interface to a smorgasbord of additional LLMS.
One day, on a plane with WiFi before paying, I noticed that DNS queries were still allowed and thought it would be nice to chat with an LLM over it.
One interesting thing I forgot to mention: the server streams HTML back to the client and almost all browsers since the beginning will render as it streams.
However, we don't parse markdown on the server and convert to HTML. Rather, we just prompt the model to emit HTML directly.
> However, we don't parse markdown on the server and convert to HTML. Rather, we just prompt the model to emit HTML directly.
Considering the target audience it probably doesn’t matter but it sounds like this could lead to pretty heavy prompt injections, user intended or not. Have you considered that and are there any safeguards?
The domain is great by the way. Congrats on getting it!
It has not been expensive to operate so far. If it ever changes we can think about rate limiting it.
We used GPT4o because it seemed like a decent general default model. Considering adding an openrouter interface to a smorgasbord of additional LLMS.
One day, on a plane with WiFi before paying, I noticed that DNS queries were still allowed and thought it would be nice to chat with an LLM over it.
We are not logging anything but OpenAI must be...