I wonder, do you have so many canisters that those eight characters make a difference? I’ll take a look at the implications of increasing it and let you know.
In order to match the architecture of my projects, which are split across already-large repos containing about close to 10 canisters each, I ideally have to name the canisters as such:
ProjectRepoCanisterEnvSubnet
Example with short names, already a total of 26 characters: WaffleAdminCoreProdGLO
Example with realistic names, total, 31 characters: PancakeSettleExecuteProdFID
So the limit of 24 is often a pain,
and I end up with names that are hard to decode at a glance.
I wonder if it might be better to instead be able to group canisters under a group name (so canisters that relate to different projects can be grouped together). What do you think @jdelforge?
Sure, that could help to remove Project from the line.
But it sounds more like a workaround than the actual fix, and it’s probably more work for DFINITY than extending a max length.
And even with grouping, the limit would still bite.
CycleOps allows much longer canister names, so I end up having the full names in CycleOps, and a shorter version of them in the NNS. Not fantastic.
There may also be a layout angle here. I proposed a toggleable list view back in January (mockup in the thread), and the 24-char cap reads like a card-layout constraint that ended up in the data model.
That said, for a canister management page, a list view would be far more readable on desktop. And in small-width mobile view, 32 characters would still hold in one line with no ellipsis.