You always have a choice. Go fishing. Eat a dog. Eat a dead body. Whatever it takes.
You forgot to include a common "choice": Die.
When the first settlers landed here, the situation they were faced with was much worse than what we are talking about today.
The first settlers found plenty of land area with opportunities for hunting and fishing, as well as water. Haiti is short of food and water, and hunting and fishing won't fix that in the short term.
I'm guessing that they don't count mails to non-existent mail boxes as spam (it's dropped before the spam/no-spam determination). CERN probably counts it as spam.
I don't know where you get this from. All that SPF gets you is that you receive less "backscatter" spam, non-delivery-reports for mail you didn't send in the first place. For most people, that's a tiny fraction of the spam they receive. The majority of spam is sent from domains with valid SPF records and passes SPF checks.
Right now the vast majority of spam is sent by compromised computers. What would stop those computers from paying the micropayments? Sure, it'd be nice to collect a few dollars from the incoming spam, but I'd feel a bit evil taking money from random people around the world. Even if they should have been smarter.
You can say that fraudulent transactions are only a few percent of total transactions today, but it will difficult to build a micropayment system which has as many abuse checks as the current transaction systems -- and the current systems would kill your idea with transaction fees often in the range of $0.50.
Firefox can't realistically license H.264. We're talking a license for unlimited copies with the right to do pretty much anything you want with the copies, including turning them into video editing software. It would be the last license sold, because everyone else can just piggy back on it.
Modern packet sniffers support IPSEC. Getting the keys out can be fun, but not all that difficult on e.g. Linux. Keeping up with the key changes adds a bit of fun too.
But 5000 FreeBSD instances with Xen? Surely you'd want a shared kernel solution for that many instances. If we assume that a minimal FreeBSD kernel can run in 2MB, that's 10GB just for the kernels before you hit user space. Unless Xen does memory deduplication, of course.
Iran doesn't need to launch anything, it just needs to be able to set off a nuclear weapon in the path of an invading army. That's the true lesson of the last Iraq war: Make sure you have Weapons of Mass Destruction (real ones, i.e. nuclear devices), then you won't get invaded.
Iran would lose in a nuclear exchange with just about anyone, but that doesn't really matter, because they are unlikely to get themselves into one.
DSL routers are universally crap. I don't understand why adding a DSL chip to an otherwise ok router makes it prone to random reboots, makes its wireless unreliable, and breaks UPNP... Yet that is pretty much my experience with all DSL routers. Oh and the DSL tends to be flaky too, for good measure.
Meanwhile pure DSL modems are fairly universally good and stable.
Email is intended to be unreliable, so there can never be an assumption that your mail isn't going to be blocked as spam for any of a number of reasons.
Email isn't intended to be unreliable. The various Internet email protocols were written in a way that makes the likelihood of failures low and practically guarantees you at least a message bounce. Spam has changed this in numerous ways, but there are two major ones. Systems now intentionally reject mail, even though it could have reached its destination, and bounce messages are no longer sent. You can't change the protocols that way and still have a reliable system, unfortunately, but it was never INTENDED to end this way.
It's way too late for that, and I only had the idea a few years ago -- once it became clear that IPv6 wasn't going to succeed in time.
Certainly it's a case of 20/20 hindsight; I'm not claiming that I could have foreseen this 10 or 20 years ago. I'm just rather sad that Carrier Grade NAT won.
Security and identity management doesn't imply loss of privacy. If things are done right, you can make up an identity any time you want. Your bank won't trust that identity at first, but that's a feature, not a bug.
It would have been fairly easy to repurpose the existing source routing IPv4 header as an IP address extension. That gives you 32 extra bits and you can do it more than once. If the end point you talk to doesn't send back the header, you fall back to traditional NAT.
It doesn't give you all the other benefits of IPv6, but those only really apply when you're IPv6-only, not dual stacked. And IPv6-only is a distant dream. Right now it just means you have to learn everything twice with subtle differences.
Apple did. The Airport is the only sane IPv6 CPE for home use at this point. Other devices can be made to behave as well or better, but they need configuration.
Ouch, changing taxes within the state can be a problem (but then Amazon UK has to handle the Channel Islands which probably presents similar problems). Varying tax on different items is very common across Europe. Generally luxury goods are taxed higher, and it can be somewhat amusing to compare which countries consider which items to be luxuries. Well perhaps I'm just easily amused.
Amazon UK manages to collect the appropriate VAT, depending on country. Which is why, if you buy from e.g. Denmark, you should order from one of the smaller UK book stores so you get to pay the UK VAT (0% on books) instead of the Danish one (25% on everything).
Slashdot Mirror
You always have a choice. Go fishing. Eat a dog. Eat a dead body. Whatever it takes.
You forgot to include a common "choice": Die.
When the first settlers landed here, the situation they were faced with was much worse than what we are talking about today.
The first settlers found plenty of land area with opportunities for hunting and fishing, as well as water. Haiti is short of food and water, and hunting and fishing won't fix that in the short term.
I'm guessing that they don't count mails to non-existent mail boxes as spam (it's dropped before the spam/no-spam determination). CERN probably counts it as spam.
Insta-death for most of the Internet, too...
I don't know where you get this from. All that SPF gets you is that you receive less "backscatter" spam, non-delivery-reports for mail you didn't send in the first place. For most people, that's a tiny fraction of the spam they receive. The majority of spam is sent from domains with valid SPF records and passes SPF checks.
Right now the vast majority of spam is sent by compromised computers. What would stop those computers from paying the micropayments? Sure, it'd be nice to collect a few dollars from the incoming spam, but I'd feel a bit evil taking money from random people around the world. Even if they should have been smarter.
You can say that fraudulent transactions are only a few percent of total transactions today, but it will difficult to build a micropayment system which has as many abuse checks as the current transaction systems -- and the current systems would kill your idea with transaction fees often in the range of $0.50.
Chrome and Safari aren't Open Source or Free Software. You can't legally turn them into video editors and then redistribute them.
Firefox can't realistically license H.264. We're talking a license for unlimited copies with the right to do pretty much anything you want with the copies, including turning them into video editing software. It would be the last license sold, because everyone else can just piggy back on it.
Modern packet sniffers support IPSEC. Getting the keys out can be fun, but not all that difficult on e.g. Linux. Keeping up with the key changes adds a bit of fun too.
But 5000 FreeBSD instances with Xen? Surely you'd want a shared kernel solution for that many instances. If we assume that a minimal FreeBSD kernel can run in 2MB, that's 10GB just for the kernels before you hit user space. Unless Xen does memory deduplication, of course.
Iran doesn't need to launch anything, it just needs to be able to set off a nuclear weapon in the path of an invading army. That's the true lesson of the last Iraq war: Make sure you have Weapons of Mass Destruction (real ones, i.e. nuclear devices), then you won't get invaded.
Iran would lose in a nuclear exchange with just about anyone, but that doesn't really matter, because they are unlikely to get themselves into one.
Anyone with your morals, that is.
Iran and Pakistan probably only have fission bombs. Not fun to be hit by, but not that much of a problem for the rest of the world, annihilation-wise.
That really should have worked, with a sufficiently long antenna. It'll be induction, but that ought to count too.
Because a significant percentage of non-spam mail actually makes it through to gmail, unlike hotmail.
DSL routers are universally crap. I don't understand why adding a DSL chip to an otherwise ok router makes it prone to random reboots, makes its wireless unreliable, and breaks UPNP... Yet that is pretty much my experience with all DSL routers. Oh and the DSL tends to be flaky too, for good measure.
Meanwhile pure DSL modems are fairly universally good and stable.
Email is intended to be unreliable, so there can never be an assumption that your mail isn't going to be blocked as spam for any of a number of reasons.
Email isn't intended to be unreliable. The various Internet email protocols were written in a way that makes the likelihood of failures low and practically guarantees you at least a message bounce. Spam has changed this in numerous ways, but there are two major ones. Systems now intentionally reject mail, even though it could have reached its destination, and bounce messages are no longer sent. You can't change the protocols that way and still have a reliable system, unfortunately, but it was never INTENDED to end this way.
It's way too late for that, and I only had the idea a few years ago -- once it became clear that IPv6 wasn't going to succeed in time.
Certainly it's a case of 20/20 hindsight; I'm not claiming that I could have foreseen this 10 or 20 years ago. I'm just rather sad that Carrier Grade NAT won.
It's a research project. It will do whatever the researchers want it to. University academics aren't exactly known as freedom-hating tyrants.
Security and identity management doesn't imply loss of privacy. If things are done right, you can make up an identity any time you want. Your bank won't trust that identity at first, but that's a feature, not a bug.
It would have been fairly easy to repurpose the existing source routing IPv4 header as an IP address extension. That gives you 32 extra bits and you can do it more than once. If the end point you talk to doesn't send back the header, you fall back to traditional NAT.
It doesn't give you all the other benefits of IPv6, but those only really apply when you're IPv6-only, not dual stacked. And IPv6-only is a distant dream. Right now it just means you have to learn everything twice with subtle differences.
Apple did. The Airport is the only sane IPv6 CPE for home use at this point. Other devices can be made to behave as well or better, but they need configuration.
Ouch, changing taxes within the state can be a problem (but then Amazon UK has to handle the Channel Islands which probably presents similar problems). Varying tax on different items is very common across Europe. Generally luxury goods are taxed higher, and it can be somewhat amusing to compare which countries consider which items to be luxuries. Well perhaps I'm just easily amused.
Names were translated too though.
News for you: The UK is part of the EU.
Amazon UK manages to collect the appropriate VAT, depending on country. Which is why, if you buy from e.g. Denmark, you should order from one of the smaller UK book stores so you get to pay the UK VAT (0% on books) instead of the Danish one (25% on everything).