Name conflict with an existing BlitzCache project

[chanido]

Hey @ersinkoc,

I just came across your project named "BlitzCache" and wanted to reach out.
I've been maintaining a library with the same name since 2020: https://github.com/chanido/blitzcache

Because the names are identical, I'm already seeing some confusion popping up:

• Search engines are mixing both projects.
• LLMs are attributing parts of my project's history/tech details to yours.
• Developers searching for "BlitzCache" are getting conflicting info.

Not a huge drama, but I figured it's better to talk about it early so things stay clear for everyone using either project.

Would you be open to one of these options?

1. Renaming your package to something different or even similar like 'blitzcache-js' or 'wp-blitzcache' so it's easier to distinguish.
2. If renaming isn't doable right now, maybe adding a short note at the top of your README saying something like "This project is not related to the original .NET BlitzCache established in 2020."

Totally open to discussing it, just trying to avoid confusion for the community.
Thanks for taking a look!

[ersinkoc]

Hey!

Thanks a lot for reaching out and for the kind heads-up i. I really appreciate it.

You’re absolutely right that identical names can cause confusion in search results, LLM references, and general developer discovery. I’ve seen similar cases before, so it makes sense to address it early while things are still flexible.

The good news is that our “BlitzCache” isn’t a fully released or actively used WordPress plugin yet it’s more of an internal/experimental project name at this stage. We’re actually planning to group our future WordPress plugins under a broader umbrella brand anyway, so a rename on our side is totally doable and won’t break any production usage.

So from our perspective:
Renaming is not a problem, and we’ll likely move it under a different branding soon to avoid long-term conflicts.

And jokingly speaking 😄 if you ever decide you want the matching domain too, we can always talk about a “friendly developer discount” valuation.

In the meantime, until the rename happens, I can also add a short clarification note in the README to avoid any confusion with your .NET BlitzCache project from 2020.

Really appreciate you reaching out in such a constructive way. It’s always better when maintainers talk early instead of letting naming conflicts turn into ecosystem noise later.

Cheers,
Ersin

[chanido]

Hey Ersin,

Thanks a lot for the quick and positive reply, I really appreciate it.

Great to hear that renaming won't be an issue on your side, and thanks as well for adding the temporary clarification in the README.

I'm glad to see that people with good taste in names can sort things out so easily 😄

About the domain, I honestly never thought about having a website beyond GitHub, but if you're not planning to use it and prefer to avoid future confusion, I'd be happy to chat about it. No pressure at all.

Cheers,
Jose