A playlist shared by a group, each on their own service
A shared playlist is one playlist for a group of people who don’t all use the same service: one listens on TIDAL, another on Spotify, a third on YouTube Music. Each of you keeps your own copy on your own service, and Trackhop keeps the copies in step: a song added by one of you shows up for the others, a song taken out goes from everyone’s copy.
There is no public playlist and no server of ours in between. The group’s changes travel through a folder you already share (a Google Drive, Nextcloud or Dropbox folder, or a Syncthing folder), through an encrypted ntfy channel on ntfy.sh or your own ntfy server, or through your own Trackhop server (Docker) when one of you runs one.
Three ways for the group to meet
The person who creates the group picks one; everyone in the group uses the same.
A shared folder. Each member’s Trackhop writes one file in the folder and reads everyone else’s. Who can read the group is who can open the folder: the files are not encrypted, so the company that stores the folder (Google, Dropbox, your Nextcloud’s host) can read them, as it can read anything else you keep there. The invite holds no secret: on its own, it lets nobody in.
An encrypted ntfy channel. No folder to share: the changes travel through an ntfy server, ntfy.sh or one you run yourself. Everything is encrypted on each phone before it leaves, with a key only the group has; the server sees messages it cannot read on a topic named after that key, never the group’s name, its songs or its members. The key travels in the invite, so anyone with the invite can read the group: send it only to the people you are inviting, and not in a public place. The server does see that someone sends and fetches messages, and from which internet address, as any server you connect to does.
My Trackhop server. For someone who runs Trackhop on Docker and has set Settings › Advanced › Coordinate with my server in the app. Creating the group makes a mailbox for it on that server, with a key for that group alone; the key travels in the invite. The others need no account on the server: the key opens the group’s mailbox and nothing else there (not the server’s syncs, settings or accounts, nor any other group). Again, anyone with the invite can read the group: send it only to the people you are inviting. What the server keeps is not encrypted: whoever runs it can see the group’s songs (titles, artists, ISRCs), the members’ names and services, and who added or took out each song, and when. Who is a curator they can work out too, from the signed list of curators, but they cannot change it, nor change the playlist: the server only stores what the members’ phones signed, and each phone checks every signature itself. The server also sees which internet address each member syncs from. A server that is off or unreachable only delays the group: changes wait on each phone until the next sync. Nothing is deleted by age, so someone back after months catches up from where they were.
Whichever way, reading is not writing: changes count only when a curator signed them (see below), so someone who got hold of the folder or the invite can follow the playlist but not change it.
Who changes what
- Curators change the playlist for everyone: what they add or take out reaches the whole group. The person who creates the group is the first curator, and can make anyone else a curator too. A group always has at least one.
- Everyone else follows: they receive the changes, nothing they do reaches the others. Each
person who follows picks how their own copy behaves:
- Exact copy: their playlist stays the same as the group’s; a song they add themselves is taken out again, a song they take out comes back.
- Keep my additions: what they add stays in their own playlist only, and is never sent.
Roles are kept by the app itself, not just shown on screen: every change is signed with its author’s key, and the list of curators is signed by the group’s creator. A change from someone who isn’t a curator is ignored by everyone, whatever app wrote it.
When a service doesn’t have a song
Every member’s Trackhop looks each song up on their own service, the way any sync does. A song that your service can’t find is never removed for the others: it waits in your sync’s review, where you can pick a match by hand or leave it out of your copy.
When two people change the same song
The most recent change wins. If one curator takes a song out and another adds it back later, it stays. A song taken out stays out: an old copy of the group’s files (a sync app’s conflict copy, say) doesn’t bring it back.
Step by step
Creating the group
- Tools → Shared playlists → Create a group, or ⋮ → Share with a group on a sync’s card.
- Pick your service and your playlist (the songs it holds become the group’s), give the group a name and say how the others will see you.
- Choose how the group meets:
- Shared folder: pick the folder your group shares, as your phone sees it (in the Drive, Nextcloud or Dropbox app’s place in the picker, or the Syncthing folder on the phone).
- Encrypted ntfy channel: leave the server as it is (ntfy.sh), or put the address of your
own ntfy server. If it needs sign-in, tick This server needs sign-in and enter your access
token (
tk_…), or your user name and password there. - My Trackhop server: offered when Coordinate with my server has your server’s address and API token. The token stays on your phone; only the group’s key goes in the invite.
- On the group’s page, send the invite: the others scan the QR code with their phone’s camera, or you send them the link. For an encrypted channel, the page reminds you that the invite is the key to the group (for your Trackhop server too).
Joining
- Open the invite link on the phone (or send it to Trackhop with Share), or paste it in Tools → Shared playlists → Join with a link.
- Check the group code under the link (20 characters in four groups, like
Q9W1D-FWF07-7YMGA-183F5): it must be the same as the one on the group’s page of whoever invited you (ask them, or look at their screen), group by group. A link changed on its way would show another code. The invite page on trackhop.org shows it too. - Pick your service: Trackhop makes a new playlist there, named after the group.
- For a group on a shared folder, choose the shared folder, the same one the group uses. For an encrypted channel or a Trackhop server there is nothing to choose: the invite says where the group is.
- The playlist fills up with the group’s songs on the first sync. You join as someone who follows; the creator can make you a curator from the group’s page.
The group’s page
- Sync now: sends your changes and brings in everyone else’s. The group’s syncs also run on their own, like any other sync; their cards wear a group mark.
- Invite: the QR code and the link, to add someone else.
- Members: who is in the group, on which service, and their role. The creator changes roles here.
- Who changed what: the group’s log, newest first.
- Change folder, if the shared folder moved (for an encrypted channel or a Trackhop server, the server it uses), and Leave group: you stop receiving changes, your playlist stays as it is on your service, and the songs you added stay with the group.
Good to know
- On a shared folder, everyone in the group needs access to the folder: inviting someone to the group means sharing the folder with them too, in the app the folder belongs to.
- Each member has one file in the folder, written by their Trackhop. Leave the files alone; a copy a sync app makes on a conflict is fine, Trackhop reads it too.
- An ntfy server keeps messages only for some hours. So each member’s Trackhop sends the whole group again from time to time, followers’ too: someone whose phone was off for days catches up completely as soon as any other member’s Trackhop syncs.
- ntfy.sh limits how much each person can send in a day. That is plenty for a group playlist of ordinary size; for a very large one, use your own ntfy server or a shared folder.
- An ntfy server that needs sign-in: each member enters their own access token or user name and password, when joining or later on the group’s page (Sign-in to the ntfy server). They stay on that phone and never go in the invite, which only says the server needs sign-in; give each member an account (or token) with read and write access to the group’s topic.
- A curator can move a group on ntfy to another ntfy server: Change server on the group’s page. The group is written there first, then a signed word of the move goes on the old server, and the others’ Trackhop follows it on their next sync (a word signed by someone who is not a curator is ignored). Anyone who missed it (the old server gone, or a phone off for longer than the server keeps messages) opens the group’s new invite: Trackhop sees it is the same group and only changes the server. A server that needs sign-in asks each member for their own on the group’s page.
- On your Trackhop server, the group’s creator can Replace the key from the group’s page: the current invite stops working for everyone, to shut out someone who should no longer read the group. Send the new invite to the members you want to keep; opening it in Trackhop swaps the key and they keep their place and role. The server’s owner can also delete the group’s mailbox, or turn the server’s API off, which closes every group on it (details).
- Trackhop Desktop answers only the computer it runs on: for a group, use a Docker server the members’ phones can reach.
- The group’s key stays on your phone: a configuration file leaves the group’s syncs out. On a new phone, join the group again with the invite.
- Large removals wait for a confirmation in the sync’s preview, as in any two-way sync.
- Each phone is its own member: on a second phone, join with the invite again (and, to change the group from there too, ask the creator to make it a curator).
- Only the phone that created the group can change roles. If it is lost or reset, the group goes on with the curators it has, but nobody can change them any more: to start over, create a new group.
Related: keep playlists in sync between two services of your own, and shared links to send someone a song or a playlist on their own service.