G'bye to EDI's journal. To be honest, our journals are getting pretty sad. They're dang-near impossible to read because of all of the 500 errors.
Here's a fix for the developer journals that could be implemented quickly. . .
1. Give all of the journal owners a way to export their journal content in an XML format that can be imported by blog software (i.e. blogger)
2. Give all gdnet+ members a field in the control panel to put a link to their own RSS feeds, be it from blogger or from a feed on their personal site.
3. Convert the Journals page to a blog aggregator like fullasagoog.com
There. All gdnet+ members could easily move their content to a more reliable back-end (blogger, movable type, etc). They then link 'em back to gamedev. And gamedev displays the journals in a better format.
That also gives people with existing journals a way to list 'em on gamedev, so they'll be more likely to get gdnet+ subscriptions just for the extra exposure.