Rising Voices, Jeremy Clarke, write about blogs in other counties and languages.

Voices without Votes, Reuters wanted to know about foreign bloggers opinion of US Presidential Election.

Custom Themes for certain topics and languages.

Other People’s Code:

-Wordpress MU (one copy of filed that is used by all blogs on site); good for sub domains, upgrades and plugins for a lot of blogs. However, you do need some programming to make Wordpress MU bend to your will.

You need to make a decision as soon as you start with multiple blogs.

Multiple languages, need to be careful about comparability issues down the line.

Decentralizied Model with posts that ping the original source. Plugins for translation, backend translation is not that hard, but front end translation is another story.

Note: this session is interesting, but not what I expected. The blog network, in this case, is really more of a non profit foundation, not a typical, for profitable network, which is what I am interested in.

I may stay for a little bit longer, then leave.

As a note, plugins might not be a good long term solution for a large blog networks due to the upkeep, as WordPress gets upgraded.

For large Blog Networks, only allow Plugins your writers feel passionate about.

Also, look at tables being created in your database by the plugin, see what breaks and what works and try up fix what breaks.

Check your theme and make sure it’s stable in all browsers.

Getting hacked, you need to upgrade to the latest version (pretty much under 2.3 can be spammed).

Learn SVN upgrades, fast and secure.

Don’t upgrade directly to your site, keep a local copy and upgrade to it first.

LTS version(2.0x) not a good idea.

Security - back up with a local version, keep up a full backup of all plugins, themes and core. Use this to replace, compare files in case you get hacked.

Role Manager Plugin, very useful, have as few admins as possible,hackers will exploit accounts. The more accounts you have, it is much easier to get hacked, harder to fix.

If you get hacked, treat all code as malicious and check plugins. Treat all users at malacious.

To detect, look at your Apache log file and be careful to rename all admin sites.

There needs to disable PAP in certain directories.

Wow, I’m over saturated with Jeremy’s talk and I feel Sebastian and I need to put a lot more attention to blog security.