[dw-free] Markdown ninja-commit (testing)

[mark]

[commit: http://hg.dwscoalition.org/dw-free/rev/8434b75cccba]

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.

Patch by mark.

Files modified:

• bin/checkconfig.pl
• cgi-bin/LJ/CleanHTML.pm

( Diff: 2 files changed. )

[dw-free] Latest Page tag cloud not updating

[mark]

[commit: http://hg.dwscoalition.org/dw-free/rev/9b8ff189d7aa]

http://bugs.dwscoalition.org/show_bug.cgi?id=3520

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.

Patch by mark.

Files modified:

• cgi-bin/DW/LatestFeed.pm

( Diff: 1 file changed. )

[dw-free] Fix slow active entries query

[mark]

[commit: http://hg.dwscoalition.org/dw-free/rev/e1764db1ad9e]

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.

Patch by mark.

Files modified:

• cgi-bin/DW/Logic/LogItems.pm

( Diff: 1 file changed. )

[dw-free] Better query, force the index

[mark]

[commit: http://hg.dwscoalition.org/dw-free/rev/a9e2c39d8b9d]

Better query, force the index

Thanks to brainstorming with exor674, it seems that forcing
the index is better here. Then we get the desired behavior and a fast query.

Patch by mark.

Files modified:

• cgi-bin/DW/Logic/LogItems.pm

( Diff: 1 file changed. )