After Firefox dropped support for the blink style, I implemented a workaround in JavaScript. It's not as elegant as I'd like, but it's functional.

You're assuming the desired target is within range...

Thanks for your response. Keep them coming.

What I think would help the most is to display a small box at the top of every page on the beta site that lists all the major problems you've identified that you know have to be fixed before the new site can become the default. Ideally, each one should be a link to a page that explains the problem in more detail. This will help us to understand that you really are listening, and trust you not to plow ahead with something that's obviously currently broken.

The problem isn't that the beta site is broken. The problem is that we don't trust you to fix it, because we don't understand why you broke it in the first place and we're afraid you don't think it's broken. Please, put our fears to rest! :-)

Well put!

What I said in another comment: Nobody comes here to read your content. They come here to read ours.

Did you notice the little gear menu, to the right of the links for funny/insightful/etc.?

What does seem to be missing is collapsed comments - comments that are scored below a certain threshold being displayed as a single line that I can click on to expand them.

Not quite. That's what we THINK we want. What we REALLY want is slightly different.

We don't want you to say you'll slow down, because we hear that as "continue to do exactly the same boneheaded thing you were going to do, just delayed for awhile."

But we don't really want you to stop and go backwards. What we want is for you to make sure that you're not leaving anything important behind when you do move forward. Lots of us have our own little irritations with things we consider to be "broken" in the beta site - my big one is that I couldn't see a way to set up abbreviated comments (where I see only a single line for comments that are scored below my threshold, but I can click on it if I decide I want to expand any specific comment). I have that now, but on the beta site, it appears to be missing. Others have complained about other functionality that seems to be missing. We need to be assured that you're not going to plow ahead without these features.

That doesn't mean you have to go backwards, because Lord knows the old site has some issues that need fixing. But remember that if you alienate your user base in an attempt to attract more users, you'll be left with nothing, because the existing user base is the only thing that makes Slashdot worth a damn. Nobody comes here to read your content, they come here to read ours.

...EVEN IF THAT'S NOT HOW YOU MEANT IT. Understand that we'll translate it this way anyway, so be careful what you say.

Alternately, if you know the comment system isn't finished but want to get people testing everything else so you can fix those bugs first, great! Understand that the comments are what makes Slashdot worth anything, and therefore the comment system is the metric by which the average Slashdotter will judge everything else that you do. So, put a big obnoxious warning at the top of every page on the beta site saying "Hey guys, we know comments are broken, we're still working on that part! Please give us feedback on everything else for now. Specifically, we know we have the following problems which we plan to fix before rolling this out to everyone..."

Or speeds it up, depending on how it's used. Sometimes a nice clean bit of JavaScript can eliminate the need for another page load, and a little AJAX query can quickly fill something in without the need to load a completely new copy of the entire page again. Of course JavaScript can also be used to do stupid annoying things, and on a site like this, they should definitely make sure the site degrades very well.

Oh hush, let him make his point. :-P

I'm not sure if you never listen to NPR, or never watch MSNBC...

The "old guard" editors didn't know how to do their jobs either. Note my user ID; I remember. I come here for the comments, not the articles.

As is so often the case, those of us posting here on Slashdot have no idea. Of course someone does, but we don't.

If you ask a transit rider how to get there by car, they may not give you the best directions. Try asking them how to get there by bus. If they don't know the answer offhand, they certainly know how to quickly find out.

Thanks, I got these titles from thomas.loc.gov and it didn't occur to me that they wouldn't be the official titles.