What are your views toward copyright laws as they exist in the U.S. today? More specifically, how do you feel about the length of time that a work is protected, is it long enough, too long, or just right?
P.S. I think it was really cool that you completed the novel for that kid that died before he finished it.
Multicast has its place. It works well with radio/television type broadcasts, where people join in and drop out while they are running. It doesn't work too well when you allow the client to start/stop/pause the stream.
Doesn't this raise an issue of what constitutes a system? Is it the hard drive that the software resides on, or is it the motherboad? Could you move the hard drive to the new system without breaking the Eula?
Actually that is totally incorrect. 150ms is perfectly serviceable for VoIP conversations as per Cisco's recommendation. The length of the delay isn't so important as keeping it consistent. If the hardware knows there is around a 150ms delay, it can buffer the conversation some and you end up with a nice smooth phone call.
Cisco's standard application of VoIP puts the phones in a vlan, and all traffic that comes in from the other switch port in the phone in another vlan. The recommend using vlans to keep the voice traffic separate from the data traffic. While everyone out there may not be implementing it this way, since the article mentioned Cisco specifically, I think this is important.
Because I would like to have more than one handset in my house without having to pay 20-40 for each one of them.
Because the voice quality on cellular still isn't nearly what it is on a landline ( I don't care what the sprint commercial says, they suck rocks).
Because in most areas you can get fewer calls going in a cell than you can on landlines, so when something big happens, like a tornado, I want to be able to use my phone. Of course cable will be out since it relys on power, and not many cable providers have UPSs in all the distribution points.
Until broadband providers support quality of service as in 802.1q&p, this isn't going to be very popular. Most people will get pretty pissed when their phone service starts to crap out because the kid next door just set up a warez site, and your shared bandwidth is being hogged.
I love VoIP, and can't wait until my cable provider has it, assuming they do it right.
And how exactly do you propose determining if a site can tolerate the traffic? Maybe a mandatory form that has to be filled out by the operator of the websites ISP that states what their bandwidth availability is, combined with a geek rating of the story?
Umm, the publisher put that in the book. They could change it to whatever meets their needs. They could require Amazon tear out the last 10 pages in any book they sell if they wanted too. The point is that the publisher is the one that makes the rules about what to do with the remaindered books, so they just need to change the rules...
Except that now they will be seen as weak, and so are far more likely to get sued by people that they bug. Shouldn't be too long before they are culled from the herd....
So couldn't they just make Amazon send them back the cover of any book that was remaindered? They could still sell it, but not as many people would buy it.
Actually the banks aren't the last ones... The FAA still uses IBM RJE. They had a Data General until about 4 years ago. Lots of Equinox stuff all over the place. Some nasty old BARR attached line printers using some sort of tn3270 hardware. They have really old consoles with the keyboard built into it, looks like star trek or something. IBM 4plex amber plasma monitors. More JCL/Infoman/ISPF/COBOL/... old stuff than anyone would ever care to imagine.
quote: "Peak usage times on DSL introduce just as much slowdown to the user with his "dedicated" pipe as they would to the Cable user with his "shared" pipe. "
That isn't very accurate. Every DSL customer has a guaranteed amount of bandwidth to the CO, which starts getting shared from that point on. Depending on how the telco has set up their network, the CO may have more than enough bandwidth to be non-blocking all the way back to their core. From there if the customer is accessing stuff that is on the telco's network, or that the telco has direct high speed links to, there will be very little slowdown even at peak times. Access to the Internet will probably be slow due to oversubscription of their PoP links, but that is pretty much to be expected.
This differs from cable in that everyone in a neighborhood node shares their bandwidth right from the start. That means that at peak times, the customer could experience slow connections even to something on the cable companies local network.
Granted most people probably don't do much of anything that is on the local companies network, so the essence of what you said is true. On the other hand, if people use the companies caching proxy server to access web pages and are just looking at the standard static content for the most part, DSL subscribers are likely to be much happier than cable users.
Mr. Anthony,
What are your views toward copyright laws as they exist in the U.S. today? More specifically, how do you feel about the length of time that a work is protected, is it long enough, too long, or just right?
P.S. I think it was really cool that you completed the novel for that kid that died before he finished it.
Multicast has its place. It works well with radio/television type broadcasts, where people join in and drop out while they are running. It doesn't work too well when you allow the client to start/stop/pause the stream.
Did anyone else that read that article get the feeling it was a hoax? It all just sounds so campy and hoaky. Like some sort of cheesy propoganda.
I can almost hear they counselor from South Park now, "Stealing bandwith is bad...MKay... Hacking cablemodems is bad...MKay..."
You know what I mean?
Heh, The University of Oklahoma regularly ships out ~400mbits of data during regular semesters. Approximately 80% of this data is P2P.
You better hope IBM doesn't see that post, they'll sue your ass off for copyright infringement.
Engraver, they're like $5 from radio shack
A small lockbox with holes drilled in the bottom that she can then mount to the bottom of her closet to put her valuables in. It saved my butt.
A number of someone to call when she gets homesick and freaked out.
Several $20 bills in seperate envelopes, for when she runs out of $$$ and needs a drink.
Napster is irrelevant.
Filesharing is going quite strong.
BMG is throwing good money after bad.
Its called humor, sheesh...
Hmm, why not just make the credit card company the one and only call you make to cancel an account that auto-bills?
Doesn't this raise an issue of what constitutes a system? Is it the hard drive that the software resides on, or is it the motherboad? Could you move the hard drive to the new system without breaking the Eula?
Actually that is totally incorrect. 150ms is perfectly serviceable for VoIP conversations as per Cisco's recommendation. The length of the delay isn't so important as keeping it consistent. If the hardware knows there is around a 150ms delay, it can buffer the conversation some and you end up with a nice smooth phone call.
Cisco's standard application of VoIP puts the phones in a vlan, and all traffic that comes in from the other switch port in the phone in another vlan. The recommend using vlans to keep the voice traffic separate from the data traffic. While everyone out there may not be implementing it this way, since the article mentioned Cisco specifically, I think this is important.
Because I would like to have more than one handset in my house without having to pay 20-40 for each one of them.
Because the voice quality on cellular still isn't nearly what it is on a landline ( I don't care what the sprint commercial says, they suck rocks).
Because in most areas you can get fewer calls going in a cell than you can on landlines, so when something big happens, like a tornado, I want to be able to use my phone. Of course cable will be out since it relys on power, and not many cable providers have UPSs in all the distribution points.
Until broadband providers support quality of service as in 802.1q&p, this isn't going to be very popular. Most people will get pretty pissed when their phone service starts to crap out because the kid next door just set up a warez site, and your shared bandwidth is being hogged.
I love VoIP, and can't wait until my cable provider has it, assuming they do it right.
Does xenu.net promote "hate"? I thought they just told the truth.
And how exactly do you propose determining if a site can tolerate the traffic? Maybe a mandatory form that has to be filled out by the operator of the websites ISP that states what their bandwidth availability is, combined with a geek rating of the story?
Umm, the publisher put that in the book. They could change it to whatever meets their needs. They could require Amazon tear out the last 10 pages in any book they sell if they wanted too. The point is that the publisher is the one that makes the rules about what to do with the remaindered books, so they just need to change the rules...
Except that now they will be seen as weak, and so are far more likely to get sued by people that they bug. Shouldn't be too long before they are culled from the herd....
So couldn't they just make Amazon send them back the cover of any book that was remaindered? They could still sell it, but not as many people would buy it.
So defibrulators must be pretty darn dangerous.
Its been in the Neiman Marcus catalog for a while.
s +submarine
Check out this google link:
http://www.google.com/search?hl=en&q=neiman+marcu
I guess you don't set up or work on many cisco routers/switches then eh?
Yeah, I'm pretty happy with mine too.
Actually the banks aren't the last ones... The FAA still uses IBM RJE. They had a Data General until about 4 years ago. Lots of Equinox stuff all over the place. Some nasty old BARR attached line printers using some sort of tn3270 hardware. They have really old consoles with the keyboard built into it, looks like star trek or something. IBM 4plex amber plasma monitors. More JCL/Infoman/ISPF/COBOL/... old stuff than anyone would ever care to imagine.
quote: "Peak usage times on DSL introduce just as much slowdown to the user with his "dedicated" pipe as they would to the Cable user with his "shared" pipe. "
That isn't very accurate. Every DSL customer has a guaranteed amount of bandwidth to the CO, which starts getting shared from that point on. Depending on how the telco has set up their network, the CO may have more than enough bandwidth to be non-blocking all the way back to their core. From there if the customer is accessing stuff that is on the telco's network, or that the telco has direct high speed links to, there will be very little slowdown even at peak times. Access to the Internet will probably be slow due to oversubscription of their PoP links, but that is pretty much to be expected.
This differs from cable in that everyone in a neighborhood node shares their bandwidth right from the start. That means that at peak times, the customer could experience slow connections even to something on the cable companies local network.
Granted most people probably don't do much of anything that is on the local companies network, so the essence of what you said is true. On the other hand, if people use the companies caching proxy server to access web pages and are just looking at the standard static content for the most part, DSL subscribers are likely to be much happier than cable users.