Yes, there’s nothing funny about Uranus. Let’s forget the childish humor and take a serious, scholarly look at Uranus. To many people it’s just a giant cloud of gas where the sun doesn’t shine, but those of us who are enthusiastic about Uranus know that it has many secrets.
Surprising as it may seem, we don’t have all that many photographs of Uranus. Yes, the Pioneers sent back pictures of Uranus, lots of them. But there are very few images that are high enough resolution and quality to show the faint rings around Uranus. Perhaps the excitement around Project Icarus will give us the excuse we need to take another long, hard look at Uranus.
Even if you have no idea how to find Uranus, you can still appreciate its unusual configuration. Scientists still don’t understand why Uranus is tilted sideways. Also, while we know what’s near the surface, we still aren’t sure of the exact chemical mixture deep inside Uranus. Are the moons stable, or are they spiraling into Uranus?
With so much to learn, we must hope that NASA will probe the depths of Uranus soon. Yes, there are many technical issues that will need to be resolved, and problems to be faced—but we put men on the moon, and I’m sure that given sufficient motivation, NASA’s engineers can lick Uranus too.
IBM picked Microsoft. Some suggest that it may be something to do with IBM CEO John Opel being friends with Bill Gates' mother from their work on the same United Way board.
The day Chrome has true support for NoScript, I'll switch back. Never before.
Chrome has the equivalent of NoScript built in. If a site tries to run scripts, you get an icon to the right of the URL bar. Clicking on that gives you a drop-down to let you enable scripts for that site.
The Internet *is* running IPv6 though. There are numerous IPv6-only web sites.
Would it be reasonable if a router was incompatible with YouTube? I mean, it doesn't specifically say that that particular web site is supported, right?
I use IP addresses to demonstrate whether or not DNS is the cause of a failure. But when I do so, they are right there on the screen available to copy and paste. And it's something I do very infrequently.
Won't work everywhere. In the UK there's a concept of a product being fit for use, for example. Regardless of whether something is stated on the box, if it's functionality a reasonable person would expect (e.g. a 2011 router having full compatibility with the 2011 Internet), you can return the product for a full refund if it doesn't have it. The US similarly has the concept of fit for purpose. Are these routers being sold with a license agreement that says "We do not warrant that you will be able to use this product to connect to the Internet"? I rather doubt it, and even if they are I rather doubt that a judge would uphold that agreement. I guess it's possible, though. We'll see if Apple manages to wriggle out of the class action lawsuit against it for selling phones that can't make a phone call if you're holding them in your left hand.
Nope, can't say it does except extremely rarely. And if it does, the solution is to fix it, not to use bare IP addresses which will break when the services move to a different address.
Right now reverse lookup is less than 100% correct on my work LAN. But that should never ever happen so I must be hallucinating.
Hey, if I had incompetent morons run my networks I could get IP addresses to fail too.
And Kubrick also apparently hated letterboxing? I think he was wrong on that, personally. The Shining really suffers when it's open matte. I used to watch it on 3:2 TV with black paper used to physically crop to the right aspect ratio...
You don't need your router to handle DynDNS. You can run the DynDNS update client on the server.
And for inside your home network, you should probably be using Zeroconf. That's what I do. The servers and printers just advertise themselves using whatever IPv4 addresses they got from DHCP, and whatever IPv6 addresses they autoconfigured themselves with.
PS3 finds the media server automatically. Laptop finds the printer automatically. SSH to any machine by name. And no DNS entries to maintain.
Yeah, I'm quietly hoping that this'll be the graphical package manager that isn't half-assed or overcomplicated. The one that finally gets me to stop using apt-get at the comment line. The one that succeeds where three or four others have failed.
I'm also hoping that the current Linux sound infrastructure will some day be the one that actually works reliably. Again, the one that succeeds where three or four others have failed.
I can agree with this part. Practically the sole reason I'm fearing the change is that I'll no longer be able to set up devices and connections easily. As it stands right now, I take one look at an IPv6 address, and it's enough to make me blanch and think "Holy hellbore, how am I going to remember that monstrosity of an address??".
Why the hell would you want to? We have this thing called DNS. I don't even memorize IP addresses on my home network.
What keeps me from doing IPv6 tunneling is an utter lack of clarity on the migration path from there. When my ISP finally does give me a 16-bit subnet in the v6 address space, I expect that I will have to go through all of that configuration again from the start and also end up spending days debugging the tiny bits of the tunneling configuration and software that didn't come out cleanly.
RFC 3068 is ten years old, so assuming your router is not more than ten years obsolete setting up IPv6 should be practically automatic.
I enabled tunneling by clicking a button then selecting two drop-downs to pick 6to4 (RFC 3068) tunneling. When my ISP starts offering native IPv6, I'll deselect tunneling.
If it's more complicated than that, you ought to be asking yourself why you're using such awful router software.
Also don't think about how many people take H.264 MPEG-4, and shove it in an MKV container, when if they used the standard MPEG-4 container it would be playable on far more devices.
(I can see an argument for MKV if your payload isn't patent-encumbered, but for MPEG-4? Puhleeze.)
Slashdot Mirror
Yes, there’s nothing funny about Uranus. Let’s forget the childish humor and take a serious, scholarly look at Uranus. To many people it’s just a giant cloud of gas where the sun doesn’t shine, but those of us who are enthusiastic about Uranus know that it has many secrets.
Surprising as it may seem, we don’t have all that many photographs of Uranus. Yes, the Pioneers sent back pictures of Uranus, lots of them. But there are very few images that are high enough resolution and quality to show the faint rings around Uranus. Perhaps the excitement around Project Icarus will give us the excuse we need to take another long, hard look at Uranus.
Even if you have no idea how to find Uranus, you can still appreciate its unusual configuration. Scientists still don’t understand why Uranus is tilted sideways. Also, while we know what’s near the surface, we still aren’t sure of the exact chemical mixture deep inside Uranus. Are the moons stable, or are they spiraling into Uranus?
With so much to learn, we must hope that NASA will probe the depths of Uranus soon. Yes, there are many technical issues that will need to be resolved, and problems to be faced—but we put men on the moon, and I’m sure that given sufficient motivation, NASA’s engineers can lick Uranus too.
IBM picked Microsoft. Some suggest that it may be something to do with IBM CEO John Opel being friends with Bill Gates' mother from their work on the same United Way board.
(Opinions mine, not IBM's.)
My local firewall and router have admin interfaces that require a dotted-quad entry in the URL bar.
What, you can't bookmark them?
The day Chrome has true support for NoScript, I'll switch back. Never before.
Chrome has the equivalent of NoScript built in. If a site tries to run scripts, you get an icon to the right of the URL bar. Clicking on that gives you a drop-down to let you enable scripts for that site.
Gah, what is with Mozilla following Google's every example, no matter how stupid or not?
Actually, they only follow the stupid examples. The good things, like per-domain script permissions, they refuse to implement.
The Internet *is* running IPv6 though. There are numerous IPv6-only web sites.
Would it be reasonable if a router was incompatible with YouTube? I mean, it doesn't specifically say that that particular web site is supported, right?
I use IP addresses to demonstrate whether or not DNS is the cause of a failure. But when I do so, they are right there on the screen available to copy and paste. And it's something I do very infrequently.
Won't work everywhere. In the UK there's a concept of a product being fit for use, for example. Regardless of whether something is stated on the box, if it's functionality a reasonable person would expect (e.g. a 2011 router having full compatibility with the 2011 Internet), you can return the product for a full refund if it doesn't have it. The US similarly has the concept of fit for purpose. Are these routers being sold with a license agreement that says "We do not warrant that you will be able to use this product to connect to the Internet"? I rather doubt it, and even if they are I rather doubt that a judge would uphold that agreement. I guess it's possible, though. We'll see if Apple manages to wriggle out of the class action lawsuit against it for selling phones that can't make a phone call if you're holding them in your left hand.
And DNS never ever fails for you?
Nope, can't say it does except extremely rarely. And if it does, the solution is to fix it, not to use bare IP addresses which will break when the services move to a different address.
Right now reverse lookup is less than 100% correct on my work LAN. But that should never ever happen so I must be hallucinating.
Hey, if I had incompetent morons run my networks I could get IP addresses to fail too.
By your definition, there are a lot of consumer routers being sold *right now* that are "ten years obsolete" right out of the box.
Yup. And I hope that there are some big class action lawsuits against vendors who fail to provide firmware updates for them in the very near future.
Letterboxing on VHS! Waste 2/3rds of your precious resolution on black bars. I can kind of see why that was unpopular on small televisions.
I always preferred losing resolution over losing big chunks of the actual movie.
Apple Airport Extreme. Well, actually a Time Capsule, which is basically an Airport Extreme with a big hard disk. I've been IPv6-ready for over two years now. Here's what I wrote about the process, with screenshots at the bottom.
On one hand, you chastise people for being a consumer, and give scatological examples like gas guzzling cars, and commercial airline flights.
Scatalogical? I know there are poop-powered cars, but I didn't know there were airlines powering planes with poop.
And Kubrick also apparently hated letterboxing? I think he was wrong on that, personally. The Shining really suffers when it's open matte. I used to watch it on 3:2 TV with black paper used to physically crop to the right aspect ratio...
You don't need your router to handle DynDNS. You can run the DynDNS update client on the server.
And for inside your home network, you should probably be using Zeroconf. That's what I do. The servers and printers just advertise themselves using whatever IPv4 addresses they got from DHCP, and whatever IPv6 addresses they autoconfigured themselves with.
PS3 finds the media server automatically. Laptop finds the printer automatically. SSH to any machine by name. And no DNS entries to maintain.
Yeah, I'm quietly hoping that this'll be the graphical package manager that isn't half-assed or overcomplicated. The one that finally gets me to stop using apt-get at the comment line. The one that succeeds where three or four others have failed.
I'm also hoping that the current Linux sound infrastructure will some day be the one that actually works reliably. Again, the one that succeeds where three or four others have failed.
Also, to all those who tout DNS as the savior for remembering complex IP(v6) addresses, consider this, router & firewall rules don't use DNS
So fix them.
logs record IPs not names,
Only for speed reasons. Look at software like analog, it resolves the hostnames when you do the reporting.
and when you roll out large amounts of servers or workstations and have to enter in the IPs manually, who wants to enter in a 128-bit hex address?
Read about stateless autoconfiguration. You don't have to enter IPv6 IP addresses into servers and workstations when you roll them out.
I can agree with this part. Practically the sole reason I'm fearing the change is that I'll no longer be able to set up devices and connections easily. As it stands right now, I take one look at an IPv6 address, and it's enough to make me blanch and think "Holy hellbore, how am I going to remember that monstrosity of an address??".
Why the hell would you want to? We have this thing called DNS. I don't even memorize IP addresses on my home network.
What keeps me from doing IPv6 tunneling is an utter lack of clarity on the migration path from there. When my ISP finally does give me a 16-bit subnet in the v6 address space, I expect that I will have to go through all of that configuration again from the start and also end up spending days debugging the tiny bits of the tunneling configuration and software that didn't come out cleanly.
RFC 3068 is ten years old, so assuming your router is not more than ten years obsolete setting up IPv6 should be practically automatic.
I enabled tunneling by clicking a button then selecting two drop-downs to pick 6to4 (RFC 3068) tunneling. When my ISP starts offering native IPv6, I'll deselect tunneling.
If it's more complicated than that, you ought to be asking yourself why you're using such awful router software.
Actually, things are moving in the right direction. Apple, Google, AOL and Facebook are all using XMPP. Yahoo and MSN are the two big holdouts.
Also don't think about how many people take H.264 MPEG-4, and shove it in an MKV container, when if they used the standard MPEG-4 container it would be playable on far more devices.
(I can see an argument for MKV if your payload isn't patent-encumbered, but for MPEG-4? Puhleeze.)
Same reason people use a crappy open format (MKV) to store patent-encumbered encoded data (MPEG-4 H.264, AC3, MP3 and AAC).
That is, they're idiots.
You don't rate the patent lawsuits against Android devices and attempts to extort B&N to use Windows for the Nook as evil then?
Only if you already have it set up. My PS3 died, and I bought a new one, but Netflix on the new one won't let me activate it until PSN comes back up.
NO they are not because they are NOT engineers.
Moron.
Software Engineering is a stupid title for stupid people to bolster their stupid little egos.
A friend of mine is a Chartered Engineer and software engineer.
Maybe you should take a look at that chip on your shoulder.