Most ISPs report that a very small number of users use the majority of their bandwidth
Yes, it's called the Pareto principle. Basic fact of economics, and not unusual. It even applies to ER visits.
Fairly set caps that accurately reflect the increased costs of increased usage, or a service like water or gas where you pay a connection fee and a per gigabyte fee, possibly with tiers so costs increase faster with very high usage.
Works for me, so long as the amount they charge reflects their actual costs. I'll happily pay 3 cents a gigabyte.
The amount of data I transfer incurs costs from their upstream providers (or, in the case of the really big ISPs, the traffic affects the networks that will peer with them for free).
And they are welcome to pass that cost on to me. I'll gladly pay the approx. 3 cents per GB.
Wait, they want to charge $1 per GB? Suddenly it seems less reasonable, yes?
There are a lot of new Linux users who are comfortable enough with Ubuntu, and even dicking around in bash, but who are not comfortable compiling stuff from source because it's not immediately clear how you go about removing, upgrading, etc. without the package manager. Yum and Apt are a hell of a crutch.
Yeah, if only there were some APT-like tool for installing source code and necessary dependencies, and then compiling the source into a.deb package.
Yet, in spite of being a sound technology (sorry), it took years before it finally reached consumer products. Even now the uptake is slow.
Presumably NXT are charging too much to license their patents. I only know of one speaker system that uses NXT technology, the Mission M-Cube, and it costs over $2000. With that kind of availability, it's easy to see why uptake has been slow.
You don't need that most of the time (everything on the network segment has an fe80:: address anyway)
Unfortunately, fe80:: addresses are link-local, so they require the interface as part of the address in order to disambiguate them; e.g. fe80::1:1%eth0. And there's a lot of software that claims to be IPv6 aware, but doesn't understand addresses in that format.
My main problem with yum is that it's incredibly slow.
I've also had situations where it seems unable to determine that if it upgrades package A from version n to version n+1, and package B from version m to version m+1, that it doesn't need to worry that package B version m+1 clashes with package A version n.
'First of all, I don't know how to make money on it'
That's easy. Make it not suck, then sell copies.
Of course, if you're RedHat, that would require getting rid of RPM and yum, and moving to a packaging system that doesn't suck like APT and dpkg, so it's not going to happen.
If I use OO, I'm pretty much stuck with whatever the developer cloud surrounding OOO decides to release.
Not at all. You can pay someone to make some changes you want to OpenOffice, or you can take all your documents and move them to another piece of software, since it's an open file format.
It's not just a known encryption algorithm, it's DRM, so there's a process for getting and exchanging keys and so forth.
Not on the Kindle. It's a totally mundane symmetric encryption algorithm; the key is generated from the serial number in the firmware. There's no key exchange, there are no certificates. It really is the equivalent of "AES using the serial number of the hardware", but with a less well known encryption algorithm and some obfuscation of the serial number.
How about this: I don't have an iPhone or an iPod Touch. I'm just pointing out that the rationalization offered for charging iPod owners for firmware upgrades is crap.
Sony doesn't charge me for firmware upgrades for my PS3. Nintendo doesn't charge me for firmware upgrades for my Wii. BlackBerry and T-Mobile don't charge me for upgrades for my BlackBerry.
And most tellingly, Apple doesn't charge me for firmware upgrades for my Time Capsule, even when they add functionality.
Slashdot Mirror
Yup. It's not metering per se that I'm against; it's $1 per GB when the bandwidth costs them pennies.
Yes, it's called the Pareto principle. Basic fact of economics, and not unusual. It even applies to ER visits.
Works for me, so long as the amount they charge reflects their actual costs. I'll happily pay 3 cents a gigabyte.
And they are welcome to pass that cost on to me. I'll gladly pay the approx. 3 cents per GB.
Wait, they want to charge $1 per GB? Suddenly it seems less reasonable, yes?
Would it kill you to use a serious dictionary rather than the piece of crap known as Webster's?
Yeah, if only there were some APT-like tool for installing source code and necessary dependencies, and then compiling the source into a .deb package.
I'm sick of lugging dead tree around and searching through rules manually. I just want PDFs (or even better, HTML.)
But if WotC will sell me PDFs, I guess I don't mind that they come with a hunk of dead tree I can leave at home.
Presumably NXT are charging too much to license their patents. I only know of one speaker system that uses NXT technology, the Mission M-Cube, and it costs over $2000. With that kind of availability, it's easy to see why uptake has been slow.
You are totally wrong about Metroid Prime. Given that you liked RE:4, I'm betting you'd love Metroid Prime.
Yeah, well, we're talking American Airlines here, so that's pretty unlikely.
Unfortunately, fe80:: addresses are link-local, so they require the interface as part of the address in order to disambiguate them; e.g. fe80::1:1%eth0. And there's a lot of software that claims to be IPv6 aware, but doesn't understand addresses in that format.
Well, it's not ideal, but 6to4 will give you automatic IPv6 connectivity even if your ISP only provides IPv4. That's what I did.
Well, that's a false dichotomy if ever I heard one.
Oh, I was thinking of 5.2 rather than 6.
Fedora 11 alpha may have a fast version of Yum.
RHEL 5 and 6 have a version that's painfully slow, compared to APT running on similar hardware.
My main problem with yum is that it's incredibly slow.
I've also had situations where it seems unable to determine that if it upgrades package A from version n to version n+1, and package B from version m to version m+1, that it doesn't need to worry that package B version m+1 clashes with package A version n.
That's easy. Make it not suck, then sell copies.
Of course, if you're RedHat, that would require getting rid of RPM and yum, and moving to a packaging system that doesn't suck like APT and dpkg, so it's not going to happen.
Fortunately, we have Ubuntu.
Not at all. You can pay someone to make some changes you want to OpenOffice, or you can take all your documents and move them to another piece of software, since it's an open file format.
Then don't.
Where is "here"? Redmond, Washington?
Not on the Kindle. It's a totally mundane symmetric encryption algorithm; the key is generated from the serial number in the firmware. There's no key exchange, there are no certificates. It really is the equivalent of "AES using the serial number of the hardware", but with a less well known encryption algorithm and some obfuscation of the serial number.
I think you are mistaking "Apple does not need to charge people" (my claim) from "Apple needs to not charge people" (your strawman).
How about this: I don't have an iPhone or an iPod Touch. I'm just pointing out that the rationalization offered for charging iPod owners for firmware upgrades is crap.
Sony doesn't charge me for firmware upgrades for my PS3. Nintendo doesn't charge me for firmware upgrades for my Wii. BlackBerry and T-Mobile don't charge me for upgrades for my BlackBerry.
And most tellingly, Apple doesn't charge me for firmware upgrades for my Time Capsule, even when they add functionality.
So I don't buy the excuse.
No it doesn't. You can buy DRM-free e-books from fictionwise.com in Kindle-compatible .mobi format that you can just copy onto your Kindle via USB.