I'm a few years younger and I have found that now that I have a good career, good income and secure finances, I get a lot more attention from the female of our species.

I'm not married but I am in a relationship with the mother of my children. She was with me when I was working my way through college and living in my grandfather's spare bedroom so I know that she's here for me and not what I have.

I'd be extremely cautious about who I'd date if I were on the scene again.

LK

There are certain feminizing elements in our society who are trying to pathologize maleness.

Boys are more likely to be diagnosed with psychological issues and medicated for doing the kinds of things that little boys just do.

We have things like California's "yes means yes" law that criminalizes what's considered normal sexuality in the rest of the country.

Some guys are just checking out "Fuck this! I'll be over here with my video games and these porn chicks who won't make me just through a bunch of stupid hoops". They never planned to have children anyway so what's the point?

LK

You're naive.

That's the whole fucking point of F/LOSS operating systems. This kind of nonsense can just be removed.

What next? Another law criminalizing Operating Systems that lack this capability? How will you enforce that? How will you detect them?

Cody Wilson's objective is to illustrate the idiocy of people who think that utopia is "just" a few laws away.

You don't like what he's doing. That's fine, you don't have to but you can't stop it either.

LK

If his losses are repaid, then he has justice.

What he seeks is retribution.

There is a difference.

LK

Multiple IPs was one solution, but the other was much simpler.

The real address of the computer was its MAC, the prefix simply said how to get there. In the event of a failover, the client's computer would be notified the old prefix was now transitory and a new prefix was to be used for new connections.

At the last common router, the router would simply swap the transitory prefix for the new prefix. The packet would then go by the new path.

The server would multi-home for all prefixes it was assigned.

At both ends, the stack would handle all the detail, the applications never needed to know a thing. That's why nobody cared much about remembering IP addresses, because those weren't important except to the stack. You remembered the name and the address took care of itself.

One of the benefits was that this worked when switching ISPs. If you changed your provider, you could do so with no loss of connections and no loss of packets.

But the same was true of clients, as well. You could start a telnet session at home, move to a cyber cafe and finish up in a pub, all without breaking the connection, even if all three locations had different ISPs.

This would be great for students or staff at a university. And for the university. You don't need the network to be flat, you can remain on your Internet video session as your laptop leaps from access point to access point.

Google Answers.
Google Shopping.
Goog-411.
Google Buzz.
Google Wave.
Google Video.
iGoogle.

I don't trust Google to keep it around once it's no longer in Google's best interests to do so and since social networking isn't Google's focus or primary source of revenue, I can't trust that.

It's not that I begrudge them the decision to do what's in their own best interests but I have that same decision to make and Google+ doesn't align with them.

LK

No condescending comments from Barack Obama about how the 80s called and wants their foreign policy back?

LK

I suspect they could have saved themselves a lot of coding by simply randomly linking to real startup web sites. It'd look no less ridiculous.

For the Osaka-Tokyo route, the Shinkansen made the difference between an overnight business trip or return the same day. That made it insanely popular. With the new train, you can not just make a set of meetings; you can do a full days work and still get back the same day (even more so for Nagoya of course).

Many people here get stationed at offices in other cities for months or years, and leave their families behind. They effectively do a weekly commute, and come home only on weekends. For a lot of people this would let them get home more often or even stay home and make this a daily commute. Expensive, but on the other hand the company doesn't have to pay for a second short-term apartment and the other costs of two households.

Windows has had IPv6 stacks since Windows 95 and Microsoft even started supplying them as of 98.

IPSec is perfectly usable.

Telebit demonstrated transparent routing (ie: total invisibility of internal networks without loss of connectivity) in 1996.

IPv6 has a vastly simpler header, which means a vastly simpler stack. This means fewer defects, greater robustness and easier testing. It also means a much smaller stack, lower latency and fewer corner cases.

IPv6 is secure by design. IPv4 isn't secure and there is nothing you can design to make it so.

IPv6 would help both enormously. Lower latency on routing means faster responses.

IP Mobility means users can move between ISPs without posts breaking, losing responses to queries, losing hangout or other chat service connections, or having to continually re-authenticate.

Autoconfiguration means both can add servers just by switching the new machines on.

Because IPv4 has no native security, it's vulnerable to a much wider range of attacks and there's nothing the vendors can do about them.

Each level is given the parent's prefix plus one or two bytes. Yes, you can announce that and it is easily summarized.

Anycast tells you what services are on what IP. There are other service discovery protocols, but anycast was designed specifically for IPv6 bootstrapping. It's very simple. Multicast out a request for who runs a service, the machine with the service unicasts back that it does.

Dynamic DNS lets you tell the DNS server who lives at what IP.

IPv6 used to have other features - being able to move from one network to another without dropping a connection (and sometimes without dropping a packet), for example. Extended headers were actually used to add features to the protocol on-the-fly. Packet fragmentation was eliminated by having per-connection MTUs. All routing was hierarchical, requiring routers to examine at most three bytes. Encryption was mandated, ad-hoc unless otherwise specified. Between the ISPs, the NAT-is-all-you-need lobbyists and the NSA, most of the neat stuff got ripped out.

IPv6 still does far, far more than just add addresses and simplify routing (reducing latency and reducing the memory requirements of routers), but it has been watered down repeatedly by people with an active interest in everyone else being able to do less than them.

I say roll back the protocol definition to where the neat stuff existed and let the security agencies stew.

These are well-established, well-tested, well-designed protocols with no suspect commercial interests involved. QUIC solves nothing that hasn't already been solved.

If pseudo-open proprietary standards are de-rigour, then adopt the Scheduled Transfer Protocol and Delay Tolerant Protocol. Hell, bring back TUBA, SKIP and any other obscure protocol nobody is likely to use. It's not like anyone cares any more.