It looks like a poorly thought-out marketing project. For example, how to deal with the Earth rotation irregularity and leap seconds? One beat is way too long to correct with, so the correction has to be in centibeats, fractions of beat, inconvenient. Why would this in CET and not in UTC? Aligning start of the day with the existing customs seems beneficial.
But the idea of the universal decimal time is a nice one. I wish we had something like that.
Dostoyevsky was originally published in magazines chapter by chapter, so he would end the December’s on a cliffhanger so that the readers re-subscribed
> Would you give your personal phone number to random strangers on the internet, or even publish it on a website? Probably not, due to the possibility of harassment, right? IP addresses aren't any different
1. The claim that IP addresses aren’t different from the phone numbers requires proof
2. Until very recently, just before the Covid pandemic people regularly exchanged physical business cards with their mobile phone numbers. So, yes, people do that.
> Realistically nobody outside some devoted HN readers are going to self host their own content.
P2P is not “self hosting”.
It’s video/audio conferencing working with less latency. It’s the ability to send a file directly and not via some file sharing site. It’s multiplayer gaming simplified. It’s faster software updates via BitTorrent.
NDP is not simpler than ARP. For one, NDP relies on link-local addresses to work which in turn relies on MAC multicast where ARP relies on MAC broadcast only.
Nothing prevents host from configuring a static link-local address, like fe80::1234. Not only that, some networks choose to have some standard link local address as a default gateway. For example, a router or a L3 switch can have fe80::1 on its downstream interfaces. This way, all hosts on all networks have fe80::1 as the default gateway and the router will have fe80::1 address on multiple interfaces.
Furthermore, you can (and some say, should) use link local addresses on transit links between your network devices, eg, between layers of switches in a hyperscale-sized data center network. Typically, the addresses will be deterministically configured, for example, consider
We have server1 connected to top-of-rack switch2 connected to aggregator switch1. Link between switch1 and switch2 is point-to-point transit. You can use exclusively link local addresses there. There are a few approaches:
- e2.48 gets fe80::2, e1.1 gets fe80::1 - all upstream ports are always fe80::2 in all network, all downstream ports are always fe80::1. A good thing is that link configuration is the same on all switches regardless of the Clos layer.
- switch1 serial number is 1001, switch2 serial number is 2002. Then, e2.48 gets fe80::2002, e1.1 gets fe80::1001. This way, all interfaces on a switch N have address fe80::N
You then can set up BGP session between the link local addresses and it either will always be either fe80::1 <-> fe80::2 or fe80::N <-> fe80::M. Switches also have a loopback address for ping, and other ICMP traffic. Either has advantages and disadvantages.
This is discussed in more details in RFC 6164, and a more high level overview is provided in RFC 7404.
In Signal, probably no. Signal has this sealed sender functionality hiding significant amount of metadata from passive observer and active examination post-communication: https://signal.org/blog/sealed-sender/
What Russian police would be able to see, that in a given time period of certificate rotation at most X people communicated to Navalny.
But the idea of the universal decimal time is a nice one. I wish we had something like that.