https://buy-zithromax.online buy kamagra usa https://antibiotics.top buy stromectol online https://deutschland-doxycycline.com https://ivermectin-apotheke.com kaufen cialis https://2-pharmaceuticals.com buy antibiotics online Online Pharmacy vermectin apotheke buy stromectol europe buy zithromax online https://kaufen-cialis.com levitra usa https://stromectol-apotheke.com buy doxycycline online https://buy-ivermectin.online https://stromectol-europe.com stromectol apotheke https://buyamoxil24x7.online deutschland doxycycline https://buy-stromectol.online https://doxycycline365.online https://levitra-usa.com buy ivermectin online buy amoxil online https://buykamagrausa.net

Your registration, please?

Okay, I’ve turned on TypeKey registration on comments here, and on the Blog of Heroes. If it’s broken, it will have to wait on fixing until after I’ve gotten back…

Okay, I’ve turned on TypeKey registration on comments here, and on the Blog of Heroes. If it’s broken, it will have to wait on fixing until after I’ve gotten back from swim class with Katherine.

43 view(s)  

14 thoughts on “Your registration, please?”

  1. Well, it appears to be working. My site’s been running slowly (for me) for a while.

    I need to do some clean-up of the “Speak!” warning code. That’s a project for today.

  2. Okay, now this is driving me batty. I’m getting a steady stream of innocuously-URLed trackbacks. One every fifteen minutes or so. Urg.

    I’m also sifting through the comment forms to discover why the MT-Notify stuff isn’t showing up, and generally cleaning up the preface text.

  3. Okay, I think I have this looking the way I want. The comment buttons are back, MT-Notify is back, and all *looks* good.

    Problem is, as I told Margie, the comment form code has been written and rewritten and modified by me over the course of the last three years of my being on MT. I grafted in the TypeKey stuff when that became available (thank God), but the block executed when TypeKey is *required* had never been actually tested, silly me.

    Anyway, it’s working here, and it seems to be working on BoH, so I’m considering it done for the nonce. I still need to implement this on Margie’s blog, but that’s about it.

  4. Okay, I think I have this looking the way I want. The comment buttons are back, MT-Notify is back, and all *looks* good.

    Problem is, as I told Margie, the comment form code has been written and rewritten and modified by me over the course of the last three years of my being on MT. I grafted in the TypeKey stuff when that became available (thank God), but the block executed when TypeKey is *required* had never been actually tested, silly me.

    Anyway, it’s working here, and it seems to be working on BoH, so I’m considering it done for the nonce. I still need to implement this on Margie’s blog, but that’s about it.

  5. I’ve debated taking SEB to a registration required setup and if I were still running MT I probably would have by now. Comment spam is a minimal problem at this point though so I’ve had no big need to change them. Now if we could just figure out a decent way to deal with trackback spam I’d be all set.

  6. The actual amount of comment spam getting through here has been minimal as well, though still irksome (not as irksome as having to clean up all the moderated comments that never got seen).

    More of a problem is that the host resources to combat it (because of the Perl nature of MT and the number of processes that get spawned with each comment submitted) has been causing difficulties, and just because stuff wasn’t bubbling to the surface didn’t mean there wasn’t a lot of it underneath.

    Trackback spam is still a problem, yes. MT has MT-Moderate (which can throw Trackbacks into moderation, I believe), and the new SpamLookup tooks may help there as well (as an extension of MT-DSBL), but it’s still a PitA.

Leave a Reply

Your email address will not be published. Required fields are marked *