This looks fantastic so far! There are two features I'd like to suggest, however:
- Recognize HTTPS urls as already being bookmarked if it was bookmarked in HTTP form
- Allow for an API call that can pull a list of all tags, the number of bundles they've been added to, and the names of those bundles, if applicable. While it's true that the API calls as drafted will allow you to get this information, it provides it in a way that requires significant manual manipulation of data on the part of the user - to illustrate:
Say that I have a Pinboard tag named "character:harry.potter". I know that tag should have been added added to the bundles "fic-by-character", "characters:c", "fandom:harry.potter", and "representation:survivors.of.abuse". I don't know for certain whether or not I've already added it to each. I can go check manually one by one, but that takes time, means that I have to keep track mentally of all the bundles it should be in and whether or not I've checked the bundle in question yet, and doesn't catch any bundles it's been mistakenly added to.
Ideally, if I used a GET call along the lines of GET /tags/bundles/, I would then get a list of all of my tags. The "character:harry.potter" tag would be followed by names of all the bundles it currently belongs to. I now know whether or not I've added the tag to all of the bundles it belongs to, and that it has only been added to the bundles it belongs to.
As drafted, I would have to:
- first: run the GET /bundles/ call to make sure I had a full and accurate list of all bundle names
- second: run the GET /bundles/name/ for bundle #1
- third: take the results and paste into excel
- fourth: use the text-to-columns feature to separate the tag names
- fifth: transpose data from column format to row format
- sixth: in a separate column, add the bundle name to all rows
- (repeat steps 2 through 6 for all bundles)
- seventh: sort and search for the tag in question and check each row it shows up in for the bundle name
- eighth: ???
- ninth: profit
in order to get the same results as before.
I understand that this is likely not a typical use case, but as you can see, such a feature would be helpful to users who tag all bookmarks very rigorously.
An additional or potentially alternate feature would be an API call that allows you to define for an individual tag, a list of bundles it belongs to - either as a replacement for all currently assigned bundles or as an addendum.