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
New Property: Post Status #19
This is the idea of adding a new property called post-status that allows you to set a post as published or draft.
post-status=published (or no post-status set) - The post is published, or when the published date is in the future, the post is scheduled.
There are a growing number of clients and servers where this property might be considered stable:
There are a handful of things in this proposal and I don't think all of them are implemented across all servers and clients, so we probably need to get a agreement on what is being used and what is not.
post-status=published (show now)
I think post-status=deleted is only being used by Postr and duplicates existing Micropub delete functionality so I think post-status=deleted will probably be removed from this proposed extension for lack of implementation.
I think everyone on the list incorporates both post-status=published and post-status=draft. The big question is if post-status=published + published=future date should be part of this extension or a different extension regarding "future posts". So I think the main discussion below should be trying to resolve "which of the clients/servers" above actually support future posts.
I had future scheduled posts on my old site (need to reimplement them in postr) and all I did for that is send a future published date.
Together & PostrChild also both support publishing with
Also draft doesn't always mean don't show, there are plenty of people who will write public drafts, and leave them unindexed / unlisted until they are ready.
And RE me using
Although now that I have written that it would be pretty cool if a micropub client could query to find deleted posts. But probably quite a niche feature.
Micro.blog supports post-status for drafts, but nothing for future posts yet. I had planned to let a date in the future be enough of a clue, regardless of whether post-status has a value. The behavior seems implementation-specific, unless we want clients to be able to query whether they can rename buttons to say "Schedule" instead of "Publish".
@manton I agree, I don’t think “Future posts” really belong as part of this Extension, but before I came around someone had put it on the wiki as part of the same thing. So I am essentially just hoping to verify that the in fact, others feel they are different enough and that there is Software (like Micro.blog) that HAS added drafts support but has NOT added future date support. I’ll document the discussions so far in the original list and see where we end up.