Is your feature request related to a problem? Please describe.
nowadays I mostly create and edit anki notes/cards through AI agents. Sometimes they mix up note ID and card ID. Note ID and card ID have the exact same format and especially the fact that they can collide (i.e. a note and an unrelated card having the exact same ID) make it quite problematic and error-prone
Describe the solution you’d like
In a future refactoring, make note ID invalid as card ID and card ID invalid as note ID.
this can be as simple as prepending a char like n1321299133612 for note and c1321299133612 for card, or using a digit to represent note/card, e.g. first digit 0 is a note and 1 is a card like 01321299133612 and 11321299133612.
I dont know the details of the codebase. But this seems quite simple and backward compatible.
Describe alternatives you’ve considered
not sure.
They have the “exact same format” because they are Unix timecodes, representing the timestamp when that note/card was created. They have meaning. For instance, a note and its first card will often have the same IDs, because they were created at the same time. They don’t “collide” – they match. I expect there are unrelated notes/cards created on different systems at the same moment that have matching IDs too.
It’s unlikely that the format of these IDs will be changed, because they are used by the system as they are. The kind of change you propose would create forward and backward compatibility issues.
With all due respect to you (and none to your chatbot) – this sounds like a problem you need to work out with your chatbot and not expect Anki to fix for you. Perhaps your chatbot should figure out the difference between notes and cards, and learn more about Anki’s database structure (since those IDs aren’t stored in the same place, and shouldn’t be easy to confuse).