This is a good starting point--a very data-driven API. Thanks for doing this! I also get some days like that, and should figure out if this could count.
A second level down might also be nice: given (auth, user, tag), get a list of entries given (auth, user, accesslist), get a list of entries. given (auth, user, entry), get previous or next entries. Auth here is the identity to query using, since the results of those matter based on who you are.
Some more queries I find myself doing manually that might be nice to have a simpler way to do:
1. Translating between date and entries, in both directions. (It's one-to-many, of course.) Even cooler would be "get entries between START and END", but that's fancier. 2. Something regarding polls. Probably the ability to map entry to poll ID, then querying by poll ID to get poll results/status. (I put a poll in almost every entry, but I am...not typical.)
no subject
A second level down might also be nice:
given (auth, user, tag), get a list of entries
given (auth, user, accesslist), get a list of entries.
given (auth, user, entry), get previous or next entries.
Auth here is the identity to query using, since the results of those matter based on who you are.
Some more queries I find myself doing manually that might be nice to have a simpler way to do:
1. Translating between date and entries, in both directions. (It's one-to-many, of course.) Even cooler would be "get entries between START and END", but that's fancier.
2. Something regarding polls. Probably the ability to map entry to poll ID, then querying by poll ID to get poll results/status. (I put a poll in almost every entry, but I am...not typical.)