Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
For the out-of-band Slashdot experience (mostly headlines), follow us on Twitter, or Facebook. ×

Comment: why? (Score 1) 402 402

OpenBSD includes mg, an Emacs work-alike in the base system, since Emacs has too many dependencies to not be a port. As the mg man page says:

mg is intended to be a small, fast, and portable editor for people who can't (or don't want to) run emacs for one reason or another, or are not familiar with the vi(1) editor. It is compatible with emacs because there shouldn't be any reason to learn more editor types than emacs or vi(1) [emphasis added].

This is a thoroughly-invented wheel. Do we need square ones at this point?

Comment: Re:Back to the future (Score 2) 142 142

Is that what that's for? Oops. Egg on my face, definitely! In my defense, while Slashdot definitely has its trolls, the signal-to-noise ration is much better here than on nearly every other site, so I've never been sufficiently irritated enough to want to plonk someone.

Comment: Back to the future (Score 1) 142 142

All I want out of a commenting system is what Usenet has had for forever: a killfile. If I know that "John Doe <jdoe@example.com>" is generally a troll, I want to just not see posts by him.

As far as I'm aware, there are no web forums or commenting systems which incorporate this functionality. I haven't done an in-depth study, though, so I'd welcome correction.

Comment: low impact (Score 1) 50 50

I'm just not convinced that an attack on traffic lights, even if successful, would have that much impact. Would there be more accidents, and potentially injuries? Absolutely. But on the scale of the country? Most folks pay attention to more than just what the light says—if another car is speeding crossways, they're going to stop, even if they themselves have a green light.

I'm willing to be convinced, but I just don't see it.

Comment: Re:We don't need a response! (Score 2) 112 112

We just give them a high intensity focused radio broadcast of "Big Bang Theory" or "The Office" and wait for them to become hooked.

Like Futurama aliens getting hooked on "Single Female Lawyer".

Great plan, except that it ends with us getting stuck with Richard Nixon's head in a robot body as president.

Comment: Re:Why? (Score 1) 157 157

The other category - typified by the Kevin J Anderson stuff - is what could, most kindly, be described at "bad fanfiction". This is the stuff that's badly written, tone-deaf and schlocky. This stuff is filled with stilted dialogue, paper thin characterisation and plot holes you could fly a Star Destroyer through. Admittedly, everything I've just said could be applied equally to Lucas's prequel movies - but you really do hope they're aiming higher than that with the new stuff.

You're right, but the biggest problem I had reading the Anderson stuff and its ilk was how blatant its marketing was. It wasn't enough to have Jedi and Sith and the whole Star Wars universe. Every time a character who also appeared in the movies has a thought it's "Oh, this is just like [thing that happened in the movies]." I finally couldn't read anymore it irritated me so much.

Comment: Not legally binding (Score 3, Informative) 33 33

It's worth noting that this is an opinion by the Mississippi Ethics Commission, and as such, while suggestive, is "advisory" and not legally binding.

The main point of soliciting an opinion from the Ethics Commission is that a "public official" who acts upon such an advisory opinion is not subject to civil or criminal liability as long as the official "follows the direction of such opinion and acts in accordance therewith unless a court of competent jurisdiction, after a full hearing, shall judicially declare that such opinion is manifestly wrong and without any substantial support." (Mississippi Code of 1972, Annotated, section 25-4-17(i)(i))

Comment: Re:No throttling - impossible dream (Score 1) 235 235

WaffleMonster, I believe you hit the nail on the head - the key is differentiate between bandwidth management and discrimination or preferential treatment. The problem will be how to clearly draw the line between them.

This doesn't seem like much of a problem to me. If your pipes are at a capacity that you need to prioritize certain traffic, you do it based on the service—video, VoIP, P2P, et cetera—regardless of source, and that's bandwidth management. If your pipes are at any capacity and you throttle a specific source of traffic, that's discrimination. Do you see any problems with that as a bright line?

"Even if you're on the right track, you'll get run over if you just sit there." -- Will Rogers

Working...