Commenting problems?


The buggy software is better now, but some people are still completely unable to comment — and the primary complaint I’m getting is that the confirmation email needed to register never arrives. One possibility is that somehow, your domain or name or something is blocked by some systemwide filter.

If that’s your problem, send me a note using the same email address you used to register. I’ll forward those to the people in charge so they can dig through the system and discover why ScienceBlogs hates you. Then we’ll slap it silly and tell it to love you instead.

Comments

  1. qedx.com says

    OpenID signins seem to work as well, though I wish it’d use my name instead of the domain name :/

  2. Jonathan Rothwell says

    OpenID signins are dodgy at best, depending on the provider.

    Playing it safe and registering with the system seems to be the best option, even if it is clunky.

  3. Rincewind'smuse says

    Thanks for looking into it. It took 4-5 attempts, but I was able to eventually get an email back. I had to change my moniker….Good luck to the others suffering from a pharyngula free day…

  4. sjburnt says

    It tells me that my sign-in was invalid, then here I am!

    Seems to work OK for me.

    Now, where is the latest poll?

  5. Ted Powell says

    I registered with TypePad a few days ago, and it works fine. Just now, to make this comment, I clicked on where it said sign in, and the text area and the buttons came up with no further action on my part.
    Works for me!

  6. https://www.google.com/accounts/o8/id?id=AItOawlLc8Gfo6oZ8uAX3dYeOBxChVtMasvnHck says

    I run a greylisting service on my system. I found that the initial confirmation email would appear and get rejected with a “retry later” status. I never ever saw an attempt to retry sending the email.

    The result was I couldn’t confirm the email.

    When I noticed I could use my Google id I didn’t investigate further by switching off the greylisting.

  7. Bride of Shrek OM says

    Funnily enough I’m having no problems at all commenting now but for the last few months…whoa!

  8. NewEnglandBob says

    It didn’t work for me for a while but it has now for a week, since I abandoned Google Chrome and returned to FireFox.

  9. 'Tis Himself, OM says

    I wasn’t able to get the confirmation email at either .lycos or .gmx. I did get it at gmail.

  10. MikeMa says

    Typepad works but moveable type cannot send or resend an email to the comcast.net domain.

  11. JohnnieCanuck says

    So one question to ask of the people in charge is, are they compliant with RFC 5321 when they get an SMTP 4xx error from a greylisting mailserver.

  12. ElectricBarbarella says

    I sent the email however, I did tell you that I was able to log in with my LJ and Type Pad accounts.

    So if it helps fix the problem, go for it.

    ~Toni

  13. Legion says

    Doesn’t Science Blogs realize that their failure to solve the login issues simply embiggens the terrorists? It’s a perfectly cromulent problem.

    ————————————————–
    Commenting with impunity.

  14. Legion says

    So one question to ask of the people in charge is, are they compliant with RFC 5321 when they get an SMTP 4xx error from a greylisting mailserver.

    Then have them run a level 4 diagnostic of the trans-warp receiver array and execute a backup scan of the neutrino displacement grid. If all else fails, bounce a graviton particle beam off the resonating polarizing regulator. That should recharge the secondary log-in interface synapse.

    Piece of cake, but have them contact me if they have any problems.

  15. Happy Tentacles says

    I’ve had all sorts of problems with registering with websites; my security system usually swallows the comfirmatory e-mails that I’m waiting for. I’ve been fighting for over three months to get a problem with a Stick Insect website to get sorted! But somehow I’ve avoided that glitch here.So far.

  16. skeptical scientist says

    I suggest using a gmail email account to register, as they seem to receive confirmation emails more reliable than some other emails.

  17. dingdong says

    I’ve been reading Pharyngula for months.

    For some reason, this is the thread that made me sign up. That or the shock of finding out my wife is pregnant.

  18. John Harshman says

    TypePad works fine. MovableType has exactly the problem you describe (email never arrives), but I don’t care whether it gets fixed unless TypePad stops working.

  19. Sili says

    For some reason, this is the thread that made me sign up. That or the shock of finding out my wife is pregnant.

    Does your girlfriend know?

  20. iambilly says

    Holyus Crappus!! I was able to sign in. Of course, I am no longer (((Billy))) The Atheist, but at least I can comment.

    From this computer.

    For now.

  21. Janine, Mistress Of Foul Mouth Abuse, OM says

    No, iambilly.

    Sorry, for a short time Jadehawk had iamjadehawk and I did the same to her.

  22. eandh99 says

    I’ve only ever been able to sign in through my LJ account, and not always then. Otherwise nothing, and I’ve got yahoo mail.

  23. Rhubarb says

    I’m only #40. I’ll try harder. Looks like I can comment successfully, though I’ll have to check back in a while to see if it “took”.

  24. John Morales says

    Funny enough, the dungeoned-troll GWIAS seems to have no prob acquiring new IDs and regos to get its fix of opprobrium. ;)

    Go figure.

  25. Gyeong Hwa Pak, the Pikachu of Anthropology says

    Funny enough, the dungeoned-troll GWIAS seems to have no prob acquiring new IDs and regos to get its fix of opprobrium. ;)

    Go figure.

    Wow, GWIAS is more persistent than Mabus. Mabus got deleted once during registration and didn’t come back.

  26. blf says

    Not a commenting problem, but you still cannot e-mail the SciBorg Webmaster clowns at webmaster@scienceblogs.com
    despite that e-address being listed as a contact on Teh Sciborg page About ScienceBlogs. Now you get the bounce:

    Hello blf@[redacted],

    We’re writing to let you know that the group you tried to contact (webmaster) may not exist, or you may not have permission to post messages to the group. A few more details on why you weren’t able to post:

    * You might have spelled or formatted the group name incorrectly.

    * The owner of the group may have removed this group.

    * You may need to join the group before receiving permission to post.

    * This group may not be open to posting.

    If you have questions related to this or any other Google group, visit the Help Center at http://www.google.com/support/a/scienceblogs.com/bin/static.py?hl=en&page=groups.cs.

    Thanks,

    scienceblogs.com admins

    I have absolutely no idea what this nonsense is about a Google Group…

  27. MadScientist says

    When your email disappears into the void, that is simply the ethernet at work. Where do people think the name “ether net” came from? It is a place not too unlike /dev/null except that sometimes information does escape the void.

  28. ikt says

    ‘When your email disappears into the void, that is simply the ethernet at work.’

    I wish the 90% of email which constitutes spam would disappear into the void..

    Good to see the commenting system is getting looked at.

    —–>> FIX THIS AS WELL: Not a commenting problem, but you still cannot e-mail the SciBorg Webmaster clowns at webmaster@scienceblogs.com.

  29. rachel.wilmoth says

    I registered through MT, got the confirmation email, but when I tried to sign in, I got “Invalid login.” But I was able to sign in through Google.

  30. audiolight says

    Then have them run a level 4 diagnostic of the trans-warp receiver array and execute a backup scan of the neutrino displacement grid. If all else fails, bounce a graviton particle beam off the resonating polarizing regulator. That should recharge the secondary log-in interface synapse.

    Piece of cake, but have them contact me if they have any problems.

    … or, check your script code / SMTP server logs for a review of what operations are taken with all of the various reply codes that have ever been received from a remote mail server – including from the reported e-mail addresses that are “broken.”

    Computer Science rarely involves trans-warp signature pattern stabilizing. Thankfully. ;)

  31. https://www.google.com/accounts/o8/id?id=AItOawmCjarMSG5ZZR58WO-P0Vxt6VsXUB3PIB0 says

    So, does anyone know how you get the google account to show a user name rather than gobblygook? I would switch to using one of the other ways of signing in but this one has always been less of a pain in the ass.

  32. SEF says

    @ …PIBo #49:

    does anyone know how you get the google account to show a user name rather than gobblygook?

    From the posts on the other thread, it seems as though several google users have successfully tackled the display name problem.

  33. aratina cage says

    PIBo #49, Have you tried creating a Google public profile?

    While logged into Google under the Gmail address you are using to comment on Pharyngula, go to http://www.google.com and click on SettingsGoogle account settings in the upper-right corner of the page. Then click on the hyperlink for a public profile, fill out the info, and scroll to the bottom and click on the button Create a Google profile. That might do it.

  34. Rincewind'smuse says

    Legion,

    Then have them run a level 4 diagnostic of the trans-warp receiver array and execute a backup scan of the neutrino displacement grid. If all else fails, bounce a graviton particle beam off the resonating polarizing regulator. That should recharge the secondary log-in interface synapse.

    Yes, Mr. Spock, but the engines canna take much more of this!

  35. https://www.google.com/accounts/o8/id?id=AItOawmCjarMSG5ZZR58WO-P0Vxt6VsXUB3PIB0 says

    I do have a google profile. I’ve even logged out an logged back in, created a nickname, and an alternative name…

  36. bignose.pip.verisignlabs.com says

    The OpenID authentication (which doesn’t require email confirmation, since there’s no password interaction at the blog) is working.

    What’s not working is using the user’s own, specified identity: the OpenID they chose to enter.

    I suspect this is exactly the same problem the Google users are having.

    The blog software is using the transient, behind-the-scenes illegible URL that should be discarded after logging in. Instead, it should use the identity they presented to the blog (the “claimed identity”, for any programmers looking to fix this problem): that’s their OpenID and should be shown to the world.

    Even better would be to use the existing registration extension so the user could *choose* a nickname, but first things first: the login process should stop being broken before we think about adding new stuff.

  37. Jeanette says

    I’ve had a devil of a time signing in. Half the fun of this blog is being able to comment, even if only once in a while.

  38. hockeybobs says

    Testing the Google sign in option – and it looks like we’re in! (I *just* created my public profile, so that’s probably the ticket to getting rid of the garbled login ID crap.)