Very well said, and I'd like to extend the idea much further: Old reddit, Windows debloater, youtube adblock, ... There are plenty of services that turned into customer disrespect, but people do huge efforts to keep them a bit less abusive. Huge kudos to these people, but isn't it time to just let the bad businesses die? If the power users are just as unhappy as everyone else, the exoduses start much faster.
Nobody needs social media of any sort. Everyone should just turn it off and stop making excuses for yourselves to stay addicted. That said, it's easier said than done. Trust me, I know.
I'm not sure I would class Youtube as social media. It can be, but some people just watch it on their TV's and never engage in a social way at all.
We do, just not social media for the sake of extracting maximum ad revenue out of users. We're a widespread society we need large online spaces, but not ones algorithmically designed to addict and derrange users.
I'm really just here because Google is shit and there are only so many alternative ways to find an aggregation of links to potentially interesting tech articles. I'm hoping to find new blogs or sites to follow, in part so I can stop coming here.
I might give up on it soon though, like I've given up on reddit. Too many junk article lately.
As for my commenting, that's because I, like everyone else here, am a bit of an idiot. HN makes it easy enough to comment that it's hard to resist sometimes.
I'd say: Shortages after the world wars, combined with the teething problems of new technology made customers acutely aware and capable of repairability. That lesson is now forgotten.
It also wasn't universally true. E.g. the story of Mad Munz creating TVs that worked only for 90% of the customers (who had good enough reception and needed less signal cleanup). His idea was to capture 90% of the market with a cheaper product, while shafting 10% of the consumers and shamelessly send them to other vendors when they reported their troubles and he already had their money.
80186 Was not IBM PC compatible. It had e.g. a PIC, DMA and timer built-in, and these were incompatible with the chips in a 8086 based IBM PC.
There were a few new instructions, too, mostly closing holes. You could left or right shift with a constant, while the 8086 had only 1 or the CX register. I think mul also gained a constant.
The fact that Intel released a CPU that could not be put in a PC probably indicates how low they estimated the survivability of the PC.
Around here, public toilets have roll holders containing 2 rolls. 2nd is unreachable, but when the 1st is empty, it falls out and 2nd drops in its place. Janitors just fill the 2nd roll if missing.
I am hoping this is normal around the world and nobody throws away slightly used rolls.
The king is already mostly ceremonial. He seems mainly a stabilization factor for the country when both halves get a bout of separatism once more: He is the ultimate person every major politician talks to when nobody wants to talk to each other. The king does have some extra rights, but not too much, and the alternative seems worse.
King Albert 2 didn't want to become king but nobody else with enough capability was available. So it's not just a fun job.
But yes, the discussion to king or not pops up once in a while, and the general response seems to be we got much bigger problems.
It's German, not British. When Belgium was founded, the fear was it would immediately try to join France. So when a French noble was offered the throne, he actually said no, quite a blemish for the young nation. A surplus German noble was crowned, which was palatable to the English as it balanced things out a bit.
"The British branch was officially renamed to House of Windsor by British king George V in 1917, during the First World War, amid anti-German sentiment."
I'm not a drawing person. I wish I could draw a lot better. I used to try once in a while, and the results were universally bad.
So a few years ago, I took a drawing course, and pushed it as fas as I could. The results were the best I ever did in my life, and not terrible, but still far from good. At this point, I've decided this is as good as things will get, and I should stop spending effort and focus on other things that I am good in.
If I happen to find myself in a situation that requires me to draw, I will make a honest effort. Maybe something will happen that makes me grow. But I have decided that for the forseeable future I am not a drawing person and that's fine.
You have to read the news from someone, and each one has its own bias. State news has a well known failure mode as propaganda. But commercial news turns out to have its own failure mode, where emotion inducing content has bigger gains for lower cost.
The best advice I can give here is to mix different sources. As a Belgian, I have a few local newspapers and the VRT news for Belgium, NOS, BBC, CNN, and Al Jazeera, which are all checked at least weekly. Each one has its own blatant biases and blind spots. There are still big missing gaps, e.g. a Chinese and an African perspective. There is clearly Gell Mann Amnesia going on. Even so, I started to look very different to the world.
The government invented intellectual property for a reason, and in this context it isn't serving it's puprose. It's not some natural law or inalienable right, it's a government monopoly that trades public rights for scientific progress.
The reason of copyright has always been to protect the current powers. To promote usefull arts has always been a whitewash. Here's e.g. wikipedia on that topic:
Doing this brings you close to OSI, which famously failed by being overcomplicated. The current design was implementable by zillions of cheap humans running cheap hardware.
I always wonder if the internet is thesurvivor of the networking cambrian explosion, with a slight roll of the dice making another candidate the winner.
As someone who was there at the time, OSI certainly didn't fail by being "overcomplicated". It failed because a) they charged money to read the standards documents and b) TCP/IP already had so much deployment momentum that nothing was going to supplant it (we see proof of this in the fact that IPv6 also didn't achieve that). Edit: also c) there was no requirement (unlike RFCs) to have an interoperable reference implementation available. So the implementations that were created mostly didn't interoperate.
This IPv8 document is not a serious proposal. The entire family of documents was published by a single person without collaboration from anyone else at IETF, and there has not been any work to integrate feedback from other IERF contributors (last I was aware of).
Anyone can publish an IETF draft document, it doesn't mean it's a serious proposal under consideration or will ever actually be implemented.
> In your opinion, do you think Internet Protocol Version 8 (IPv8) [1] stands a chance to fix the mistakes of IPv6 after more than 20 years now?
IPv8 solves precisely zero of the problems that is causing a 'slow' roll out of IPv6 / replacement of IPv4:
"""
So it's a matter of mathematical and physical fact that to expand the address size, you must change the protocol, and that means two things immediately:
You have to change the version number.
You have to add new code to handle the new version.
Furthermore, you don't want to split the Internet in two, so you must design a method of interworking between the old version and the new version. Annoyingly, you need to do that in a way that can be done completely in machines that know about the new version, because other machines don't know anything at all about the new version, by definition. So,
You need a coexistence technique so that updated systems, with the new protocol, can connect to old systems that know nothing of the new protocol.
Two minutes of thought show that this third requirement has only two solutions:
(3A) Dual stack, in which the new machines speak both the old (IPv4) and new (IPng) protocol.
(3B) Translation, in which something translates addresses between the old and new protocols.
[…]
Incidentally, "IPv8" proponents often ask why IPv6 didn't simply stick some extra bits on the front of IPv4 addresses, instead of inventing a whole new format. Actually, we tried that: the "IPv4-Compatible IPv6 address" format was defined in [RFC3513] but deprecated by [RFC4291] because it turned out to be of no practical use for coexistence or transition. The related "IPv4-Mapped IPv6 address" format is still valid and has a role in the POSIX socket API. Mappings of this kind also figured in the moderately successful coexistence technologies known as 6to4 [RFC3056, RFC3068] and Teredo [RFC4380], which have now been overtaken by events.
I'm always fascinated by how many people think IPv6 adoption would have gone lightning-fast if we just used This One Weird Trick, where said trick has actually been tried and didn't help. They usually refuse to back down even after you tell them so.
6to4 or NAT64 isn't the same thing as what all those IPv4+/5/7/8 people want, if that's what you were referring to. You don't actually own the IPv4-mapped-V6 address, as in packets don't get routed to you, they go to a relay that was notoriously flaky.
> You don't actually own the IPv4-mapped-V6 address, as in packets don't get routed to you, they go to a relay that was notoriously flaky.
6to4 is exactly ownership:
> For any 32-bit global IPv4 address that is assigned to a host, a 48-bit 6to4 IPv6 prefix can be constructed for use by that host (and if applicable the network behind it) by appending the IPv4 address to 2002::/16.
> For example, the global IPv4 address 192.0.2.4 has the corresponding 6to4 prefix 2002:c000:0204::/48. This gives a prefix length of 48 bits, which leaves room for a 16-bit subnet field and 64 bit host addresses within the subnets.
> There's no way around it: a non-IPng-having node will have to go through a translation box of some kind.
Yes. Note that it doesn't need to be someone else's relay; anyone with IPv4 connectivity could easily route 2002::/16 into IPv4-land (without having to announce it in BGP for others to use). You could even announce 2002:aabb:ccdd::/48 as a more-specific in BGP if you wanted, although this was more exotic.
If I have 1.2.3.4 in ipv4 world, I want 1.2.3.4 in ipv6 world instead of a random new address. I want another ipv6 host to be able to send dst=1.2.3.4 and have it go directly to my ipv6 host. 6to4 isn't comparable to that, it's for translation to/from v4 like you said.
By having 1.2.3.4 you also got 2002:1.2.3.4::/48 'for free' (per 6to4). So if you want to send things to 1.2.3.4 / ::ffff:1.2.3.4, you tell your router that it's available via 2002:1.2.3.4::/48.
Any idea that you think is clever and to 'just' do X and/or Y for IPng, and would work, has probably already been thought of and attempted in the last 20-30.
Having 1.2.3.4 in v4 doesn't make ::ffff:1.2.3.4 or 2002:1.2.3.4 route to me in v6. It would route to a relay that translates/resends to v4 1.2.3.4, then it reaches my router over v4. Nobody can use that address over pure v6.
There's no one clever trick to make the transition easy, the idea is to preserve the v4 address blocks in v6. That cascades down to a bunch of different decisions, some of which include keeping NAT around. They've most likely thought of that too, and turned it down because they wanted to start with a clean slate and maybe also had some other vision of pure P2P apps.
> Having 1.2.3.4 in v4 doesn't make ::ffff:1.2.3.4 or 2002:1.2.3.4 route to me in v6. It would route to a relay that translates/resends to v4 1.2.3.4, then it reaches my router over v4. Nobody can use that address over pure v6.*
Sure they could: if your ISP owns 1.2.0.0/16, it could advertise 2002:1.2::/24 via BGP. So if someone on the other side of the planet wants to send something to 2002:1.2.3.4::/48 they would know where to send it.
And just like how something sent to 1.2.0.0/16 globally is then handled internally via IS-IS/OSPF/etc so your ISP knows how to send something for 1.2.3.4 to your CPE, your ISP would know how to handle 2002:1.2.3.4::/48 to get it to your CPE.
Routers are told to map traffic for (::ffff:)a.b.c.d to 2002:a.b.c.d::/48. If you're sending from w.x.y.z, you can put the source address as from something in 2002:w.x.y.z::/48.
It has nothing to do with "clean slate" or not. There are two immovable facts:
"""
IPv4 implementations, in 1994 and still today, have the 32-bit address format built into their code. Whether you expand the address size to 33, 64 or 128 bits, all IPv4 implementations will discard the packets. So it's a matter of mathematical and physical fact that to expand the address size, you must change the protocol, and that means two things immediately:
1. You have to change the version number.
2. You have to add new code to handle the new version.
And this also includes 'accessory protocols': DNS A records are fixed at 32-bits, so if you want to use hostname with IPng you needed to upgrade the DNS infrastructure, including APIs to say "give me A and Ang", and then you perhaps need fallback mechanisms, in which case you're at:
Any IPng protocol, including 'just' adding bits, regardless of how you want to hand wave it as being 'just' an extension of IPv4 will be in same situation because you can't fit >32-bits in the 32-bits of the original code. You're rolling out new code in a rolling fashion, just like had to be done with IPv6.
Well yeah if you made your router use 2002:1.2.3.4, your ISP advertised 2002:1.2:: on BGP, and the other ISPs agreed your ISP owns that, that would work. They didn't do that, and the spec didn't say to. They did 6to4 instead.
I understand the limitation that you can never put a 128-bit address in a 32-bit field, and one way or another two hosts and everything in between have to understand the new packet format. That didn't force them to make ipv6 its whole separate network from v4 where almost no state is shared with v4. Having separate DHCP6 vs DHCP4 was a choice, likewise with DNS, NAT, and even the routing tables. It makes the difference for service operators who would be fine adopting ipv6 but don't want it to be a big project.
> The current design was implementable by zillions of cheap humans running cheap hardware.
Yes and no. The current internet arguably does not work without a browser and a TLS stack anyway, neither of which is easily implementable (e.g. number of practically usable rendering engines is in the single digits). I mean, I can piece together an IP packet, too, but there's not that many usable services reachable that way.
> Doing this brings you close to OSI, which famously failed by being overcomplicated.
We're slowly reinventing OSI, one step at a time: OSI had multiple sessions per transport connection (QUIC), 20 byte addresses (IPv6) and a directory system with public-key infrastructure (DANE, vCard, SSHFP, etc).
