> This error check has always existed in the search code, but most > people never see it. This is a sanity check on the since_id parameter > to prevent people using ones in the future. The problem yesterday was > specifically that several back-ends fell behind. If you hit an up-to- > date back-end and collected a max_id, then hit an out-of-date back-end > it would complain that you were using a since_id in the future from > its perspective. We've corrected most of the back-ends but we have a > few more upgrades this evening to fix the last few. Sorry for the > delayed reply but I need to focus on fixing and not email.
Got it. Is there a way, maybe, to try to detect this condition specifically on the backend and maybe return a more generic "Search is running behind"? It was really throwing users for a loop (and worse blaming the app ;-). -- ------------------------------------ personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [email protected] -- "I'd love to go out with you, but I'm rethreading my toothbrush bristles." -
