Imagining the Console Client

Imagining the console client:

% teamgroove team create --name='Fellowship of the Blues'
New team 'Fellowship of the Blues' has been created and is now your default team.
It has been allocated the unique code 3AF7265001B26521563726500CD, which can 
be used to invite other people to 'Fellowship of the Blues'.

% teamgroove team list
You are a member of three teams - keep it rolling!
[1] Vampire Metal Gurus
[2] Country Music Hoedown
[3] Fellowship of the Blues

% teamgroove team share --email [email protected] 
An invitation has been sent to [email protected] to join 'Fellowship of the Blues'

% teamgroove team join --teamid=3AF7265001B26521563726500CD
Welcome! You have joined team 'Fellowship of the Blues'

% teamgroove track add --ref=http://spotify.com/track/id/981797236 --rate=5
You have added 5* track ....

% teamgroove track vote --rate=3 --ref=http://spotify.com/track/id/981797236
You have given a 3* rating to .... 

% teamgroove track list --top=10
#1 4.5* 	Boogie Chillun
#2 4.3* 	The Thrill Is Gone
...
#10 3.9* 	Got My Mojo Working

Following on from a comment:

Finally, the commands appear to 'know' who is running them. Is this because there is first a log-in command or are you thinking that information is held in a config file somewhere?

There's no user-story for logging in or configuring settings, so as you rightly observe there's something missing. It is important to walk before running, so I propose the simplest addition I can think of.

% teamgroove
Welcome to teamgroove! You have been assigned the temporary 'nickname' of <67127CD85A>.
To personalise your nickname try 'teamgroove profile update nickname="XYZ"', where XYZ is replaced
by your glamorous on-line name (CrazyCacophany, Ringtone1337, etc)

% teamgroove profile update nickname=Steve
Nice to meet you, Steve.

I am deliberately avoiding any implication that there is a registration process since no user story actually implies that. This means that this fictional interaction is potentially decentralised and serverless. The alternative would be to require registration.

% teamgroove
Welcome to TeamGroove! Before you can use TeamGroove properly, you need to create an on-line
account with our servers. This account is only used to retain your playlists and we do not hold
any personal data. We regularly compile the top 100 tracks and other seasonal playlists from all
the fully anonymized playlist data, which we monetize to provide this free service.

I am OK with that [y/N] ....y
Password: *********** 
[Very Strong, woooh, you've been working out]

You have been registered and your private anonymous ID has been saved to ~/.config/teamgroove.json
Optionally you can provide your email address. We only use this to implement password recovery.

I would like to share my email address in case I forget my password [y/N] .... n
No problem.

Thank you so much for joining our little community of +1,000,000 and growing! Do visit our 
forum to find out what is happening at:
https://whatsup.teamgroove.org/

At the moment you do not have an online 'nickname', which is how you will appear to your 
teammates, and is used to tally your votes. Would you like to set one now?

I am ready to set my nickname [y/N] .... y
Nickname: WildBillHiccups

Done, WildBillHiccups. This has been stored in ~/.config/teamgroove.json
That's everything for now. We hope you enjoy TeamGroove! Goodbye.