ReadWriteWeb is now ReadWrite
readwrite.com
readwrite.com
I have a feeling their are some loose ends in their code where a user visits Page A then navigates to Page B and posts a comment there, but Disqus wasn't properly updated and the comment therefore gets filed under Page A.
It't not really a single-page-app, we just load the next article via ajax. First page loads normally. I prototyped that out but quickly realized it was totally overkill for a publication like this.
This particular issue is actually related to migrating comments to the new domain & urls. We actually have to provide Disqus with legacy urls for old articles. A few got mixed up. The reloading is actually working just fine.
Did they forget the fervor over the Gawker redesign, or did we decide it wasn't that bad and nobody sent me the memo?
On article pages, the left-side article list is actually pretty similar to something like a "See Also" box that would just show a few articles. Add a few extras and make it infinitely scrollable, and that's what we've got here. The main benefit is to not have to do a full page-load when skimming a series of articles. You also get the google reader-like J/K key navigation. Otherwise you'll be clicking the Back button and going back and forth.
Having the right sidebar scroll separately helps with ad exposure and keeps it from showing just whitespace. Some people like it.
Too bad, ReadWriteWeb used to post useful, informative (I.e. not link-bait) articles. Already on the home page I can see content-free link bait like "How many screens does one man need?" (name-checking Apple) and "As Facebook prepares to release 3Q earnings, reasons for cautious optimism."
Looks like the ads aren't showing up for you. I see the same thing with Flashblock on. We're also still working on properly targeting ads.