Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
for anyone looking into implementing this, you can basically take
auth is probably the one big open question. for a first pass, i'd recommend punting on it. just use the silo access token directly as the micropub. users could ask me for their token, or they can mint their own, per silo.
i'd also recommend punting on update, delete, media endpoint, and querying source content, at least to start.
The issue name “micropub for bridgy publish” sounded a lot like what I was looking for in https://chat.indieweb.org/dev/2018-02-26/1519669277072200 but this issue is clearly about adding Micropub support as another API to Bridgy Publish, rather than adding another Bridgy Publish target to Micropub servers (for which I’ll file a separate issue).
Perhaps consider renaming this issue to something like:
Micropub API to Bridgy Publish
and I can file an issue for: Bridgy Publish to Micropub servers
(Originally published at: http://tantek.com/2018/057/t2/issue-name-micropub-bridgy-publish)
So, thinking through this a little bit while looking through the code. The Micropub post sent would become the post that gets syndicated. You still have to determine what service it gets syndicated through. I see a couple options here, currently the URLs used are:
Micropub could either have a single endpoint:
And use a special mp- command to signify the silo or, what I think would be better is making
An endpoint that fetches the service from the url, then no special data has to be passed through the object itself.