Consider making questions (and other live feed data) cyclical. Much like the search feature, consider making the elements of a question list cyclical to prevent the DOM from getting overloaded and causing severe lag when response feeds get large. One idea would be to display the initial question and truncate intermediate replies (or only show 'Good Answer' replies after response feeds reach a certain threshold) This will help in preventing OS feeds from locking up the frontend when inundated with ajax requests trying to update large feeds.
This, of course, could be expanded at the user's request as seen in the OS search result panels.
or maybe have some way of "scrolling" throw a large list of responses so you only see a "window" of say, 20, responses at any given time? that way the client doesn't need to hold the entire feed in local memory.
Join our real-time social learning platform and learn together with your friends!