jonrosebaugh

No, that’s not really what I want.
I want to have wp-rss2.php included as part of a theme. So the small changes I make to it will be enabled when that theme is enabled, and disabled when the theme is disabled.

That is a point… It’s just a stock debian apache install, so probably not.

Will do. As an aside, is there any sort of caching, or problem with headers, that Apache is doing that could be causing this? That’s what the guys on IRC mentioned.

I will note that the comments feed has now seemed to have caught up to date… But there was a period of at least four hours when it didn’t show that comment.

https://blog.inklesspen.com/wp-commentsrss2.php

https://blog.inklesspen.com/?p=76 has a comment, but it doesn’t show up in the comment feed. the latest one that shows up there is for https://blog.inklesspen.com/?p=73

Never mind, they have mysteriously started appearing again

Adding those ampersand-number codes to the blacklist causes errors, at least in 1.2. I’ve been meaning to upgrade, but I think I’ll wait until 1.5 is released.

I set my blog to require moderation for all comments and I found out how 161.58.59.8 was slipping through the spamwords filter. Instead of using ‘phentermine’, for example, he types in ‘ph&#101;nt&#101;rm&#105;n&#101;’, which looks exactly the same in a web browser. It’s a variant of one of the common email-munging tactics. Any ideas on how to deal with this fellow’s tactic?