Periods in URLS will be for losers who can't afford 'real' Internet names Dotless domain users will run afoul of parsers that reject e-mail addresses lacking syntactically valid FQDNs.
Now I can finally realize my dream and create the ".isgay" TLD. Can I get igpayatinlay.isgay? I want to build a site dedicated to Google Image Searching in Pig Latin.
IPv6's limit is unreasonable in that is unreasonably large. That's the point. Specifically, that's the good point. The bad point is when it is unreasonably small, usually because someone thought it was reasonably large.
The best point of "Reasonable limits aren't" is to avoid setting a limit at all and mandate coding for arbitrarily large numbers.
If we instead spread them over the planets surface, then there is 226854911280625642308 [IPv6 addresses] for every square cm of land-area (approximately 1/5th that if you also need ips for every square cm of water).
Yes, that's nicely unreasonable, even for a society that doesn't just live on the surface but rather builds tall (and deep) structures so people can live on top of each other.
Unless of course you need to use your IP as your encryption key. Worse if it needs to be prime: there are only approximately 2^128 / ln( 2^128 ) = 3.83534127545935 * 10^48 of them. Of course, you'd see that as an example of gross mismanagement, and you might be right. Still, I expect owning a prime IPv6 address would be more desirable than a composite one. Great for use as the public key for the NAT behind it. Assuming of course that it isn't one of the trivial primes, though they'll have their own interests. (Who wants/has 0000:0000:0000:0000:0000:0000:0000:0002 ?)
But seriously, I think IPv6 stands the test of "Reasonable limits aren't" very well. It's limits aren't reasonable, but in the good way.
The main bit is from pages 85-95 (TITLE II, appending to the Foreign Intelligence surveillance Act of 1970 (50 U.S.C. 1801 et eq.)a "TITLE VIII--PROTECTION OF PERSONS ASSISTING THE GOVERNMENT").
Though TITLE I pages 15 and 45 also have "Release From Liability" sections reading in commonality:
RELEASE FROM LIABILITY. No cause of action shall lie in any court against any electronic communication service provider for providing any information, facilities, or assistance in accordance with... pursuant to...
Now, I don't know about you but I think that is quite reasonable for now. When we all need 5x10^28 addresses each (not to mention the extra addresses each person can get behind a NAT) then there will be a problem.. in the meantime, "5x10^28 IP addresses should be enough for anyone";) What I mean is that limits should be unreasonably large or else they will prove to be unreasonably small. A reasonable limit will invariably be proven too low. Preferably, limits should be done away with when at all possible, but if they must exist, let them be unreasonably large.
Reasonable? If every person required one new IP address every millisecond it would still take 1.58444 x 10^18 years to exhaust them.
And I meant it jokingly here. IMO IPv6 gets it right by setting a very unreasonable (-ly high) limit. But, since you didn't laugh, I have to be serious now.
With developments today, I wouldn't be surprised if someone finds a reason to consume huge swaths of IP addresses rapidly. Maybe not by assigning every RFID tag a unique IPv6 address, but who knows how many may actually be in a single product. Or maybe, taking your figure of 5x10^28 IP addresses per person, that's a big address space in which to randomly route packets to prevent their reassembly by an outside party. You may just have to do that to protect your privacy against the ubiquitous microscopic self-replicating cameras floating around everywhere like grains of dust, each with their own IP addresses as well.
There's another phrase, I think it goes, "Programs will expand to fill available memory." If you give a huge space for IP addresses, expect IP assignments to grow to fill that address space. Even to waste it by doing sparse allocation.
There are programmers out there today that think not consuming a processor 100% all the time is a waste of processing power, so they write wastefully inefficient code all the time to utilize the processor all the time, ignoring the needs of other concurrent proceses.
There's always TiVo, I suppose... Actually, the TiVo Series3 solved my digital cable woes. Ever since Time Warner Cable installed "mystro" software on their cable boxes, they've been unusable by my analog-recording TiVos as they would fail to change channels properly or crash if said channel changes were done on-time rather than one minute early or late.
Once I had the CableCard-enabled TiVo (and signal problems were resolved with an unbalanced splitter), I've been happily recording all my digital (non-OnDemand) channels. Granted, the TiVo generally won't let me transfer any shows on an encrypted channel to my computer unless I scheduled it as a Manual Recording(*), but it does a good enough job down-converting to anamorphic video on the analog outputs for DVD burning. I just need something that will also capture the fiber audio.
(*) This has only happened the one time, recording for two hours starting 2 hours into a 4-hour timeslot, with one minute of padding at each end. It was the second half of the new The Andromeda Strain miniseries in HD.
Yeah, well, maybe I'll rip out the DVD and replace it with some super l33t faster reading one and I'll just expect it to work with all future Wii games. Well good luck finding a drive that plays both clockwise and counterclockwise.
Nevermind of course that customs only searches your property on arrival, not departure, so they're protecting against people bringing their nuclear secrets... to us? There's no cause for safety screeners to search laptops before boarding.
But under, "Won't someone think of the `nucular' bombs," they'll gladly blur the lines between safety and customs checks.
I had a need for a (short-range) wireless keyboard a few months ago and ended up going infrared so that if anyone was going to snoop me, they'd have to be in my line of sight. Some devices don't like other devices sending (to them) rogue IR signals. Notably, a TiVo controlling a cable box via infrared can't do it if it is seeing other IR signals (a big problem if you use wireless IR repeaters that will convert any RF noise back to IR). The incoming signals saturate its IR bus preventing transmission. It will delay changing the channel until the IR interference ceases. Building tents around the IR blasters won't help. I've had one fail to record all but the last 5 minutes of an hour-long show because of that.
Also, have you considered that IR reflections, like the keyboard's IR signal off the glass of your display, could permit those not in your line of sight to eavesdrop on your keystrokes?
I've lost count how many times Slashdot stories have stated Standard times during Daylight Saving Time (and sometimes stating Daylight Saving Time during Standard).
Anyway, turns out I can't run Firefox 3 on my work machine at all. At least, not until everyone gets switched to Ubuntu. This Redhat 9 installation doesn't include libpangocairo-1.0.so.0 and I lack the privilege necessary to install the RPM.
Why not give FF3 a go? The memory management situation is a *lot* better... I wanted to wait for Download Day.
Now that I have, I discover it doesn't want to run on Redhat 9 due to no libpangocairo-1.0.so.0 shared object file. So it looks like I'll have to wait until IT upgrades me to ubuntu first.
This is ridiculous. Waiting for whatever hour to download the new Firefox is like camping out in front of the store and waiting in line all night to buy a Playstation the first minute it appears on a shelf, or worse yet, paying out the nose for one on eBay when all you have to do is wait a few weeks and get one at retail price without all this nonsense. Why bombard the server to download it at the first moment of its availability? Unlike camping out in front of a store or buying on eBay to be an early adopter, one does not have to do either to get Firefox 3.0. If you've already downloaded Release Candidate 3, you already have the same file with a different name. The point in waiting is to help set a Guinness World Record for the most downloads of an application in a 24 hour period.
[On Steve Wiebe competing for the Guinness World Record for highest score in Donkey Kong] Jillian Wiebe: I never knew that the Guinness World Record Book was so... I never knew it was so important. Steve Wiebe: I guess a lot of people are... yeah, a lot of people read that book. Jillian Wiebe:[while directly looking at Steve, her father] Some people sort of ruin their lives to be in there.
I prefer this quote:
(It was, of course, as a result of the Great Ventilation and Telephone Riots of SrDt 3454, that all mechanical or electrical or quantum-mechanical or hydraulic or even wind, steam or piston-driven devices, are now required to have a certain legend emblazoned on them somewhere. It doesn't matter how small the object is, the designers of the object have got to find a way of squeezing the legend in somewhere, because it is their attention which is being drawn to it rather than necessarily that of the user's.
The legend is this:
"The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair.") Alas, that legend is too long to fit in a Slashdot tag.
People still use Flashblock? I thought newer versions of NoScript made Flashblock obsolete. I am using NoScript but not Flashblock. I currently run without the flash plug-in and run with no sound card on my work machine.
Judging from NoScript's behavior and the description of Flashblock, NoScript will enable all flash objects when scripting is allowed from a site, but Flashblock allows selective enabling of flash objects.
Slashdot Mirror
Compare slashdot.com/comments.pl to things like Sir Dr. Public, John Q. III DDS Esq.
IPv6's limit is unreasonable in that is unreasonably large. That's the point. Specifically, that's the good point. The bad point is when it is unreasonably small, usually because someone thought it was reasonably large.
The best point of "Reasonable limits aren't" is to avoid setting a limit at all and mandate coding for arbitrarily large numbers.
If we instead spread them over the planets surface, then there is 226854911280625642308 [IPv6 addresses] for every square cm of land-area (approximately 1/5th that if you also need ips for every square cm of water).Yes, that's nicely unreasonable, even for a society that doesn't just live on the surface but rather builds tall (and deep) structures so people can live on top of each other.
Unless of course you need to use your IP as your encryption key. Worse if it needs to be prime: there are only approximately 2^128 / ln( 2^128 ) = 3.83534127545935 * 10^48 of them. Of course, you'd see that as an example of gross mismanagement, and you might be right. Still, I expect owning a prime IPv6 address would be more desirable than a composite one. Great for use as the public key for the NAT behind it. Assuming of course that it isn't one of the trivial primes, though they'll have their own interests. (Who wants/has 0000:0000:0000:0000:0000:0000:0000:0002 ?)
But seriously, I think IPv6 stands the test of "Reasonable limits aren't" very well. It's limits aren't reasonable, but in the good way.
Migration, migration, BEES!
Though TITLE I pages 15 and 45 also have "Release From Liability" sections reading in commonality: RELEASE FROM LIABILITY. No cause of action shall lie in any court against any electronic communication service provider for providing any information, facilities, or assistance in accordance with
Reasonable? If every person required one new IP address every millisecond it would still take 1.58444 x 10^18 years to exhaust them.
And I meant it jokingly here. IMO IPv6 gets it right by setting a very unreasonable (-ly high) limit. But, since you didn't laugh, I have to be serious now.
With developments today, I wouldn't be surprised if someone finds a reason to consume huge swaths of IP addresses rapidly. Maybe not by assigning every RFID tag a unique IPv6 address, but who knows how many may actually be in a single product. Or maybe, taking your figure of 5x10^28 IP addresses per person, that's a big address space in which to randomly route packets to prevent their reassembly by an outside party. You may just have to do that to protect your privacy against the ubiquitous microscopic self-replicating cameras floating around everywhere like grains of dust, each with their own IP addresses as well.
There's another phrase, I think it goes, "Programs will expand to fill available memory." If you give a huge space for IP addresses, expect IP assignments to grow to fill that address space. Even to waste it by doing sparse allocation.
There are programmers out there today that think not consuming a processor 100% all the time is a waste of processing power, so they write wastefully inefficient code all the time to utilize the processor all the time, ignoring the needs of other concurrent proceses.
Once I had the CableCard-enabled TiVo (and signal problems were resolved with an unbalanced splitter), I've been happily recording all my digital (non-OnDemand) channels. Granted, the TiVo generally won't let me transfer any shows on an encrypted channel to my computer unless I scheduled it as a Manual Recording(*), but it does a good enough job down-converting to anamorphic video on the analog outputs for DVD burning. I just need something that will also capture the fiber audio.
(*) This has only happened the one time, recording for two hours starting 2 hours into a 4-hour timeslot, with one minute of padding at each end. It was the second half of the new The Andromeda Strain miniseries in HD.
The guy wasn't smuggling a warhead, he was smuggling warhead plans. Those aren't going to set off any radiological or metal detector alarms.
But of course the reason why they're telling us about this now is only because they want to justify searching all laptops at all border crossings.
Nevermind of course that customs only searches your property on arrival, not departure, so they're protecting against people bringing their nuclear secrets... to us? There's no cause for safety screeners to search laptops before boarding.
But under, "Won't someone think of the `nucular' bombs," they'll gladly blur the lines between safety and customs checks.
Also, have you considered that IR reflections, like the keyboard's IR signal off the glass of your display, could permit those not in your line of sight to eavesdrop on your keystrokes?
I've lost count how many times Slashdot stories have stated Standard times during Daylight Saving Time (and sometimes stating Daylight Saving Time during Standard).
Anyway, turns out I can't run Firefox 3 on my work machine at all. At least, not until everyone gets switched to Ubuntu. This Redhat 9 installation doesn't include libpangocairo-1.0.so.0 and I lack the privilege necessary to install the RPM.
Now that I have, I discover it doesn't want to run on Redhat 9 due to no libpangocairo-1.0.so.0 shared object file. So it looks like I'll have to wait until IT upgrades me to ubuntu first.
[On Steve Wiebe competing for the Guinness World Record for highest score in Donkey Kong]
Jillian Wiebe: I never knew that the Guinness World Record Book was so... I never knew it was so important.
Steve Wiebe: I guess a lot of people are... yeah, a lot of people read that book.
Jillian Wiebe: [while directly looking at Steve, her father] Some people sort of ruin their lives to be in there.
However, if you don't wait 'til 1 PM EST, you won't be counted for the Guinness Record.
BTW: EST? Really? So not only do I have to account for time zone, I also have to adjust for my local adherence to Daylight Saving Time?
(Or, as Bugs Bunny puts it, "diabolycal sabotaygee".)
Everyone knows invisible dragons aren't really invisible. They only look that way.
The legend is this:
"The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair.") Alas, that legend is too long to fit in a Slashdot tag.
It is not the Slashdot filter. The page you cited has the same edit. You'd think a site hosting such content would think to turn of their own filters.
Rick Gassko: Not that I'm complaining, but I usually don't like my filth this clean!
Judging from NoScript's behavior and the description of Flashblock, NoScript will enable all flash objects when scripting is allowed from a site, but Flashblock allows selective enabling of flash objects.