This is a #nos-dev-diary from a mostly-backend-developer.
We posted about our Twitter crossposting service a short while ago but there were some problems with the Twitter API and messages got stuck in the queue resulting in tweets not being posted. What I speculate has happened is that some people exceeded their personal API limits and their tweets got stuck in the queue blocking other tweets from being posted. I can't confirm this since Twitter reports that we have not exceeded the API limit despite responding with “Too many requests”. I released an update which resulted in some tweets being sent by implementing proper backoffs and handling messages out of order.
Given that fact that I suspect people wouldn't be happy with a sudden wave of tweets being posted I haven't copied the messages that were stuck to the new queue for now so only new notes will generate tweets.
The service is available here: https://tweeter.nos.social
If someone has seen weird Twitter API behaviour similar to the one I described where all calls fail with “too many requests” but clearly no requests succeeded in the windows specified in the docs please let me know.
Previous:
#twitter #nostr