Alright, short question – long answer.
In the context of the player and co-op, I advise for clarity that we refer to folks who create playlists and curate as simply “listeners”. Creating playlists and other potential curatorial activities will be features of listener accounts, or could be reserved to Listener-Members. But terms like “selector” imply a different role.
In terms of multiple nicknames for accounts, I’m still learning about the user API so there may be misunderstandings below. Here’s my current interpretation; tread lightly.
In the future, a Resonate account will be able to create and manage multiple personas. Personas have unique usernames. Personas can be managed by one or multiple accounts. Examples: an artist could allow a persona they’ve created to also be managed by their label. A persona representing a band could be managed by all of the band members, each through their own accounts.
The main way that personas manifest practically is as a page/profile on the player. If multiple accounts controlled the same persona, they would all be able to upload to a shared artist page, edit it, etc.
I’m not sure if these same principles apply to listener pages, and that’s where this starts getting weird. On the player, a listener page displays playlists made by that listener. The URL for this page is linked to the listener’s username, so anonymity would require a workaround for the playlist to be accessible.
At this point, page and user management happens on the Dashboard (which has the music uploader, artist earnings, stats, etc) and the ID server (which manages profiles, editing accounts, uploading profile pics, etc). The priority there is to make the Dashboard useful for artists’ needs. Listeners technically can log into the Dashboard, but don’t have much to do there.
SO ANYWAY, multiple nicknames,
VIA DASHBOARD - First, we’d reach a point where an account can switch between artist personas while using the Dashboard.
VIA PLAYER - Switching personas on the player seems a lot more complicated. Listeners switching between personas on the player may be possible, but would require UI work or development of a Listener Dashboard. My instinct tells me that listener features ideally be built into the player itself, as it already is the listener dashboard practically speaking.
VIA FORUM - I imagine implementing this Persona system would require an new and sorta unprecedented Discourse feature. Discourse requires a username to be linked 1:1 with an email address, unlike resonate personas. Maybe there is some feature out there that allows a Discourse account to manage multiple usernames from a single account and to switch between them, but I have no idea how Discourse would handle all the other aspects affected by this (trust levels, badges, groups, etc).