yeetpostyeetpost

Changelog

Queue pause, tag rules, and refusals that clear themselves

One day of what shipped in yeetpost.

#175 #176 #177 #178 #179 #180 #181 #182 #183 #184 #185

You can now pause a queue, and refusals clear themselves once the account recovers.

New

  • Queue: PATCH /connections/{connectionId}/queue with { "paused": true } holds every queued post where it is until you resume.
  • Queue: Resuming moves anything that fell overdue onto the connection's next free slot, one at a time.
  • Queue: A backlog never bursts out at once when you resume.
  • Queue: You can copy a connection's queue slots to other accounts in one action, instead of re-entering the same weekly schedule by hand.
  • Console: New accounts get a welcome message in their own language.

Improvements

  • API: Tags have a real charset: 1 to 40 lowercase letters, digits, dashes, underscores, colons, dots and slashes.
  • API: A tag you send is lowercased and trimmed before it is checked, so cms:Launch and cms:launch are the same tag.
  • API: Any other tag is 400 invalid_request.
  • API: The queue endpoint is strict: an unknown field in the body is 400 invalid_request instead of being silently ignored.
  • Console: A reconnect_required refusal clears from the account's warnings once the account reconnects.
  • Console: A platform_unavailable refusal clears from the account's warnings once the platform recovers.
  • Console: A refusal about a dead login (reconnect_required), an outage (platform_unavailable) or an unconfirmed send (send_interrupted) clears once the account reconnects or the platform recovers.
  • Console: A warning names the account it is about.

All changes