Specification for --scheduled-at

[rhersel]

Can you please specify '--scheduled-at'. Even after hours of reading UTC and timestamp specs, I'm still not able to schedule a post. Here is an example:

toot post 'scheduled 21:46' --scheduled-at "2022-11-30T21:46:00"
Toot scheduled for: 2022-11-30T21:46:00.000Z

Seems like Toot accepts the scheduled post, but it is never sent. Does this option work at all, or is it a timezone issue?

Thanks, Ralf

[kseistrup]

Does this option work at all?

As a person who is using this feature very often, I can say with confidence that it works.

I always add the Z myself (as in YYYY-dd-mmTHH:MM:SSZ), not that I think it is required, and toot always responds with the milliseconds added. A couple of times I added the milliseconds myself because they were siginificant for the post, but they were ignored.

The target accounts are hosted on a Pleroma server, not Mastodon, in case it makes a difference.

[ihabunek]

If toot displays "Toot scheduled for: ..." that means that it received the reply from the server that the toot was scheduled for that time. After that it's up to the server to respect that, I have no way to influence it.

[ihabunek]

@kseistrup The latest release 0.31.0 adds --scheduled in which takes a human readable duration after which to schedule the toot.

From toot post -h:

--scheduled-in SCHEDULED_IN
    Schedule the toot to be posted after a given amount of time. Examples: "1 day", "2 hours 30 minutes", 
    "5 minutes 30 seconds" or any combination of above. Shorthand: "1d", "2h30m", "5m30s". Must be at 
    least 5 minutes.

[rhersel]

That is nice. Thank you.