check my amazon wishlist


CoreMedia vs. TYPO3

TIMTAB latest builds

stable:
v0.5.11 from TER
bug fix: commenting was possible although disabled for a post

unstable:
2006-04-15

what's new in unstable:
Ready for TYPO3 4.0.0. Trackback routines reorganized. Now Trackbacks will be sent only when the post is not hidden. Please test wether Trackbacks are working when writing post with tools like w.bloggar.

renner

Coding Night Wannabe an Apple? Robert Sebastian Session Robert

Archives

Categories

Buddies and others

del.icio.us links del.icio.us linkage




    Powered by Technorati



    Disclaimer

    I just brought the site back to life so that people can stop reminding me that it's down. Please note that probably most if not all content is outdated. I'll try to update stuff as soon as possible.

    best Ingo

    03
    Sep
    2007

    Fight the SPAM, part IV


    Just some days ago I created an account for our newest buzz blogger Søren Andersen on buzz.typo3.org.

    After doing that I checked how akismet is doing in blocking comment SPAM, I actually saw that it didn't do it's job as well as expected as there were some error messages that the API key for typo3.org is invalid or a lot of messages just weren't recognized as SPAM. Nervertheless it blocked most of the spam and we'll stik to it.

    So I did some SQL queries to clean up the mess which purged some 60k+ SPAM messages from the DB since the last clean up.

    As this is a boring task I don't wanna do any longer I decided to adopt a technique known from other blog systems. This is called "close comments after". Often spamers use comments on old posts as they have a higher rating in google and thus the links they generate with their comments also get a higher rating. So the name pretty much says it all: After a given time the comments for a post are automatically locked so that no more comments are possible.

    That should give us a rest from SPAM and more fun reading the posts on buzz. You too can grab that extension from TER as soon as it pops up overthere, which should happen with the next processing of the uploaded extensions.

    As always: Have fun!

    comments

    #1 | Micha commented on Monday, 03-09-07 16:07

    Gravatar: Micha

    Very nice idea! I will install it asap. Sometimes I´ve those "invalid key" messages too but no idea why. What are the other messages you get from the akismet errorfield?

    Maybe autoprune (delete all spamcomments older than 30 days) would be a nice idea for the next mf_akismet extension, isnt it?


    #2 | Ingo commented on Monday, 03-09-07 20:41

    Gravatar: Ingo

    that'd be nice I guess. What I noticed when deleting all that spam is that it would make sense to make these buttons to mark messages as spam not reload the whole page but issue an AJAX request... =)


    #3 | Micha commented on Monday, 03-09-07 20:50

    Gravatar: Micha

    Nice Idea! I will do the same time you implement a hook to the list module in the core ;)
    That XCLASS sucks..


    Sorry, comments are closed for this post.