Sorry I got the blocks sizes wrogn in that last post, 6to4 is 2002::/16 teredo is 2001::/32

There are three types of IPv6 address you may see on a windows 7 machine on a network that does not provide native IPv6

1: a link local address (from the block fe80::/64), afaict you will always get this but as the name suggests it's only usable on the local link.
2: a 6to4 address (from the block 2002::/8), you will get this if you have a public IPv4 address and either no firewall or one that lets through the 6to4 packrs
3: a teredo address (from the block 2001::/16) , teredo is a nat traversing automatic tunneling system, it's enabled by default for home user machines but it's supposed to be disabled by default on corporate networks (defined as networks continaing a domain controller)

Both 6to4 and teredo should in theory allow communication with hosts on the ipv6 internet but in practice they can be somewhat flaky and said communication with the ipv6 internet largely reliant on relay servers run by a handful of altruistic providers.

A quick googling found

http://www.clarisonus.com/Rese...

It seems to vary but even if the filtering is present there is likely to be a range just above 20KHz where human hearing is poor but the filters in the soundcard are still passing enough signal to be useful.

Simple analog filters (that you coudl build with 10 cents worth of components) have a slow rolloff. You can't just say "pass everything up to 20KHz, reject everything above that" or even "pass everything up to 15KHZ reject everything over 25KHz" and design a simple analog circuit to do it.

This is one of the big reasons we use high sample rates and filter digitally nowadays. You can get arbiterally close to an ideal "brick wall" filter digitally (though you do pay a price in time delay and computing power) whereas in the analog world high order filters tend to have problems with stability and sensitivity to component tolerance.

That's hardly surprising, using a tunnel hides all hops between you and the tunnel gateway from traceroute and similar tools.

Think about it for a minuite, if they have allocated the addresses to you they can use it to "justify" requests for further allocations. Even when buying used IP addresses you still have to justify your use of the IPs to get them registered to you.

They can then reclaim those addresses from you (and other similar customers) when the shortage gets so acute that they really need them.

OOI who is the provider?

The problem is that the humans who built many systems didn't just use their "human representation of time" as a display format. They used it as an entry format, a storage format, a calculation format, a transfer format.

Humans are good at making educated guesses, computers not so much so you have to go through ALL your code checking it is making the assumptions you want it to make. Further if you bake in an assumption like =nn means 20xx you are just postponing the problem.

Yes and no, we have certainly built systems that can handle dates beyond 2038

but afaict while the linux developers have noted that it is a problem for 32-bit linux they have not yet done the work to fix it and to be done sanely this work really needs to start from the bottom of the stack. There isn't much app developers can meaningfully and sanely do when their OS is broken.

Given that the problem hasn't been solved for many new systems being deployed now I can't share your optimism that systems with the problem will be phased out by 2038 and I would expect a lot of emergency patching.

Yeah it's nothing new to put such emulation in place, apple did it twice when they switched to powerpc and when they switched to intel. DEC did it for windows NT on alpha. Intel did it for windows and linux on itanium (the itanium originally had hardware x86 support but it sucked so much that software emulation was faster and it was removed in later versions). qemu can do it for linux binaries across a wide range of cpu architecture combinations.

It's doable but there is a significant performance penalty. Thats tolerable if your new CPU is significantly better than your old one/competitors one but if your new chip is only slightly better than your old one or your competitors one then it's going to suck badly.

They also recently bought the SSD part of OCZ which had a reputation for being one of the shittiest SSD makers around. I'd want to hold off for a while to see if they can turn that around before buying their SSDs.

Also apparently their marketing was terrible, so they didn't reach out to the people who could benefit from their service and afford the price.

I would note that while the original irridium company did fail the new irridium company is managing to find enough money from it's subscribers to fund satellite renewal.

iirc they tried a few different methods over the years, IIRC they tried transmitting programs in the computers native tape format and they also tried using a special tape format that was designed to be used on multiple different computers (with a special loader program) and to be more tolerant of poor tranmission conditions. I think they may have tried program distribution over teletext at one point too but few people had a teletext decoder hooked up to their computer.

The trick is to use a phased array, the individual antennas in the array have relatively low gain (and are hence physically small) on their own, however by driving them as an array you can create highly directional beams and you can do it in many directions and it turns out you can do the same thing for receive by doing weighted sums of the inputs.

The handheld end is more problematic, the directionality of an antenna is highly dependent on size and there isn't much you can do about that. There is also the problem that if it's too directional you have to aim it at the sattelite (either physically or electronically)

handheld phone to geostationary orbit has been done with a phased array on the sattelite.

It takes just over 100ms to send a signal to geostationary orbit for your round trip time you have to multiply that by four (client-sattelite-server-sattelite-client) giving a minimum theoretical ping time of just under 500ms.

Lower orbits should do better and it should certainly be possible to bring the latency down to a level where it is comparable to the latency experianced when browsing an australian website from europe.

If you are seeing two seconds of latency from your sattelite provider there is some other factor at play besides the raw radio latency to/from orbit.

It's also in the ultimate edition.

The other problem is it breeds resentment among the white able bodied males who are discriminated against by the quota systems. It also breeds resentment amongst the companies own staff who may feel they are being forced to hire unqualified staff to meet quota.