It would be awesome – and way beyond the functionality of a mere API as presently being conceived – if DW had a settings page that allowed users to create API access keys that granted permissions to an arbitrary subset of DW functionality, so then they could hand the API access key over to a third party, to let that third party act as an agent, with less-than-full control of one's journal.
• A backup service could be allowed to read one's locked posts, but not one's grantors' locked posts, and have no write access at all.
• An automated posting service, e.g. IFTTT, could be allowed to post, but not read or comment at all.
• A design service could be allowed to change one's journal's style, without having any access to locked content, and no other write or read permissions.
no subject
It would be awesome – and way beyond the functionality of a mere API as presently being conceived – if DW had a settings page that allowed users to create API access keys that granted permissions to an arbitrary subset of DW functionality, so then they could hand the API access key over to a third party, to let that third party act as an agent, with less-than-full control of one's journal.
• A backup service could be allowed to read one's locked posts, but not one's grantors' locked posts, and have no write access at all.
• An automated posting service, e.g. IFTTT, could be allowed to post, but not read or comment at all.
• A design service could be allowed to change one's journal's style, without having any access to locked content, and no other write or read permissions.