The Bible says that homosexuality is a sin... period...

So is eating a cheeseburger. [Exodus 23.19]

Seems to me, OKCupid trying to boycott a perfectly good company and product over a single person's political views, is grounds for boycotting OKCupid.

I'm not sure me boycotting OKCupid is going to make much difference vs. me not having even heard of it had they not pulled this publicity stunt.

They wouldn't happen to host their servers on BurstNET would they? Apparently they are in some sort of dispute with their landlord and suddenly decided to ship a datacenter full of racked servers from Pennsylvania to North Carolina over the last week, with the corresponding problems that comes from a poorly planned rushed move.

Do you avoid iPhones and iPads because they don't use Intel microprocessors?

Personally I avoid them because they don't use TI microprocessors, since TI was two months earlier than Intel in developing a microprocessor, and theirs was a true single chip microprocessor, while Intel's was only part of a bigger solution. There's also the microcontroller/DSP combo that went into the F14 Tomcat two years earlier, but was classified until 1997, and unknown to both Intel and TI, and then the Gilbert Hyatt invention, which despite having its patent overturned by Intel's pack of lawyers undoubtably pre-dated Intel's invention even if he failed to commercialize the design.

All this really shows is that once technology is ready for an invention, multiple people will naturally come up with the idea around the same time, so the whole concept of patents could do with a rethink to allow for this parallel discovery while at the same time protecting against blatent copying.

The fact that Japan has always claimed to work within the rules of the IWC shows that they do give a shit about the ruling on some level. If they wanted to continue blatantly commercially whaling without even the slightest pretence of giving a damn, they could have joined Norway and Iceland in giving the finger to the IWC long ago.

It also depends on the timing of the redesign. Did they redesign the part before his daughter was killed and fail to issue a recall notice, or was it done as a result of investigation into her accident?

1) We don't know what actually happened between Costco and the testing facilities and suppliers. Even though samples were tested, there could be a concern that there were problems in the food that was not tested. Costco has not handled the public relations about this incident in a sensible manner: Costco officials did not return telephone calls seeking comment.

In true Slashdot spirit, I've only read the summary, but even that was enough to tell me that Costco is doing the right thing here.

The product was tested extensively and determined to be safe. Costco initially agreed to allowing the peanut butter to be sold, but rejected it as 'not merchantable' because of leaking peanut oil.

The jars are not sealed. They might test OK now, but by the time the food banks get through the stock, who knows what organisms have made the jar their home.

If the drone breaks up on re-entry, does the record still stand? Shouldn't they be waiting until it returns to Earth before announcing a new record?

The submitter is exaggerating. The Lock option still works for the keyboard. It acts like it is always on for the mouse.

The "Lock" feature is not in the Gnome Accessibility settings, so must be a KDE specific feature. Looking at the patch that was identified as the cause of the behaviour change, it only affects mouse operation, so either another patch is involved, or the Lock feature is still working for keyboard use. The submitter's problem is with the change in behaviour for the mouse, but I'm not entirely clear why. When you use Ctrl-mouse clicks (his example for a problemetic use case), more often than not you want to select multiple items. And more often than not, the subsequent operation is a copy (Ctrl-C) or cut (Ctrl-X) event. If you really just want to Ctrl-mouse then perform a non-Ctrl operation, a simple tap of the Ctrl key toggles it out of its locked state. So the fact that mouse events now imply modifier locking even when lock is off for keyboard use (where it is less useful) seems like it could actually have been a designed feature which was broken for some time before, and only now fixed (by a change that fixed some other bugs that had nothing to do with accessibility). The submitter is upset because the behaviour of basic UI operation changed, which is understandable. But it isn't the critical issue that makes Xorg unusable for disabled users that he makes out it is. It is more like the change from menu and toolbar to a ribbon - something that users can get used to and might eventually find more efficient than the previous behaviour if they give it a chance.

Did he mention the system used to work as expected, and now is broken?

Are you sure it was working as expected before? The current behaviour seems quite convenient, and quite possibly could have been the original intention of the feature, especially since the fix that has changed the behaviour seems to be the correct fix for other problems involving distinction between mouse and keyboard events. A lot of fuss is being made about the fact that the bug reporter needs to press Ctrl a second time to cancel his previous control for a mouse operation - if that is, he is not going to immediately press a control key (Ctrl-C, Ctrl-X being the most likely operations after a multiple object mouse selection). Apparently this makes sticky keys unusable for him and will cause him to switch OS. Good riddance I say. Impatient, grandstanding users are a huge demotivator for open source developers.

Read the bug report. The accessibility feature works. The submitter (who also happens to be the bug reporter) found a fairly minor subfeature (the ability for sticky key modifiers to act as lock keys) has been broken recently. I say fairly minor, because the only key this might be critical for in certain use cases is the Shift key, where a separate Caps Lock is already available. Exaggerating the issue by claiming it makes accessibility on Xorg unusable and bitching on slashdot because its been a whole 11 weeks since he found the problem and noone has released a fixed version yet is just grandstanding.

It's also probably how any security works until it's been around for 20 years and they hire a contracting company to make them really good software that does what they want, instead of what they think they want it to do.

You really don't understand the companies that are awarded government contracts, do you? Figuring out what the customer really wants is not part of their job description, and is most likely grounds for being put on the first plane back to India. You give the customer exactly what they ask for, no more, with screeds of documentation signed and countersigned in triplicate to cover your ass. When the customer asks for a database that matches names, the names must match, in the official character set of the nation - ASCII, not any other character set, and no mention was made in the customer requirements of accounting for alternate transliterations, so don't try to bring it to the table.

The search area is almost as far south as South Georgia.

In the same way that Portland, Oregon is almost as far north as Edmonton, Canada, or Barcelona, Spain is almost as far north as Newcastle-on-Tyne, UK. Funny how lack of land skews your perception, isn't it?

In English headline writing, using 'headlinese' it's traditional to take liberties with the language that wouldn't normally be allowed.

Another reason this is done is to confuse you into taking an interest in the article's contents (so you can figure out what the headline actually means). Especially when it is a front page headline, where such confusion might involve buying a copy of the newspaper.