@community Hey guys, looking forward to our next chat tomorrow. Just making sure you’ve seen @brndnkng’s great work here
We’ll be discussing that first, followed by a follow up on this
And we might get to a discussion and maybe some practical tweaks on how we’re using and highlighting user groups here on the forum.
See you tomorrow (well tomorrow for me at least) 
@community Great call all! Here’s what we discussed
This week @brndnkng will build on the survey draft, with the following
Finalising the list of questions (incl phrasing and list of options for each)
A paragraph-long introduction to the survey describing what it is and why we’re doing it
@Hakanto will finalise 2 to 5 questions about the person’s relationship with Resonate, which will be included at the start of the survey.
I’ll have a look at the mechanics of the survey, starting with talking with @melis_tailored:
@Hakanto will come to a landing on what community topics we’re going to embed on the new website, specifically
Once he’s decided on a what topics we want to embed, we’ll then ask @Timothee to assist in how best to insert them into the current design. @boopboop and I will do the actual implementation.
We’re going to run a competition to select a user playlist to feature in the player here on the community. @boopboop will be looking at the structure and mechanics of the competition.
p.s. @boopboop we’re all looking forward to a picture of that hermit crab, the fifth member on our call 
[Technical aside: I can’t undo my like. Does the option to unlike a like expire?]
Update. No… the functionality of like-reversal isn’t time based. It seems to be an immediate condition that is isolated to this thread. I suspect a parameter setting.
I’d rate this setting as ‘sub-optimal’: diminishes user’s control of their voice.
@community doing a trial run of a wiki poll app
Please check it out here - All Our Ideas - Bringing survey research into the digital age
Nice! However I think we should try using the native discourse polling here. Here’s where you can access it.
Building the ballot is the issue though, the poll assumes the items are already decided.
Doing a wiki post could be a solution but there’s the paranoia someone accidentally deletes someone else’s submission. A thread is also an option?
Thread is good. Also our old wordpress gravity forms toolkit is a good and easy way to build dynamic web forms.
See this for example:
@community giving an update that i won’t be on this week’s call. i have a friday deadline i must meet and don’t have the bandwidth to do that and finish my homework for our team tbh.
def down to pick things back up next week, and completely open to others stepping in/pick-up where i left off on the Mapping Diversity Survey
from my notes from our last call, we need another paragraph explaining why we’re doing it as well as flushing out the survey questions a bit more to be more inclusive. if anyone else is down with taking a stab at it, that’d be love.
if not, we’ll just pick things back up re: mapping diversity survey in a week or so
'preciate y’all
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).
Even if this is only a rough rendering it is very helpful, thank you!
I’ll digest and then perhaps have more questions. 
Minor correction. No, a ‘persona’ belongs to one and only one user = account, typically an email address.
The intention was indeed that listeners, labels and artists could have multiple personas, but at the moment I think we are planning for listeners to have one persona, multiple personas being reserved for artists and labels. That could be changed.
Thanks for checking my work, Nick!
Interesting, so a persona couldn’t be managed by multiple accounts?
Let’s say I am an independent artist on resonate and then I join a label. I have a persona for my music. I decide to give the persona to the label to manage. I wouldn’t retain any control over the persona? I may be misunderstanding.
It seems much better if this was more like a delegation of control which could be revoked at will by the delegator, like assigning someone as a proxy on your behalf. It would be odd to hand over complete control because I assume the artist would lose the ability to check their earnings and stats, not having access to the persona.
A delegating relation was envisaged. I’m not sure if it was implemented in the current version? From the user and membership API spec, see this comment:
Yes: There is a ‘delegate’ relationship that may be set by the originating owner of a profile. Either a label delegating control to the artist, or vice versa.
However, bear in mind It is important that a public release, legally issued under contract to a label should not be suddenly represented as an independent release, now that the artist is independent: two profiles may still be required, one under the label, and another as the independent artist. It should also be possible for the artist to create a separate profile that is the parent of both those profiles, one being the historic one under the label, and the current one. Of course the artist may have current and previous ‘personas’ under many labels, not just one.
If the ‘label’ relationship is just a looser ‘marketing agent’ setup, with no specific rights relationship to record, it may be perfectly OK for the ‘marketing’ agent to hand over the profile to the artist. It’s always the original owner that has to initiate the setting up of a delegate or the transfer of control, of course.
We have a very flexible profile system and even without a secure (and potentially complex) persona handover (think about transferring ownership of bank accounts as an analogy) there are workaround ways to represent the situation with only a little bit of duplication of profile information.
@community Thanks all for coming
No worries @brndnkng, we can continue next week 
This is version 1 of the competition. Each cycle of the competition lasts for a calendar month.
We can nominate any playlist, whether created by a human or machine. The playlist has to be two items or more.
We create a new topic each cycle, people nominate playlists by replying to the topic with an embed, or link of the playlist. This nomination period lasts for 2 weeks.
Nomination period ends, and poll is created in the OP of the competition topic with links all nominations in posts. Voting lasts for 2 weeks.
If the desired technical characteristics of a future ‘selector account’ are similar to those of the artist role / account and permissions - ie the ability to create multiple personas, with their own playlists and rich story / pictorial content, it’s straightforward from a back-end perspective - we just add another ‘usergroup type’ and they share the artist-level Role permissions. As you say, what the player UI / forum does with it is a different matter.
The key thing is to make sure that the player is associating playlists, releases, profile pictures and uploaded tracks with a ‘profile’ (persona, usergroup) and not directly with a user. Hope that is true!
