Looks like the 503 Errors with Firefox are really slowing down discussions.
The article mentioned that the new number range search feature in Google could be particularly dangerous. Maybe I'm a little naive... why is it so dangerous?
There have been a high number of occurances of 503's since the zero-notice updates a few weeks ago. (at the same time, all web pages started returning "no-cache" so simple brower navigation is forced to redownload every byte on every mouse click. When I logged a bug about this, it was immediately dismissed without comment.)
Well, I will not be sending in more money because they don't act like they want it. Hell, they can not even respond to emails I send them so I will give my money to someone else or perhaps I will just save it. How many shares of/. parent company will 5 USD buy?
And the previous page/next page links have mysteriously vanished, as have the META NEXT/PREV links that make Firefox's link toolbar work. This is making Slashdot significantly harder for me to read.
I've been giving serious thought as to writing a web page scraper for Slashdot so that you can browse it in a decent environment. The web front end is seriously beginning to suck.
Is there anywhere appropriate where I can send comments? There seems to be no webmaster link anywhere. The 'Bugs' link off on the l
When I logged a bug about this, it was immediately dismissed without comment.
And this is notable, why?
SlashDot programmers are the biggest bunch of NIH-weenies I've seen in quite a while. If you make any constructive suggestions via a bug report, or report a real bug, you get the standard line "while your suggestion would work, we'd rather do something vastly more complicated instead in some nebulous future".
They really don't give a hoot so long as the paychecks keep coming in and they can get away
Hmm... (Score:5, Interesting)
The article mentioned that the new number range search feature in Google could be particularly dangerous. Maybe I'm a little naive... why is it so dangerous?
Re:Hmm... (Score:4, Informative)
-
Looks like the 503 Errors with Firefox are really slowing down discussions.
They're not just in Firefox, they're affecting everyone. Slashdot's been more like SlashNOT this week so far.Re:Hmm... (Score:5, Informative)
Re:Hmm... (Score:3, Interesting)
Re:Hmm... (Score:1)
Re:Hmm... (Score:1)
Re:Hmm... (Score:1)
Re:Hmm... (Score:0)
Re:Hmm... (Score:0)
Re:Hmm... (Score:2)
I've been giving serious thought as to writing a web page scraper for Slashdot so that you can browse it in a decent environment. The web front end is seriously beginning to suck.
Is there anywhere appropriate where I can send comments? There seems to be no webmaster link anywhere. The 'Bugs' link off on the l
Re:Hmm... (Score:0)
And this is notable, why?
SlashDot programmers are the biggest bunch of NIH-weenies I've seen in quite a while. If you make any constructive suggestions via a bug report, or report a real bug, you get the standard line "while your suggestion would work, we'd rather do something vastly more complicated instead in some nebulous future".
They really don't give a hoot so long as the paychecks keep coming in and they can get away