That explains it.
I stopped using my phone during the holiday break, and after that, nothing
worked.
I typically send the mentions.json with the count, since_id and max_id
parameters, but over the holidays that accumulated and started returning
errors. I heard about this problem first from a
This error usually occurs when it takes longer than a certain amount of
allotted time to serve the request.
While I'd prefer it if we could serve 200 tweets at a time on a mentions
timeline consistently without throwing a 502 (the time will indeed come),
you are likely to get better, more consiste
