Hey, remember how I mentioned that there had been some issues with the commenting here? And how I suggested the utterly clunky fix of using a different browser to leave your comments?
We (i.e., our tech guru) think we know why that works and, even better, a less clunky way to achieve the desired result:
When ScienceBlogs came into the world not so long ago, the Universe may have experienced a little hiccup, wherein some bad ScienceBlog cookies may have been spewed forth.
Deleting all cookies your browser may have ingested from scienceblogs.com ought to clear up your commenting problems. From here on out? Nothing but good cookies. (Thin Mints hidden in the back of the freezer good.)
Thanks for your patience.
More like this
It is with great regret that I am writing this. Scienceblogs.com has been a big part of my life for four years now and it is hard to say good bye.
Everything that follows is my own personal thinking and may not apply to other people, including other bloggers on this platform. The new contact…
If you follow @ScienceBlogs on Twitter, you may have seen a cryptic tweet yesterday, just saying:
ScienceBlogs will soon be making a very exciting announcement - so stay tuned!
SciBlings (who by then knew what the news was going to be, but were asked to keep it under the wraps until the official…
I am back from the 4th ConvergeSouth, the do-not-miss Greensboro conference about the Web, blogging, journalism and community (and the model/inspiration for our own science blogging conferences, including the third one) . Big kudos to Sue Polinsky, Ed Cone and the cast of thousands for putting…
DrugMonkey, Nick, Afarensis, Chad and John explain it better, but in short, each SciBling needs to pick two regular readers who will, over a longish period of time in the future, tag (in delicious, with a special tag) three site-wide scienceblogs.com posts of their interest. These posts will be…
I am so grateful!
NOTHING is better than thin mints from the back of the freezer!;-)
being a professional geek, the cookie problem is most likely browser related. IE may experience problems not evidenced in Firefiox or Netscape.
Well, let's see if it helps...