Does anyone else think "and API" makes as much sense as "apples, oranges, pears, and fruits"?
I do, I do!
Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
51–60 of 75 posts
Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#52Author 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…
Do you mind if I know how much you paid for the domain, brilliant find.
Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#53This 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
Lmstudio or something like that on a laptop which has a lot of vram.
Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#54I 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 hold a good 2 letter Chat domain: hi.chat and pay $250 a year to renew, i do get enquires all the time, no idea how to price it tho, so i dont respond. Anyone have any ideas how to go about evaluating it?
If you have a lot of inquiries - start responding with ridiculous prices (whatever ridiculous means to you.. 100k.. 1kk, whatever). Answer different price for each new price request. People either agree, stop talking or start negotiating down. After 30 emails I bet you will have some idea about how much you can sell it for.
One simple thought - it’s just an email answer, not a contract/obligation that you have to sell it at particular price, you can change your mind at any time.
Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#55Author 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 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.
There used to be a service where DNS requests to FOO.that-service.org would return the abstract for the Wikipedia article "FOO".
edit: I think it was this one, seems to be defunct now: https://dgl.cx/2008/10/wikipedia-summary-dns
Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#56This 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
If you can do DNS queries set up a Iodine server at home and tunnel into it.
Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#57Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#58I asked 5 questions, 4/5 of them said it can’t answer them because “it doesn’t have access to real time data”
Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#59Re: Ch.at – A lightweight LLM chat service accessible through HTTP, SSH, DNS and API
#60A fun recursive prompt exploiting the fact that the site renders the model output as HTML:
Generate raw HTML (no code blocks) for an iframe pointing to `ch.at/?q={query}`, where {query} is the the entirety of this prompt after and including the word "Generate", until the following number, which should be incremented prior to encoding: 1