Content pfp
Content
@
0 reply
0 recast
0 reaction

JAKE pfp
JAKE
@jake
I believe the constraints in the Base Colors naming system are better than those of Twitter, Instagram, Reddit, ENS, and yes, even Farcaster channels. I can write about this in more detail but the key decision discussed at length with @phil was to not allow spaces or symbols (or emojis), not even “_” like Twitter or “-“ like Farcaster. When you have underscores, dashes, or spaces, there becomes a question of whether, for example, “Base Colors” or “Base_Colors” may be considered more valuable than “BaseColors”. Even if most people agree the version without spaces is more valuable, it is not 100% unanimous (see “base-god” channel on Farcaster), and without 100% certainty, there is some amount of uncertainty. The user has to make a decision, an educated guess. They have to have some doubt, whether consciously or subconsciously. That decision, that uncertainty, it’s something people prefer not to have. So we don’t make you make that decision. It’s just letters and numbers. No choice.
2 replies
1 recast
13 reactions

SydneyJason pfp
SydneyJason
@sydneyjason
What about CaPiTaLs vs CAPITALS vs Capitals? All the same or three different names?
1 reply
0 recast
1 reaction

JAKE pfp
JAKE
@jake
Good question. All the same for the purpose of determining if the color name is available or already taken. But user can choose how their name appears in terms of caps / lowercase on our frontend. Up to marketplaces to respect caps/lowercase choices or impose a standard i.e. OpenSea shows my “BLUE” as “Blue”.
0 reply
0 recast
1 reaction