Skip to content
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

Stable Property: Post Status #19

Closed
EdwardHinkle opened this issue Apr 4, 2019 · 11 comments
Closed

Stable Property: Post Status #19

EdwardHinkle opened this issue Apr 4, 2019 · 11 comments
Labels

Comments

@EdwardHinkle
Copy link

@EdwardHinkle EdwardHinkle commented Apr 4, 2019

Wiki Page

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.
post-status=draft - The post is a draft, and should not be shown in lists. (Of course it's up to the implementation whether it wants to use a capability URL for draft posts or actually restrict it to logged-in users.)

There are a growing number of clients and servers where this property might be considered stable:

Clients:

  • Quill
  • Indigenous for Android (supports Draft, Published and Future Dates)
  • Micro.blog (supports Draft and Published)

Servers

  • p3k
  • Micropub for WordPress (supports Draft, Published and Future Dates)
  • IndieWeb for Drupal (supports Draft, Published and Future Dates)
  • Postr (supports Draft and Published) [also uses post-status=deleted]
  • Micro.blog (supports Draft and Published)
  • abode (supports Draft and Published)

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)
post-status=draft (don't show)
post-status=published + published=future date (show in the future)
post-status=deleted (don't show)

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.

@EdwardHinkle
Copy link
Author

@EdwardHinkle EdwardHinkle commented Apr 4, 2019

@manton @dshanske @aaronpk @swentel

Of your projects listed above as implementations of the Post Status Micropub property, which ones actually support "Future Dated Posts" that is sending a Micropub post with a future "published" date and have it scheduled to not appear until that time has arrived.

@grantcodes
Copy link

@grantcodes grantcodes commented Apr 4, 2019

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 post-status=draft

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 post-status=deleted it effectively becomes a trash of sorts, so the posts still exist and can be undeleted. I agree it probably shouldn't be in the spec, just a note on my handling on deleting and undeleting posts.

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.

@dshanske
Copy link
Member

@dshanske dshanske commented Apr 4, 2019

Micropub for WordPress does because WordPress does

@swentel
Copy link

@swentel swentel commented Apr 4, 2019

Drupal supports published / draft + future dates. Indigenous allows sending published/draft and future dates (also in draft state) - and also has local drafts.

@manton
Copy link

@manton manton commented May 14, 2019

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".

@EdwardHinkle
Copy link
Author

@EdwardHinkle EdwardHinkle commented May 14, 2019

@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.

@EdwardHinkle
Copy link
Author

@EdwardHinkle EdwardHinkle commented May 14, 2019

@aaronpk I think you’re the last implementer of this Extension that hasn’t provided their thoughts. Any thoughts? 🙂

@manton
Copy link

@manton manton commented May 6, 2020

To follow up on this… I realized recently that Micro.blog "accidentally" supports future posts, sort of. If you create a post with a date in the future, it will be published when that date hits, after the next time you create another post or change anything else on your blog.

I plan to tweak this to be a formal "scheduled posts" feature without any other Micropub changes except setting a published date in the future.

@dshanske dshanske changed the title New Property: Post Status Stable Property: Post Status Jun 27, 2020
barryf added a commit to barryf/micropublish that referenced this issue Jul 17, 2020
This overlaps with `deleted` property and seems
likely to be removed looking at the discussion on the issue:
indieweb/micropub-extensions#19
@dshanske
Copy link
Member

@dshanske dshanske commented Aug 16, 2020

Closing this issue as stable. Any discussion of additional post status properties can occur in a new issue linked to this one.

@jamietanna
Copy link

@jamietanna jamietanna commented Feb 8, 2021

Do we have an example of what this looks like for:

  • JSON Create
  • JSON Update

Or is this only expected to be for forms?

@jamietanna
Copy link

@jamietanna jamietanna commented Feb 8, 2021

To answer my own question, yes, it is treated as a property post-status:

{
  "action": "update",
  "replace": {
    "content": [
      "..."
    ],
    "name": [
      "Reply to https://twitter.com/joshghent/status/1358869174307725316"
    ],
    "post-status": [
      "draft"
    ]
  },
  "url": "https://www.jvt.me/mf2/2021/02/auyd3/"
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants