HN user

kazen44

1,886 karma
Posts0
Comments994
View on HN
No posts found.

a combination of many things.

For one, Cities in the netherlands are already quite dense, and the dutch are focused on building family houses attachted to each other mostly (row housing).

Also, thanks to the massive agricultural sector and a lack of oversight on industry, the netherlands has a massive problem with nitrogen in its soil which prevents building because building stuff generates more nitrogen.

Speculation and the liberalisation of the housing market has also massively contributed to price increases.

https://en.wikipedia.org/wiki/Nitrogen_crisis_in_the_Netherl...

this is still kind of possible, by doing neighbour discovery and querying the host for its hostname with mdns.

In my opinion, this automatic mapping of DNS names to addresess is not part of the IP protocol, and shouldn't be.

SLAAC is probably one of the better improvements of IPV6. DHCP breaks down at scale. Managing many DHCP prefixes becomes a massibe pain, SLAAC is far more scalable, far more easy to make redundant if you have redundant gateway's and protocol wise is really simple.

arp simply breaks down in very large networks aswell.

Think about things like the following: you are a datacenter and are providing connectivity to the internet for your customers. Each customer get a vlan with a specific ip prefix attached to it. You prove the gateway for each customers subnet.

ARP crosses the L2 vs L3 boundary to do succesful address resolution. The problem this creates in large (mainly datacenter) networks is that a router needs to do arp resolution for for a LOT of networks. (i am talking about 100's of networks in past, many thousands with something like an EVPN vxlan).

Why is this a problem? Layer 2 lookups are usually done in the forwarding plane, and ARP resolution is usually a routing engine task. Doing it this way is very expensive compared to the IPV6 way of doing things. (multicast based address resolution).

The router only needs to send out one multicast packet per vlan, instead of doing arp resolution for each specific host in the vlan.

In modern datacenters this is "fixed" by doing arp suppression, which is a whole other level of hackary added on top of it.

also, the knowledge about how a nuclear bomb works wasn't a secret. The way to produce one was the hard part to figure out. Without the espionage, a industrialised country like the USSR would have figured out how to produce an atomic bomb eventually.

can't decide how to tackle illegal mass migration

the mass migration caused by american wars in the middle east you mean? Also, frontex seems to be working fine so far.

on a single direction on defeating Russia

unlike the US, which has stopped all military aid to ukraine in 2025, and seems to be favouring russia more and more.

Lets not forget, europe is increasing its military en masse mainly because on one hand you have the russian flattening ukraine, and on other hand you have the US demanding greenland.

Who needs further enemies with friends like this?

what are you on about? this idea of a referendum is a straw man. Member states joined the EU through mechanisms of their state. (Acts of parlements, referendum or something else).

Also, the votes you are described are all about the implementation of certain ideas/legislation inside the context of the EU, not about the organisation itself?

it is also a very easy pathway to create controlled opposition. When you are a totalitarian dictator without elections, opposition of any kind is hard to control. With faux elections you give people a "choice" which seems reasonable compared the usual extremes in an totalitarian state.

Secondly, we employ "adversarial" systems for two branches of government (legislative and judicial) because it's a hell of a lot easier to spot flaws in ideas of people you are opposed to (as opposed to some European Judiciaries that have "inquisitorial" systems, where a judge investigates activity).

if that would be the case, why is the adversarial system not working in its current practice?

Also, i think the difference between the judicial systems of parlementary/european and the american system have more to do with the difference between civil and common law.

European goverments are really the legacy of the revolutionary french idea's of a civic state, in which citizens have duties to the state, and have rights being garantueed by the state. The state itself is being granted the authority to do this by its citizens through some process.

multi-site k8s is also very "interesting" if you encounter anything like variable latency in your network paths. etcd is definitly not designed for use across large distances. (more then a 10km single mode fiber path).

splitting things out in a smaller prefix then a /64 breaks a couple of things. SLAAC will not work, and slaac is actually a really neat usecase for containers. Not having the overhead of DHCP for container addressing is neat. Also, smaller blocks then /64 makes things like prefix delegation (usually) also break from a provider.

alright, what you are proposing is kind of hard to do. Source routing is not easy, and source validations is even harder.

and what prevents me, as a abuse hoster or "bad guy" from just announcing my own IP space directly on a transit or IXP?

You might say, the IXP should do source checking aswell, but what if ipspace is distributed/anycasted across multiple ASN's/ on the IXP?

Also, if you add multiple egress points distributed across different routing domains, it gets complicated fast.

Does my transit upstream need to do source validation of my IP space? What about their upstream? Also, how would he know which IPspace belongs to which ASN's considering the allocation of ASN numbers and IP space is distributed across different organisations across the globe. (some of which are more malicious/non function than others[0]). Source routing becomes extremly complex because there is no single, universal mapping between IP space and ASN's they belong too.

[0]https://afrinic.net/notice-for-termination-of-the-receiversh...

its a shame DANE never took off. If we actually got around to running a trusted DNSSEC based DNS system and allowed clients to create certificates thanks to DANE, we would be in a far more resilient setup compared to what we are now.

But DNSSEC was hard according to some, and now we are running a massive SPOF in terms of TLS certificates.

i also find the sentiment of "well we use a third party so blame them" completely baffeling.

if you run anything even remotely mission critical, not having a plan B which is executable and of which you are in control (and a plan C) will make you look completely incompetent.

There are very, very few events which some people who run mission critical systems accept as force majeur. Most of those are of the scale "national emergency" or worse.

also, the availability of the routing and switching infrastructure of the internet must be atleast a factor higher then that of the world wide web.

Physical network equipment is redundant and reliant enough that getting 5 minutes of downtime or less per year is totally doable.

the web however... is a far different beast (and in my opinion, with an incentive which does not factor in reliability)

congo is also a classical example of the resource curse.

Congo is so resource rich, that the state can sustain itself easily with simple, low skilled extraction of resources, without the need to invest in its populace to increase economic output through other, more difficult means.