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

[Request]: Scheduling / scheduled / delayed toots (and editable queue) #142

Closed
1 of 4 tasks
nekohayo opened this issue Mar 31, 2023 · 1 comment · Fixed by #1209
Closed
1 of 4 tasks

[Request]: Scheduling / scheduled / delayed toots (and editable queue) #142

nekohayo opened this issue Mar 31, 2023 · 1 comment · Fixed by #1209
Labels
api Fedi software API related issue composer Composer related issue enhancement New feature or request priority: medium

Comments

@nekohayo
Copy link
Collaborator

Describe the request

Mostly self-explanatory ;) for many, many, many reasons, I would like to be able to draft posts and schedule them for automatic publication at a certain date and time in the future.

The Mastodon protocol has the ability to handle it (but their web UI doesn't expose the feature yet). I don't know if the protocol allows managing/editing the queue of scheduled toots, though.

Implementation Details

  • This should be an option in settings.
  • This should be only available to some fediverse backends. (Include which ones on the above field).
  • This is client-only (and shouldn't sync with the instance).
  • This follows the GNOME HIG.
@nekohayo nekohayo added the enhancement New feature or request label Mar 31, 2023
@HallaSurvivor
Copy link

I would love, in particular, to be able to queue or schedule my boosts so that I don't feel like I'm spamming my followers whenever I'm online.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Fedi software API related issue composer Composer related issue enhancement New feature or request priority: medium
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants