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
Functionality related to avoiding the annoyance of hitting the rate limit and having your message swallowed by robin.
My initial idea was to simply prevent the rate limit from being hit by making the enter key inactive for the time required by rate limit (6 seconds by my current test).
This would mean you just have to press enter again, and dont have to press up to get the last message first.
The next level of this feature could be detecting that an attempt to send has failed and then automaticaly sending the message once the time has elapsed.
It occurs to me that this might help spammers if it allowed them to stagger messages to be sent every time the rate limit is up, so i'd suggest only keeping one message. - solving the problem and not creating a big new one.
The text was updated successfully, but these errors were encountered:
Functionality related to avoiding the annoyance of hitting the rate limit and having your message swallowed by robin.
My initial idea was to simply prevent the rate limit from being hit by making the enter key inactive for the time required by rate limit (6 seconds by my current test).
This would mean you just have to press enter again, and dont have to press up to get the last message first.
The next level of this feature could be detecting that an attempt to send has failed and then automaticaly sending the message once the time has elapsed.
It occurs to me that this might help spammers if it allowed them to stagger messages to be sent every time the rate limit is up, so i'd suggest only keeping one message. - solving the problem and not creating a big new one.
The text was updated successfully, but these errors were encountered: