Some threads have been crashing for people due to an overload of embedded tweets/media.
I've been talking to the Rivals main tech guy and he's working on a solution to the problem. Basically, it's nothing that Rivals has changed, it's believed that Twitter has changed how or what their embedded tweets load, which is causing a HUGE amount of data being sent back to the servers and causing some threads to crash.
They're in the process of building a work-around. In the meantime, as a short-measure fix, they've changed the # of posts per page to lessen the load for each thread. It'll revert back to the norm once the fix is in place.
I've been talking to the Rivals main tech guy and he's working on a solution to the problem. Basically, it's nothing that Rivals has changed, it's believed that Twitter has changed how or what their embedded tweets load, which is causing a HUGE amount of data being sent back to the servers and causing some threads to crash.
They're in the process of building a work-around. In the meantime, as a short-measure fix, they've changed the # of posts per page to lessen the load for each thread. It'll revert back to the norm once the fix is in place.
