Hi all — I help manage somosazucar.org, one of the local volunteer groups of Sugar Labs, the nonprofit behind the open-source Sugar Learning Platform originally developed for the One Laptop Per Child (OLPC) project.
SomosAzúcar has supported open education and children’s digital literacy initiatives across Latin America since 2009.
The domain expired on 2025-10-06, but due to a Postfix configuration issue on sugarlabs.org, GoDaddy’s renewal notices never reached us.
By the time we discovered the problem — about 35 days after expiration — GoDaddy informed us that the domain was already being prepared for auction, and that the only way to recover it would be to bid for it like any other buyer.
It feels wrong that a long-standing nonprofit project could lose its .org domain over a technical mail glitch.
Has anyone here faced something similar with GoDaddy or other registrars?
Is there any way to appeal to PIR (.org registry) or GoDaddy executive support to restore the domain before it’s auctioned?
Any advice or contacts would be deeply appreciated — this domain represents more than 15 years of open education work.
I sometimes use llm from the command line, for instance with a fragment, or piping a resource from the web with curl, and then pick up the cid with `llm gtk-chat --cid MYCID`.
Hey I felt bad that there was a longer delay and by making sure to lazy-load everything I could, I managed to bring down the startup time from 2.2 seconds to 0.6 on my machine! Massive improvement! Thanks for the challenge!
You triggered my curiosity. The chat window takes consistently 2.28s to start.
The python interpreter takes roughly 30ms to start.
I'll be doing some profiling.
Yeah I agree, I've been thinking about using Rust. But ultimately it's a problem with GTK3 vs GTK4 too because if we could reuse the Python interpreter from the applet that would speed things up but GTK4 doesn't have support for AppIndicator icons(!).
I've been pondering whether to backport to GTK3 for this sole purpose. I find that after the initial delay to startup the app, its speed is okay...
Porting to Rust is not really planned because I'd loose the llm-python base - but still something that triggers my curiosity.
Yeah absolutely, I've just got to point where I'm happy with the architecture so I'll continue to add UI. I've just added support for fragments and I've thought to add them as if they were attached documents. I've in the radar to switch models in mid conversation and perhaps the ability to rollback a conversation or remove some messages. But yeah, system prompt and parameters would be nice to move too! Thanks for the suggestions!
I suffer from the limitations of both X11 and Wayland. Some things work in one and not the other, it's a trade off. In Wayland I can use different scaling for each monitor (in exchange for a LOT of RAM). But in X11 I can use Barrier to share my mouse / keyboard with my other computer. So I use one when I have a second monitor and have to restart my session when I use a second computer :'(
I downloaded the 64bit Linux build and it has a strange executable called "payload". I moved it out of precautio and still launched the app, and it seems to work fine without this executable. What is this "payload"? Anyone know? A quick search didn't find anything relevant.
I am familiar with your port and found it unplayable on the XO laptop (although I commend you on your apparently painful task of making it run in the first place!).
While I appreciate your thoughts on the OLPC, I am more interested in Alan's thoughts on Sugar.
Hello Alan,
In light of the poor results of the OLPC project, in reference to the Children's Machine, leaving aside commercial factors, do you think the Sugar user interface is appropriate for the task? If not, how can it be improved, what is good/bad about it?