You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
I just noticed on 0.8.1 that when I schedule posts with dates in the future that they become available via federation immediately.
Steps to reproduce (if necessary)
Steps to reproduce the behavior:
Create a new draft post and give it a created date in the future
Move post from drafts to a public blog
Note that viewing the blog while logged in shows it as being Scheduled
Note that viewing the blog while logged out doesn't show the post
Using Pleroma/Mastodon lookup the blogs federated address
Notice the scheduled post appears in the post listing from Pleroma/Mastodon with its created date showing correctly
Expected behavior
I would expect that a post with status scheduled would not be published via federation until after its created date. If it's not visible from the blogs url when logged out it shouldn't be visible via federation.
Thanks for the report, I was able to replicate this as well. Looking into the cause now -- probably some missing logic.
Beyond just not publishing to the fediverse in this case, to get the full scheduling functionality, we'll also need to add some kind of mechanism that regularly checks for scheduled posts and federates them out. That'll be part of a larger undertaking we're tracking here: https://writefreely.org/tasks/567
Describe the bug
I just noticed on 0.8.1 that when I schedule posts with dates in the future that they become available via federation immediately.
Steps to reproduce (if necessary)
Steps to reproduce the behavior:
created
date in the futureExpected behavior
I would expect that a post with status scheduled would not be published via federation until after its
created
date. If it's not visible from the blogs url when logged out it shouldn't be visible via federation.Application configuration
Version or last commit: 0.8.1
The text was updated successfully, but these errors were encountered: