Jonathan LaCour

I've made the suggested change. If it works well in the iOS app, I'll eventually make the edits in the macOS app to trigger an automated configuration. Great suggestion :)

Add the ability to submit a list of categories when submitting a link to Indiepaper via the API. The categories will be added as `category` properties in the MF2 JSON `category` property. This will drive enhancements to the macOS app, bookmarklet, and iOS Workflow/Shortcut.

Great suggestion. I am debating either including mf2py as a dependency, or just using https://python.microformats.io as a web service like I do with Mercury, so I don't have to worry about keeping it up to date.

I will likely want to take the output from mf2py and strip out everything but the basics. Any directional feedback is, of course, welcome!

This looks awesome! I also think that the blue in the lighter version would benefit from some toning down, but other than that it looks fantastic. I can't wait to try it on iOS and macOS!

It would also be nice to add IndieAuth to the Indiepaper website, which could then generate bookmarklets and macOS configuration links automatically based upon the IndieAuth exchange.

For the use case of Aperture, the user would log into www.indiepaper.io with https://aperture.p3k.io, and then would select a channel to publish to during the auth flow.

At present, Indiepaper for macOS requires that the user manually configure their target micropub endpoint and a bearer token. This is nice and explicit, but it isn't a particularly good user experience. It would be better if configuration was automated.

Currently, I am thinking that I should add auto-configuration via a URL handler for the macOS app. Something like this:

`indiepaper:configure?micropubTargetURL=https://aperture.p3k.io/micropub&bearerToken=ASDF`

Then, when clicked, the link would launch Indiepaper for macOS, store the configuration, and let the user know that they're all set.

The simplest option would just be to let people manually configure Indiepaper by having them enter their Bearer token and Micropub Endpoint from Aperture.

I think @aaronpk is considering making it possible to IndieAuth directly with a Microsub channel in Aperture, which would provide a better experience eventually. In the meantime a manual configuration option would still be useful.

This is a test issue. Hopefully it works!

I'm not sure if this is possible, but it'd be nice if the plugin could tell Bridgy to immediately scan a just-published issue or comment to force a publish.

After we do this manually, it we would be good to brainstorm how we could potentially make the configuration discoverable from the user's website or microsub server, or both.