I am trying out the Pinned Recordings API.

 

When I add a pin using /1/pin it shows up

• in the list of pins returned by /1/Zastai/pins
• as the sole pin returned by /1/Zastai/pins/current

Which makes perfect sense. It also shows up at the top of my feed on the website.

If I then use /1/pin/delete/nnnn to delete that pin, it stops being returned by those endpoints, and it disappears from my feed. So far, so good.

 

If I add the pin again, it shows up again.

But if I then use /1/pin/unpin, that reports success (and only success; it might be useful if that also returned the recording mbid/msid and/or the row id), but only the output of /1/Zastai/pins/current is affected. That endpoint reports null as pinned recording, but /1/Zastai/pins retains the pin and it also remains visible on my feed.

 

So if "unpin" does not mean either "delete your pin with the highest row id" (making it repeatable to delete all pins without first acquiring their row ids) or "delete the pin you added most recently" (making it usable once), then what does it mean (and why is it useful)?