A typical VoIP connection uses 2kB/sec. If you talk for an hour, you've uploaded and download a grand total of 7MB in each direction. Big deal. If you talked on your phone 24/7, you'd use 5GB of bandwidth. If your ISP is going to come after you for this kind of use, you need to get rid of them posthaste and use somebody who doesn't suck.
If you think the internet is going to have problems because everybody starts making 7MB/hour phone calls, you have another thing coming.
On that same theme, a message for web site admins: don't store plaintext passwords in your database! You should be storing a hash of the password, and never be able to guess somebody's password just because they have an account on your site.
If you are distributing very small chunks of a movie with the intent that someone will collect them all and form the entire movie, you are infringing no matter how small the chunks are. Judges aren't idiots, and the law isn't as inflexible as a computer program. It doesn't matter if you hide this behind a smokescreen of "reviews" if it's obvious to any eight-year-old that the only reason the "reviews" exist is to allow people to download the movie.
The "russian" suprnova is up and works fine and at least the loki people are putting up some kind of fight so the technology isnt just considered illegal outright.
Not to mention that BT is the P2P app with significantnon-infringinguses that are more than just theoretical, and past the "I upload my crappy basement-produced MP3s for the world to see" level. Frankly, this kind of use interests me a thousand times more than the next Britney Spears pirating system.
The page you referenced said that only 2% of the arrivals at Ellis Island were sent home. Today, from what I know of our immigration policy, I would not be surprised if only 2% of immigrants are actually accepted. Only rejecting 2% of the people who arrive doesn't seem very far from "more or less an open immigration policy" to me.
Yes, that's basically what I had in mind. What's your point?
I'm not in favor of illegal immigration. I'm in favor of making illegal immigration unnecessary by vastly expanding those eligible for legal immigration.
The bottom of Sumatra is the part that's deep, deep underground (or water). The quake happened near the bottom of Sumatra, to the West of the Northern end of the island. I just think it's funny that somebody complaining about small tidbits of journalistic accuracy is going around saying "bottom" when he means "South"
Many of us realize that our ancestors were immigrants, and think that people today should get the same treatment our ancestors got a hundred years ago.
Sure, you can much more easily choose a different VoIP provider than you can a POTS provider, but how long before market consolidation leaves only one or two real VoIP choices?
My guess is never. The VoIP market doesn't show any sign of being a natural monopoly the way the telephone market is. Economies of scale won't win you very much past a certain point, so there's no reason it would ever get to the point you describe.
And speaking of poor journalism, has anyone else noticed that Fox News has the epicenter of the quake totally wrong? They put it down near the bottom of Sumatra.
As far as I'm aware, the quake was near the bottom of Sumatra. Did you mean to say "near the South of Sumatra"?
This seems to be the Linux user's favorite retort for any shortcoming. Comparing your OS's usability to Windows is like comparing your restaurant's food to McDonald's. It's true that it's better, but that doesn't mean anything.
Sorry, you have no idea what you're talking about..app bundles are actual directories, with no difference from any other directory at the filesystem level. The only part of the OS that treats them differently is the Carbon and Cocoa APIs, which will make them look like files or directories as appropriate.
If you ftp put a.app bundle, ftp will tell you that it can't put a directory, simple as that. A.app bundle doesn't have a resource fork, so it would be kind of hard to strip it. You seem to have confused the issue of bundles, which integrate perfectly into the UNIX side of things and cause basically no problems, with old single-file Carbon applications with resource forks, which are extremely rare and do break in the way you describe, but which are not.app bundles.
Did you just write four paragraphs on how to install an application on OS/2, and then call it "simple"? On OS X, it is literally a single drag with the mouse.
You shouldn't need to borrow an OS X Server CD to reformat with case-sensitive HFS+. Just boot your normal install CD in single-user mode (hold command-S while booting) and use the command-line utility from there. I've never done this, but I don't see why it wouldn't work.
Functions like loading plugins and libraries at runtime are generally handled in userland, not in the kernel (or so I think), so we're talking about the same thing. Any OS which supports a no-execute flag will support a way to mark a region of memory as executable.
I e-mailed a contact address that was no longer valid. If I had just trashed the bounce, I never would have known that my e-mail had failed, and I would have assumed that the people I was trying to contact were a bunch of jerks, instead of tracking down a working address for them. This kind of stuff happens fairly often for those of us who don't live in a cave.
In short they would have to provide a way to mark a write-able buffer as executable
Every single OS that supports a no-execute bit provides this (including Windows), otherwise things like dynamically-loaded libraries wouldn't work too well. JITs that run on these OSes are, of course, coded to call this when necessary. It's not really a big deal.
Remember that even though NX is The Next Big Thing in the x86 world, rationally-designed CPU architectures have had no-execute bits in their MMUs for a long, long time, and the OSes that run on them tend to take advantage of it.
Slashdot Mirror
Those rates aren't very hard to beat. For example, you quote 5 cents a minute to France, whereas Skype only charges 2 cents a minute.
What kind of broken connection do you have where you actually notice the 2k/sec that the VoIP connection takes up?
Of course, this doesn't change your other objections, which are completely understandable.
"Huge amount of bandwidth"? What are you smoking?
A typical VoIP connection uses 2kB/sec. If you talk for an hour, you've uploaded and download a grand total of 7MB in each direction. Big deal. If you talked on your phone 24/7, you'd use 5GB of bandwidth. If your ISP is going to come after you for this kind of use, you need to get rid of them posthaste and use somebody who doesn't suck.
If you think the internet is going to have problems because everybody starts making 7MB/hour phone calls, you have another thing coming.
On that same theme, a message for web site admins: don't store plaintext passwords in your database! You should be storing a hash of the password, and never be able to guess somebody's password just because they have an account on your site.
It was caused by a really big earthquake on the ocean floor....
If you are distributing very small chunks of a movie with the intent that someone will collect them all and form the entire movie, you are infringing no matter how small the chunks are. Judges aren't idiots, and the law isn't as inflexible as a computer program. It doesn't matter if you hide this behind a smokescreen of "reviews" if it's obvious to any eight-year-old that the only reason the "reviews" exist is to allow people to download the movie.
The "russian" suprnova is up and works fine and at least the loki people are putting up some kind of fight so the technology isnt just considered illegal outright.
Not to mention that BT is the P2P app with significant non-infringing uses that are more than just theoretical, and past the "I upload my crappy basement-produced MP3s for the world to see" level. Frankly, this kind of use interests me a thousand times more than the next Britney Spears pirating system.
The economy is not a zero-sum game. Those immigrants could be a net gain for California, not a loss that has to be minimized.
The page you referenced said that only 2% of the arrivals at Ellis Island were sent home. Today, from what I know of our immigration policy, I would not be surprised if only 2% of immigrants are actually accepted. Only rejecting 2% of the people who arrive doesn't seem very far from "more or less an open immigration policy" to me.
Yes, that's basically what I had in mind. What's your point?
I'm not in favor of illegal immigration. I'm in favor of making illegal immigration unnecessary by vastly expanding those eligible for legal immigration.
The bottom of Sumatra is the part that's deep, deep underground (or water). The quake happened near the bottom of Sumatra, to the West of the Northern end of the island. I just think it's funny that somebody complaining about small tidbits of journalistic accuracy is going around saying "bottom" when he means "South"
Many of us realize that our ancestors were immigrants, and think that people today should get the same treatment our ancestors got a hundred years ago.
Sure, you can much more easily choose a different VoIP provider than you can a POTS provider, but how long before market consolidation leaves only one or two real VoIP choices?
My guess is never. The VoIP market doesn't show any sign of being a natural monopoly the way the telephone market is. Economies of scale won't win you very much past a certain point, so there's no reason it would ever get to the point you describe.
And speaking of poor journalism, has anyone else noticed that Fox News has the epicenter of the quake totally wrong? They put it down near the bottom of Sumatra.
As far as I'm aware, the quake was near the bottom of Sumatra. Did you mean to say "near the South of Sumatra"?
If it's a relic, then it's not Russian, it's Soviet. If you want to call it current then it could be Russia, but then there would be some irony
Yeah, because the cataclysmic breakup of the largest country on the planet never generates any opportunity for irony....
Ooh, that suggests a great riff on one of my favorite things....
ENTIRE STATE OF RHODE ISLAND DESTROYED IN ENORMOUS EXPLOSION
Details at 11!
My faith in the UW system (I'm a UW-Milwaukee alum) has now been restored. :-)
It's far easier than windows.
This seems to be the Linux user's favorite retort for any shortcoming. Comparing your OS's usability to Windows is like comparing your restaurant's food to McDonald's. It's true that it's better, but that doesn't mean anything.
I said you should boot in single-user mode from your install CD. Are you going to try to reformat your CD?
Sorry, you have no idea what you're talking about. .app bundles are actual directories, with no difference from any other directory at the filesystem level. The only part of the OS that treats them differently is the Carbon and Cocoa APIs, which will make them look like files or directories as appropriate.
.app bundle, ftp will tell you that it can't put a directory, simple as that. A .app bundle doesn't have a resource fork, so it would be kind of hard to strip it. You seem to have confused the issue of bundles, which integrate perfectly into the UNIX side of things and cause basically no problems, with old single-file Carbon applications with resource forks, which are extremely rare and do break in the way you describe, but which are not .app bundles.
If you ftp put a
Did you just write four paragraphs on how to install an application on OS/2, and then call it "simple"? On OS X, it is literally a single drag with the mouse.
You shouldn't need to borrow an OS X Server CD to reformat with case-sensitive HFS+. Just boot your normal install CD in single-user mode (hold command-S while booting) and use the command-line utility from there. I've never done this, but I don't see why it wouldn't work.
Functions like loading plugins and libraries at runtime are generally handled in userland, not in the kernel (or so I think), so we're talking about the same thing. Any OS which supports a no-execute flag will support a way to mark a region of memory as executable.
Last week.
I e-mailed a contact address that was no longer valid. If I had just trashed the bounce, I never would have known that my e-mail had failed, and I would have assumed that the people I was trying to contact were a bunch of jerks, instead of tracking down a working address for them. This kind of stuff happens fairly often for those of us who don't live in a cave.
In short they would have to provide a way to mark a write-able buffer as executable
Every single OS that supports a no-execute bit provides this (including Windows), otherwise things like dynamically-loaded libraries wouldn't work too well. JITs that run on these OSes are, of course, coded to call this when necessary. It's not really a big deal.
Remember that even though NX is The Next Big Thing in the x86 world, rationally-designed CPU architectures have had no-execute bits in their MMUs for a long, long time, and the OSes that run on them tend to take advantage of it.