Paul Haddad's latest activity
Paul Haddad
- 1y ·
-
Public·
-
tapbots.social
{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}
Paul Haddad
- 2y ·
-
Public·
-
tapbots.social
{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}
…See more
Paul Haddad
- 2y ·
-
Public·
-
tapbots.social
{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}
@Gargron @gruber just to step in here, I'm guessing the issue is that Per IP rate limit. If that could be per OAuth token it'd probably be hit a lot less often. As of now its kind of easy to hit if you are running clients on multiple devices + have a lot of push notifications (which is another issue that I owe you some details on).
…See more
@Gargron @gruber just to step in here, I'm guessing the issue is that Per IP rate limit. If that could be per OAuth token it'd probably be hit a lot less often. As of now its kind of easy to hit if you are running clients on multiple devices + have a lot of push notifications (which is another issue that I owe you some details on).
See less
@Gargron @gruber just to step in here, I'm guessing the issue is that Per IP rate limit. If that could be per OAuth token it'd probably be hit a lot less often. As of now its kind of easy to hit if you are running clients on multiple devices + have a lot of push notifications (which is another issue that I owe you some details on).
@Gargron @gruber just to step in here, I'm guessing the issue is that Per IP rate limit. If that could be per OAuth token it'd probably be hit a lot less often. As of now its kind of easy to hit if you are running clients on multiple devices + have a lot of push notifications (which is another issue that I owe you some details on).