From the clause, I can see no change of copyright or any other IP, but Google is granted non-exclusive rights to the post. (Non-exclusive meaning the copyright holder can still do whatever he likes with it, even sell it on).
Google is protecting their backside. If they don't ask for a non-exclusive right when you post through this service, there is a potential for a lawsuit later if they create archives or do other things with that material. If I were in their shoes, I'd ask for a non-exclusive license, too, in order to continue be able to post.
Slashdot has at least an implicit (if not explicit) non-exclusive right to your words when you post here.
When I ran an early Internet marketing mailing list from 1994 to 1996 (www.i-m.com), I foolishly didn't initially make a condition of posting, and this, in turn, led users later to threaten me with lawsuits if I produced any for-profit or for-free versions of the list outside the archive. I eventually shut down the list, as I had better things to do than hire lawyers and sort out copyright issues.
"Intel sponsored the study because a year ago Intel was full-blown behind Bluetooth. Bluetooth has since died a nasty death, and Intel has changed courses to embrace Wireless Ethernet."
This is horribly misinformed. Bluetooth hasn't died; it hasn't really shipped. It will, almost certainly. Intel didn't drop Bluetooth; it dropped HomeRF, a competing high-speed networking standard. Bluetooth's purpose is wholly different - mostly for very low-power synchronization and info exchange, like synching a Palm with a laptop, loading phone numbers into a cell phone, etc.
We'll see if Bluetooth lives up to it. But Intel is pouring lots of cash into the hole, as are several other major chipset makers and many many hundreds of manufacturers. As with cell phones that browse the Web, the design will determine it's really useful and consumers (business and home) actually want it.
But it's coming. 802.11b and Bluetooth won't be competing; they'll be complementary, because 802.11b, for the foreseeable future, takes up too much power, and won't be cheap enough ($20 vs. $5 ultimately) per chipset to integrate into the simple devices that will use it.
Actually, Airwave is one of dozens of companies, including MobileStar, WayPort, Surf and Sip, etc. All of them have networks of varying size. Most of the major airports in the US should be wired by year's end. Or, rather, unwired.
In Sweden, Telia has put WiFi in quite a few locations, and is about to expand in partnership with SAS to a number of European outlets, and a couple in the US - all SAS waiting lounges.
The deployment is underway; the real problem is roaming agreements, so you pay a single monthly fee and can access all networks. There are some problems with that, of course, because of the nature of access points and access lists. Too long to go into here.
I wrote about this at length back on Feb. 22. Here's the NY Times link (no reg required link): http://www.nytimes.com/2001/02/22/technology/22WIR E.html?pagewanted=all
HomeRF had the FCC approve a change to its implementation of FH in 2.4 GHz which boosts it to 10 Mbps in its 2.0 version, and up to 22 Mpbs in a not-yet-released 3.0 spec. The HomeRF group claims to be ready to ship by summer a variety of devices.
The 5 GHz range will be dominated by 802.11a. I don't know whether its FH or DS, but FH doesn't make sense given the DS involvement in 802.11b. "a" should operate above 50 Mbps according to manufacturers. Expect delivery of equipment later this year or early next year.
They will make access points with both 2.4 GHz ("b") and 5 GHz ("a") chipsets and antennas to handle transition from b to a, especially in enterprises.
Here's the 802.11 (wireless LAN) IEEE workgroups site:
http://www.ieee802.org/11/index.html
and an excellent summary
http://www.eetimes.com/story/OEG20001002S0048
My real concern with any of these pieces of legislation is the fact that a lot of spam originates from mail servers and often individuals outside the U.S.
I've been hoping that SSL's patent expiration would result in a modification to sendmail that would allow us all to join any number of third-party certificate agencies and confirm our identity and our voluntary adherence to policies like no open relays and so forth.
If we could use an SSL sendmail-to-sendmail solution with third-party identity verification, spam would disappear. It relies on open relays and open sendmail systems that accept mail and then filter later.
Hey, Dan, is O'Reilly going to make available streaming video, archived audio, transcripts, chiselled slates, papyrus, or some other method for telepresence? I can't be there, but I'd like to hear your session. I also understand that Marshall Burns, a custom 3D fabrication futurist is going to speak with a colleague about Napsterizing design of 3D stuff.
Slashdot Mirror
Google is protecting their backside. If they don't ask for a non-exclusive right when you post through this service, there is a potential for a lawsuit later if they create archives or do other things with that material. If I were in their shoes, I'd ask for a non-exclusive license, too, in order to continue be able to post.
Slashdot has at least an implicit (if not explicit) non-exclusive right to your words when you post here.
When I ran an early Internet marketing mailing list from 1994 to 1996 (www.i-m.com), I foolishly didn't initially make a condition of posting, and this, in turn, led users later to threaten me with lawsuits if I produced any for-profit or for-free versions of the list outside the archive. I eventually shut down the list, as I had better things to do than hire lawyers and sort out copyright issues.
This is horribly misinformed. Bluetooth hasn't died; it hasn't really shipped. It will, almost certainly. Intel didn't drop Bluetooth; it dropped HomeRF, a competing high-speed networking standard. Bluetooth's purpose is wholly different - mostly for very low-power synchronization and info exchange, like synching a Palm with a laptop, loading phone numbers into a cell phone, etc.
We'll see if Bluetooth lives up to it. But Intel is pouring lots of cash into the hole, as are several other major chipset makers and many many hundreds of manufacturers. As with cell phones that browse the Web, the design will determine it's really useful and consumers (business and home) actually want it.
But it's coming. 802.11b and Bluetooth won't be competing; they'll be complementary, because 802.11b, for the foreseeable future, takes up too much power, and won't be cheap enough ($20 vs. $5 ultimately) per chipset to integrate into the simple devices that will use it.
In Sweden, Telia has put WiFi in quite a few locations, and is about to expand in partnership with SAS to a number of European outlets, and a couple in the US - all SAS waiting lounges.
The deployment is underway; the real problem is roaming agreements, so you pay a single monthly fee and can access all networks. There are some problems with that, of course, because of the nature of access points and access lists. Too long to go into here.
I wrote about this at length back on Feb. 22. Here's the NY Times link (no reg required link): http://www.nytimes.com/2001/02/22/technology/22WIR E.html?pagewanted=all
HomeRF had the FCC approve a change to its implementation of FH in 2.4 GHz which boosts it to 10 Mbps in its 2.0 version, and up to 22 Mpbs in a not-yet-released 3.0 spec. The HomeRF group claims to be ready to ship by summer a variety of devices. The 5 GHz range will be dominated by 802.11a. I don't know whether its FH or DS, but FH doesn't make sense given the DS involvement in 802.11b. "a" should operate above 50 Mbps according to manufacturers. Expect delivery of equipment later this year or early next year. They will make access points with both 2.4 GHz ("b") and 5 GHz ("a") chipsets and antennas to handle transition from b to a, especially in enterprises. Here's the 802.11 (wireless LAN) IEEE workgroups site: http://www.ieee802.org/11/index.html and an excellent summary http://www.eetimes.com/story/OEG20001002S0048
My real concern with any of these pieces of legislation is the fact that a lot of spam originates from mail servers and often individuals outside the U.S. I've been hoping that SSL's patent expiration would result in a modification to sendmail that would allow us all to join any number of third-party certificate agencies and confirm our identity and our voluntary adherence to policies like no open relays and so forth. If we could use an SSL sendmail-to-sendmail solution with third-party identity verification, spam would disappear. It relies on open relays and open sendmail systems that accept mail and then filter later.
Hey, Dan, is O'Reilly going to make available streaming video, archived audio, transcripts, chiselled slates, papyrus, or some other method for telepresence? I can't be there, but I'd like to hear your session. I also understand that Marshall Burns, a custom 3D fabrication futurist is going to speak with a colleague about Napsterizing design of 3D stuff.