It seems like the only internet protocols they didn't implement were the ones designed for chat. How could they forget about IRC, XMPP and SIP?
I'd love a deltachat bot too..
Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
31–40 of 75 posts
Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#32I find the fact that in this day people can own two letter domains absolutely staggering, based on rarity, those should be worth millions I guess?
I own vecs.ai and it's surprisingly hard to find buyers. Domains are really just Xoomer NFTs
Why would that one specifically find buyers? Do people commonly use vecs as a short for vectors or am I missing something?
Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#33Author 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…
Cool! Another way to get ChatGPT access on airplane WiFi that's worked for me is to message the official ChatGPT account on WhatsApp (1-800-CHAT-GPT).
Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#34I find the fact that in this day people can own two letter domains absolutely staggering, based on rarity, those should be worth millions I guess?
There's plenty still available. I bought an unregistered one last year for zero markup. Which reminds me, it needs renewing today.
Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#35Author 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…
Random thought popped i my head you could allow for cool setups/prompts as sub domains.
something.ch.at is some web space for somebody else's showcase. (within reason of course)
real cool idea, re: being able to use a LLM over DNS in a plane.
Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#36It seems like the only internet protocols they didn't implement were the ones designed for chat. How could they forget about IRC, XMPP and SIP?
No SOAP, CORBA, WAP or RS232 interfaces either.
Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#37It seems like the only internet protocols they didn't implement were the ones designed for chat. How could they forget about IRC, XMPP and SIP?
This is because when an account generates text in a chatroom it is generally referred to as a "bot".
They can create chatrooms dynamically so no one but the user will see them.
Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#38This is very clever - I was wondering if there could be a way to use LLMs on planes without paying for wifi (perplexity has been usable via WhatsApp but I’d rather use a different provider). Appreciate the privacy focus too
Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#39Earlier quoted context omitted.
This is because when an account generates text in a chatroom it is generally referred to as a "bot".
They can create chatrooms dynamically so no one but the user will see them.
That's wise, but how will the user protect against the host in those protos?
Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#40Author 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…
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.