Keeping the name of the service

[dessant]

Hi @soruly! I was wondering if you intend to keep the name of the service, I think it would be important for discoverability. I've seen the service is being referred to in multiple ways, but users seem to prefer calling it WhatAnime, and it also happens to be an awesome name for the product. Would you be open to converge under the WhatAnime name?

I've seen you changed domains recently, but it would be nice to still have a canonical name for referring to your service, and WhatAnime has the advantage of years of public awareness.

[soruly]

There are only two hard things in Computer Science: cache invalidation and naming things.
-- Phil Karlton

I think a proper name should reflect what it is and what it does.
And I think "trace anime", rather than "what anime", better reflect what it actually does.
It doesn't recognize anime like an AI (it has no machine learning at all), many are confused by the name, and I have always wanted to correct it (if I can restart everything from the beginning).
I've also thought of separating the database and application under two different names like:
ASVDB (anime scene visual database) and ASSE (anime scene search engine), but this is left undecided until I can (or should I?) separate them an make them operate independently. (and also need to check domain name availability for that)
Yes I know the name "whatanime" is widely used and it's now even more confusing hosting a service called "whatanime" (or "WAIT") on trace.moe , sorry about that.
But there has been too many 3rd party integrations that I can't just ask everyone to correct it.
Even myself struggle to rename official services like http://t.me/whatanimebot , too many users are using it.
For new users, it feels insecure when clicking a URL called "whatanime" goes to "trace.moe".

As a matter of trust, I'd recommend you should use "trace.moe" for the name of the service.

[dessant]

Thanks for the clarification, I'm going to replace WhatAnime with trace.moe in my extension.