HN user

apk17

89 karma

http://github.com/apk/

Posts0
Comments96
View on HN
No posts found.

Partially. Telekom keeps up the line for months at a time. I guess that is due to telephony being done via VoIP, and they don't want to interrupt your late night calls.

Others, even Congstar (which is a cheap telekom brand), do 24h disconnects with a new v4 address, and no v6 at all.

The DSL I use gives me a fixed v4 and v6 range, but still needs to do the daily disconnects.

Theoretically, yes.

Practically, my laptop is in some Wifi network and has an IPv6 address, but that isn't accessible from the outside because the Wifi/router box blocks incoming connection. That is a wise decision overall, but unforunately replaces the "can't connect because NAT" by "glorious IPv6, bit still can't connect".

And I'm not the owner of those boxes.

How is that supposed to fly? When they look inside the VPN I'm just using, they'll see git-ssh traffic to a bitbucket server, and are none the wiser.

(And: Seriously, HN, recaptcha on the login dialog? Have you any idea how hard that is on tor users?)

Mobile carrier NAT, mobile device hotspot NAT, vmware NAT - that's the most I've seen so far.

But IPv6 in home networks replaces the unreachability-because-of-NAT by unreachability-because-of-filtering. The usual home router protects your clients, and if it's not your box, you're out of luck.

To think of it - I might have heard these two pass by. Not on that flight, but I lived with my parents in northern germany, not far from the danish border, and en route from the north to the baltic sea and on to russia. I often heard the badam, accompanied by a creak of the wooden roof.

Kleinwalsertag. Austrian territory, but only reachable (by road) through germany. Was connected to german phone network, which changed once telco stuff got smart enough. Effect: For some time a german and an austrian phone number reached the same phone.

I.e the 10% are not worthy of having an ISP, or health insurance.

As for the ISPs, this often isn't even about the customers being annoying, but simply their subscriber line being rotten or in an undocumented state which to sort out is too complicated for the tech-drones.

Definitely not 'expected'. I like the mailing list bug tracking more than having that on git{hub,lab,whatever}.

git makes it even possible to host a repo on multiple git* hostings, but apparently nobody came up with a successful distributed pullreq/issue tracker yet.

IHMO post-scarcity could have started long ago. The problem will be that the people out of a jobs can't think of something new to do, at least not as fast as the machines (or the people with the machines).

Subjugation already happens. When it's easier to keep the population poor and just raid the natural ressources of a country, that's the way it often goes.

It shifts the balance. Even if my hotline gets bombarded by mechanical turks the costs are the same on both sides.

Now google duplex can go and phone up every businessowner asking for the current store hours (or whatever), thus dumping the work of updating google's information on the store owners at essentially no own cost.

And the store owner does not even have a chance to find out whether it is a customer that will in some probability show up, or if he's just being used.

The network needs to know your location in real time in order to route calls to you.

At least for GSM, that isn't as true as you say it. It only needs to know in wich group of cells you are, as as re-registering with each cell change was deemed too heavy on the battery, and they rather page for your phone in the entire location area.

Likewise, triangulation requires the phone to send something, which means that you can notice that, and also that continuous triangulation will drain your battery.

(Which brings up the question of how often and how smartly google sends updates for the traffic density map.)

Fun story: A long time ago I was on the phone with someone, and typed some commands. For some reason tab completion made ticking noises in the phone.

Then it dawned on me: I was currently logged in on the machine on his desk.

Unified deployment with your non-go containers.

Also, port and volume mapping, so the container/go binary does not need to know physical/host pathnames to data files.

They routinely put fiber cables on high voltage lines, and apparently also on catenary masts along railway lines around here (germany).

Fibers are somewhat fragile, but not the complete cable. But the splicing necessary for local distribution will be hard to do on a mast top.

How would you know? Or at least, how would I know? If, back in the POTS day, the exchange went down half the night, I wouldn't have noticed.

Nowadays, you can look into your router logs. And Telekom had serious issues with their VoIP stuff.

Likewise, even the apparently planned outages at my previous location exceeded the 30 minutes. (It's still good, but not that good.)

Hours? Even back with locomotive-pulled trains where you actually had to shunt the cars to a different platform that should be below 15 minutes, and today, it adds less than three minutes to the train that is longer at the platform (Ohlsdorf, Hamburg rapid transit).

Provided that both trains arrive on time.

And doing in in flight is much harder (and not legally possible), but if you would want to join/separate in the outskirts to get one into town and the other on the bypass, just the stopping and reaccelerating will cost some minutes.

2. was done in britain a long time ago. They just uncoupled cars at the rear end and braked them down to intermediate stops; the rest of the train continues. (Ok, no bypass.)

Unfortunately the inverse operation isn't as easy, and it's an expensive operation, too.