-
Notifications
You must be signed in to change notification settings - Fork 1
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
Additional syndicate-to property #23
Comments
Ready in Drupal IndieWeb and Indigenous |
I would find setting defaults for syndication very useful, but I'd like this to be more granular based on the I think this may be a candidate for adding an optional item to the query for supported properties (#8) instead:
|
Oh, I desperately need this! I won’t have time to immediately work on this but I do plan to support this on the server side. (Originally published at: https://v2.jacky.wtf/post/de738b9b-7442-4a28-ab05-676270e020b7) |
Going to track progress on my implementation of this at https://git.jacky.wtf/indieweb/koype/issues/213 (Originally published at: https://v2.jacky.wtf/post/6ba67a27-b616-44b4-9636-0d7334b850ae) |
Proposal: Add a new property to the syndicate-to query to tell the server what kind of post the client is trying to make.
The server could then return a different list of syndication targets depending on the post type. Additionally: Add a new property to the response for servers to tell the client which options to check by default. {
"syndicate-to": [
{
"uid": "https://archive.org/",
"name": "archive.org",
"checked": true
},
....
} |
Micropublish now supports this |
https://www.w3.org/TR/micropub/#h-syndication-targets
Proposing an optional property, checked, that if present and true would tell a client to set the target to checked by default...as opposed to the current behavior common in clients of making the user select each syndication target.
If the endpoint does not want to give the user any choice, it would not provide a target at all and just posse each time.
The text was updated successfully, but these errors were encountered: