Good news, bad news. It's most likely possible that we can change it so the embedding runs prior to the "jump to first unread post" event. We'd have to locate where each runs. The embedding is most likely buried in an XML file; when we wrote the code for them, we had to do it as an XML file and then import it, so I'm pretty sure that it was written to one of the board's XML file. The "jump" function - not sure about that. Best guess on that is that it's a JavaScript that's called as a function. Assuming we can locate those, most likely we could do it. That's all the good news.
The bad news is that even if we did it, it probably won't help much. The embedding simply replaces the HTML that points to the tweet with HTML that can be embedded. The problem is that once that happens, the board has to go out to that "new" URL and pull down the tweet. The big problem is bandwidth and the speed in which the contents of the tweet can be pulled. I can't think of a way to tell the "jump" function how to tell that all embedded material has completely loaded, which is what would be needed. So, even if we changed it, what would happen is that the "embed" function would run and replace the "bad" URL with the "good" URL. Then, the "jump" function would fire - but it would not have a way to know how long to delay firing so that all the content would be loaded. So, even after the "new" URL is created, the "jump" would still occur prior to all the content of the tweet was pulled and rendered.
Having said all that, I'm not the most skilled coder by any means. It's possible that DaveH or zoogs might be able to come up with an idea.
