Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror

Submission Summary: 0 pending, 13 declined, 6 accepted (19 total, 31.58% accepted)

×
Idle

Submission + - Plan to test Shakespeare remains for marijuana (foxnews.com) 1

dutchwhizzman writes: A team of scientists has submitted a formal request to test the remains of William Shakespeare for drugs. Notably, for marijuana, since remains of clay pipes found in his garden have been tested positive for four-twenty. If they get permission, we may have to adjust our view on his world famous plays quite substantially.
Microsoft

Submission + - MicroSoft Office 365 goes live (microsoft.com)

dutchwhizzman writes: MicroSoft today officially announced the worldwide launch of their in-browser office collaboration suite. They have recently been communicating that they are planning on a cross browser, cross platform support for all their apps in the future. Now is the time to see if they can live up to that plan and if it's any good.

Submission + - Bittorrent and uTorrent sued for protocol (torrentfreak.com)

dutchwhizzman writes: "Bittorrent and uTorrent are sued for using techniques in their clients and the bittorrent protocol. From the article it appears that technologies are used that were submitted in a 1999 patent, that was approved in 2007. This itself is not uncommon, but reading what technologies are used, HTTP could very well be prior use, or violating at least part of the same protocol."
Firefox

Submission + - Fedora refuses to fix broken flashplayer in 14_64 (redhat.com)

dutchwhizzman writes: After over 150 entries in a bugzilla bug over Adobes' broken 64 bit flash player, there still is nobody that is fixing the problem. Even Linus Torvalds himself has given his comment that no matter who broke it, Fedora should just fix it, since the end users don't care. Fedora developers so far refuse to revert a change to glibc that triggers the bug in Adobes's software, "because the bug is in Adobes' software and Adobe knows it's in there".

In the mean time, end users are left with glitches and broken sound in their 64 bit OS experience, and only a few found the cause and remedy for this in the bug description. Right now there is even a plea to stop submitting comments to the bug, in the hope that the developer might want to revisit it and read what should have been done weeks ago. Is it really so that developers, in this time and age, can dictate what gets commented to a bug and what gets fixed in such a big community project, just because they are the ones with write access to a repository?

Slashdot Top Deals

"The four building blocks of the universe are fire, water, gravel and vinyl." -- Dave Barry

Working...