Community input: revisiting the project name

[jlengelbrecht]

Since this is a community project, I don't want to make a call on this in a vacuum. So I'm putting it to everyone. Nothing is decided. This is me laying out a real question honestly and asking what you think.
The question: should we revisit the "GlycemicGPT" name?

Why it's worth discussing

Two things have come up:

"GPT" is creating real friction. We have been blocked from sharing the project in several diabetes and self-hosted communities, and it got flagged on Hacker News . Specifically because "GPT" in the name trips AI-spam filters. That's a concrete, repeated cost to getting the project in front of the people it's meant to help. "GPT" also ties us to one vendor's branding (OpenAI's), when the project is deliberately model-agnostic. You can run it with Claude, Gemini, local models via Ollama, whatever you choose.
The name is narrower than the project. "GlycemicGPT" reads as "a GPT for glucose," but the project is more than a chat feature. There's a dashboard, an API, mobile and watch apps in the works. A name tied to one feature may not fit where things are heading.

The honest counterweight

Renaming is not free. We've built real recognition under "GlycemicGPT". The project, this community, our Open Collective, the domain, an in-progress grant application, and everyone who already knows us by this name. A rename means renaming the GitHub org (which breaks existing links), migrating the domain, updating Open Collective, and a fair amount of cleanup, with some permanent loss of the recognition we've built. The counter-argument is that we're still early, and if we're ever going to do this, it's cheaper now than after more users, docs, and integrations pile up.

Where I stand

I think the "GPT" friction is real enough to take seriously, and I personally lean toward exploring a name that drops it. But whether a rename is worth the cost and what we'd rename to, are genuinely open, and I'm not going to push a change through on my own.
If the consensus is "keep it," that's a real outcome and I'll respect it.

What I'm asking

Leave feedback in a comment below to show where your head's at (non-binding — just gauging sentiment).
Is the GPT friction worth a rename to you? What would you weigh differently? And if you lean toward a new name, what direction feels right? Naming ideas are very welcome — this is wide open.

If there's appetite to move forward, we'll do it deliberately and together, with a follow-up round to settle on the actual name.
I'll leave this open for about two weeks, then summarize where we landed and propose next steps.

[DanielDanielsson]

Thanks for raising this, I think renaming is the right move. The main reason I say that is because I want this project to go as far as possible, and if the current name is creating friction with communities, discoverability, and the broader vision of the platform, then it’s worth addressing.

And if the community decides to move forward with a rename, I’d be happy to help with the cleanup and migration work and brainstorm new names.

[seitzbg]

I fully agree that a new name should be explored given the current name will hold the project back and bring an unnecessary GPT association to it.

[palmarci]

I also had this idea before i saw this post. As a non native speaker i have never saw the word "Glycemic" until i came across this project, despite being T1D. It is also a bit hard to write :P

[richardchen874-sys]

I would lean toward exploring a rename.

The “GPT” friction seems real for two separate reasons:

• it can trigger AI-spam assumptions in communities where the project is meant to be shared
• it makes the project sound tied to one model family or vendor, even if the actual architecture is model-agnostic

For a project like this, the name probably needs to communicate trust, health context, and user-owned data more than “chatbot.” If the roadmap includes dashboard, API, mobile/watch apps, self-hosting, and support for Claude, Gemini, Ollama, or other local models, then a broader name may age better.

I would also consider the point raised by non-native speakers. If the name is hard to spell or unfamiliar even to some T1D users, that creates another small adoption cost.

Maybe the decision framework could be:

• easy to say and remember
• not tied to a single model/provider
• not likely to trigger AI-spam filters
• still clearly connected to glucose / diabetes / metabolic context
• broad enough for dashboard, API, mobile, watch, and self-hosted workflows
• safe and serious enough for health-related communities

A rename has migration cost, but if the current name is already blocking distribution and narrowing the project’s perceived scope, it may be cheaper to fix while the project is still early.