Slashdot was never good

Personally I can't understand why it's ok to negligently allow birds to hunt billions of insects and earthworms, but apparently society is fine with that.

You'd only need a super high fps device that detects on/off state of the light, which I guess would be a lot easier and cheaper than a real camera.

Forget CPU and GPU already. The mining difficulty has risen so much recently that what you can mine with them today won't event offset the power costs.

ASICs are the only viable option today for at-home mining, but I'm pretty sure they'll also be rendered useless soon by hosted mining services (CEX.IO already has 25% of the whole Bitcoin network mining power) that are able to consolidate costs and run their mining farms in countries with cheap electricity.

Fact:

97.3% of statements starting with "Fact:" are actually repeated talking points supported by absolutely no real fact.

Don't mix up addressing and computing.

The whole internet would fit in a 64 bit address space, there is really absolutely no need at all for more than 64 bit for addresses in CPUs, that's why x86_64 and other 64 bit archs are here to stay, and you'll probably never see "128 bit" processors at all.

On the other side, today's x86_64 CPUs are capable of 128 bit (SSE) and 256 bit (AVX) computing. The width of the compute units is also bound to increase for some time, with Intel already planning to go 1024 bit in the not-so-far future.

Apparently not today.

Checking for AAAA DNS record
no AAAA record

i686 because I don't see a reason to run x86_64 on 2GB of RAM

x86_64 IA would provide a noticeable performance improvement for some apps, even if you had 640Kb of RAM. It's not only 64-bit addressing but also 64-bit registers (and more of them), 64-bit ALUs, an so on ...

The vector unit must be FMA capable just like Larrabee, hence the doubling of FLOPS/cycle.

Mpath-tools is a set of programs for linux 2.6+ that aim to facilitate load balancing and failover over multiple and heterogeneous ISP connections.

4.0 was NT4 ... my guess is 95/OSR2/98 were all 3.2x

It was too computationally intensive for *realtime* rendering in 1973, but clearly not out of reach for the kind of modeling software NASA people were using ...

Also, it should be noted that realtime phong shading was already common in demos/intros running on 33 MHz 386 CPUs back in the 90s

IPv4 multi-homing can't be done without BGP, either. The requirements for Provider Independent address space in IPv6 are identical to the requirements for PI address space in IPv4.

I meant "cheap" multi-homing without a PI address block, like it's used in many small/medium offices where you have multiple ISP links and just failover by changing the SNAT mapping at the gateway when one goes down.

Doing this with ipv6 requires renumbering the whole internal network each time you switch links, or the more costly alternative of getting your own PI block, which in turn isn't IMHO sustainable for the long term because everyone doing it would make the global BGP table grow an awful lot faster that it's already.

OK, so it seems you agree (with the Founders of the Internet) that end-to-end is a good thing. .... and now you say it's a bad thing. So is it a good thing or a bad thing then?

My personal opinion is that end-to-end is *generally* a good thing, but shouldn't be *enforced* because there always will be edge cases where it will conflict with privacy.

Er, what??

Do you mean to say that without NAT a firewall is not needed, or that a firewall doesn't impact reachability ?

With IPv6 I can use NAT if I want.

I'm all for freedom of choice, my problem actually is that you can't use ipv6 NAT even if you want. Not with Linux anyway.

If people want anonymity within their local network, then there will be a market for devices that do IPv6 address cloaking and you can buy one and use it to hide your addresses.

Exactly, you would have to pay for something you can achieve with one iptables command line on ipv4. See my point ?