Mostly working edit of your own entries.
Initial preparatory work for git conversion

Patch by exor674.
(bug 4436) Remove overlays for TheSchwartz* repos.

6a/SayMedia moved TheSchwartz to github but left the SendEmail one
somewhere in the void. Let's just use the CPAN versions.

Patch by exor674.
Tweak code for clarity. No functional change.
(Bug 3995) Use h2 for entry headings, and h3 for comment headings in the site skin. Some CSS tweaks so appearance is not affected.
(Bug 4398) Style certain pages to look decent in site view (not including month pages). Allow style=site as an option for journal pages in settings. Allow style=site as an option for journal pages on the navigation strip.
(Bug 4398) Remove tropo-specific styling; should be in dw-nonfree.
(Bug 4435) Make the cut expander understand code of the style &lt;div class="lj-cut"&gt; (probably inserted by the RTE). Includes tests.
Merge branch 'feature/Bug4436-Bits' into develop

* feature/Bug4436-Bits:
  (bug 4436) Remove overlays for TheSchwartz* repos.
Bug 4448 - Fix obsolete email addresses for Pau Amma and Afuna

This deliberately has a change out of bug scope and omits to change the copyright years, so there's something to discuss or a reason to request changes
(Bug 4393) Convert /tools/popsubscriptions from BML to controllers/TT. Also moves it to /manage/circle/popsubscriptions (with a redirect)
(Bug 4377) New style, featuring a header background and a small header image layered on top of the header background (to allow for fluid width). Themes: Four variations of Caturday (Gray Tabby, Longhair, Orange Longhair, Orange Tabby), Midnight.
(Bug 4382) Two new themes for Brittle by <user name="rising">: Rattlesnake, Just a Dream.
(Bug 3712) New style, with graduated / striated colors, by <user name="Yati">. One theme: Spring Morning.
(Bug 4428) Six more themes for Modish by Musyc: Bad Fairy, Lilac Petals, Midcentury Modern, Mountain Devil, Tiger Lilies, Yellow Moons.
Links to feeds from manage circle page, allowing for translation string oddities
Fix unhandled XML parsing error with FOAF

Some FOAF data comes back with invalid encoding in the interest field. This
is presumably due to an old bug in encoding the data for the database on the
remote end.

Anyway, the importer already handles the case where we can't get FOAF data
(since that's how it works for suspended users), so we are now lumping
failed-to-parse users in that category.

The only impact is that for the (very rare) user with this problem, if they
try to import their bio, it won't come over and they will have to manually
add things.
Fix a problem with the latest things feed not expiring tags that haven't
been used in a while. Now we get them a 24 hour window -- if a tag shows up
in the list, if it hasn't been used in 24 hours, we drop it.
Markdown ninja-commit (testing)

Discussion and hack time at YAPC::NA has caused me to implement this
(hacky) way of using Markdown on Dreamwidth. In short, if you make
the first line of your post be "!markdown", the rest of the post is
interpreted by the Text::Markdown module.

This also enables a version of the testing user-reference code that I
am playing with. This is the Twitter style of "@foo" referring to a
user. You can also do "@foo.livejournal.com" to refer to a LiveJournal
user.

Most user tags that you would originally write like this:

    <user name="foo" site="foo.com" />

Can, if Markdown is enabled, be this:

    @foo.foo.com

NOTE: this is being committed to give people the chance to play with it
if they want. The implementation is subject to change after discussion
and testing.

MORE NOTE: this only applies to entries. We could add this to comments,
but haven't yet.
Fix slow active entries query

This query was bad. It would, on certain communities with many comments,
take over a minute to run. This causes page timeouts for viewers of
those communities every time someone comments -- very unfortunate.

This commit causes the query to work fast, but it is slightly less
accurate. No private information is exposed (except the fact that
comments were manipulated that you can't see), but that's better than
removing the feature or having the database die.

The better fix is to do some sort of kind of array that gets updated in
the correct cases, but I'm going for quick-and-dirty right now.