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.Dismiss alert
It looks like tweets for some notes will simply never be posted. Some of them can't be posted presumably because users revoked permissions for the app, some can't be posted because Twitter keeps replying with "too many requests" for some unknown reason.
I think if a note for which a tweet can't be posted becomes older than e.g. 7 days we should no longer try to post that tweet and drop it from the queue. Firstly with an overwhelming likelihood we will never actually manage to post it so what is the point in trying over and over again. Secondly after some time it may actually be undesirable to suddenly have old notes posted to your profile as they are no longer relevant and it will be confusing to the user.
On 2023-11-17 we merged #63. After 2023-11-25 we can remove the code which supports old events with missing data in them after confirming that the queue length has dropped to zero at least temporarily.
It looks like tweets for some notes will simply never be posted. Some of them can't be posted presumably because users revoked permissions for the app, some can't be posted because Twitter keeps replying with "too many requests" for some unknown reason.
I think if a note for which a tweet can't be posted becomes older than e.g. 7 days we should no longer try to post that tweet and drop it from the queue. Firstly with an overwhelming likelihood we will never actually manage to post it so what is the point in trying over and over again. Secondly after some time it may actually be undesirable to suddenly have old notes posted to your profile as they are no longer relevant and it will be confusing to the user.
Checklist:
The text was updated successfully, but these errors were encountered: