Actor identification and path to commumity listings and teams

[nielskijf]

UID: USER-47DEQpj8 - would be nice:
• Convert the 32-byte hex value into a Base64 string.
• Example:
• Full Hex: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
• Base64: 47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZGHhSuFU=
• Resulting UID: ACTOR-47DEQpj8
• Trade-off: Base64 increases readability but introduces non-alphanumeric characters (e.g., /, +).

Base32 would be a little longer but use only alpha
ACTOR-47DEQpj8 as starting point, we might resolve to nickname if possible.
You can add it to a ticket because its just how the FE renders the info.

Check: https://base64.guru/standards/base64url
the only non alpha characters are - and _ it looks cleaner. and is still denser.
base64.gurubase64.guru
Base64URL | Base64 Standards | Base64
Base64URL strings can be used as URL addresses or filenames

Requirements:

• We need a way to resolve Catalyst ID to users, for use in the template and use for team creation down the line.
• The approach above is basic, but gives us the minimal functionality to do this.
• This will allow people to share Catalyst ID. as social requirement, and sets up our system to build towards more advanced collaboration and community listings (indiv, team, organisation)