New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mp-destination command should use destination
in the config
#3
Comments
@manton is Micro.blog or any client doing anything with this currently? I see that micro.blog returns this info already. I think this would also solve my next challenge for myself while building out my reader. |
@aaronpk Micro.blog returns the destinations (I just fixed this to remove the |
Just an update since it has been a couple of years: Micro.blog supports this in all its apps, including the new version of Sunlit and on the server. Every Micro.blog account can have a test blog, and many accounts have extra blogs for a podcast, so it's pretty common to have a response like this from
|
Koype supports the returning of a destination field but it's only the URL. Adapting it to match syndication targets is a good idea and I'll report back when I finish that. (Originally published at: https://jacky.wtf/2022/4/B7/B7PqiX4v8kM8QEWr_VlxLZfO) |
If the Micropub server supports writing to more than one website, the server can return a list of destinations the client can write to when creating a new post.
To match the use of the
syndicate-to
property, the server should return the list of destinations asdestination
, since the command the client would use ismp-destination
.https://www.w3.org/TR/micropub/#syndication-targets
An example query response:
Then in the Micropub request, the client would use the property
mp-destination
to indicate which to post to.The text was updated successfully, but these errors were encountered: