When Twitter bridge encounters a 403 (rate limit) err, drop the notice

instead of requeuing.

diff --git a/plugins/TwitterBridge/twitter.php b/plugins/TwitterBridge/twitter.php
index e133ce6f745c1a8c5e9e30ef67d367e91b6f1bbc..33dfb788bf5d3d27d11b447bbc8644cdf51660a7 100644 (file)
--- a/plugins/TwitterBridge/twitter.php
+++ b/plugins/TwitterBridge/twitter.php
@@ -269,19 +269,23 @@ function process_error($e, $flink, $notice)
 
     common_log(LOG_WARNING, $logmsg);
 
-    if ($code == 401) {
-
+    switch($code) {
+     case 401:
         // Probably a revoked or otherwise bad access token - nuke!
-
         remove_twitter_link($flink);
         return true;
-
-    } else {
+        break;
+     case 403:
+        // User has exceeder her rate limit -- toss the notice
+        return true;
+        break;
+     default:
 
         // For every other case, it's probably some flakiness so try
         // sending the notice again later (requeue).
 
         return false;
+        break;
     }
 }