I just got an email notification and while I can understand that they're doing this (all those GB must add up to a significant cost), the relatively short notice seems unnecessary.
Even having a publisher doesn't address the underlying issue: There are simply too many 'indie' games. Relatively simple high-concept low-fidelity retro games don't have a huge audience and that audience is getting swamped with a torrent of games of varying quality.
But what percentage of systems is actually ONLY implementable using a block-chain-based cryptocurrency?
I love decentralisation as much as the next guy but it's not a feature. Apart from the obvious authority-circumvention (both positive and negative), what killer features do these systems have?
All the interesting projects I've seen for ethereum rely on Intel SGX to bring ground truth about the real world onto the chain.
Clicking yes might not even be necessary: I recently went to a laywer-oriented event (IANAL) that discussed the GDPR and it had a cheerful talk about "Alternatives to Consent"
The talk listed all the possible ways the law allows you to store/manipulate user data without requiring explicit consent... There are a shocking number and iirc they apply basically whenever you have a direct consumer relationship with some company.
It's sobering to think about how easy it must be (for a sufficiently funded organisation) to effectively determine "public discourse" on a large number of topics.
Then again, never underestimate just how willing people are (all on their own) to grab their virtual pitchforks without much consideration.
I'm sorry to say this but your country uses an outdated, deprecated implementation of Democracy. While we respect it greatly for its historical value as one of the first stable implementations, it is no longer recommended for production environments due to its many known critical bugs, most famously the first-past-the-post issue in its election algorithm.
Instead we'd recommend one of the European-republic forks (E.g. Germany's federalism 2.0) or, if you're feeling adventurous, one of the smaller forks like 'Direct Democracy' or the nordic-style forks.
Please note that those newer implementations have significantly higher system requirements, usually calling for a well educated population that is willing to debate and compromise rationally.
That's a great idea! Not only does it just 'feel right', it also prevents some of the legal mess people were seeing with effectively moonlighting for the hiring company.
As a minor, your parents decided for you, but once you're 18 nothing is stopping you from either trying to re-negotiate the contract (i.e. become politically active) or trying to find a better deal (emigrate). You can also decide to simply unilaterally break the contract (become a criminal) and in practice you could even live without such a contract in a variety of vast areas that are largely uninhabited.
You're not being compelled to accept this contract, but it's such a good deal that few people decide otherwise.
What's the point behind Gulden, though? Why do I need a cryptocurrency for anything they're doing? Do they allow anonymous gulden -> IBAN transfers? If yes, that'd be a unique feature but also one that has obvious potential for misuse and might not go down well with financial institutions and regulators.
That's a great concept: The fact that a list of {name, email, mobilephone number} allows you to effectively re-create your own network wherever you want is pretty cool.
I read the open/closed in the article as less about that and more about the fact that e.g. I can't push a twitter post to Facebook without Facebook specifically putting that function into Facebook. I also can't combine the comment streams from Twitter and Facebook. That's the kind of openness that I thought the article was referencing.
I know you're just using it as an off-hand metaphor but fire is actually one of the most useful tools in preventing and fighting large fires (e.g. forest fires).
Short answer: They didn't survive. IIRC a significant portion of all humans born in past centuries simply died as infants/children, usually from things that are trivially preventable today with basic hygiene, good nutrition and antibiotics/vaccines.
Humanity as a species obviously survived because people simply had a lot of children to compensate the high mortality rates.
I think the long tail isn't an issue. We'll probably have dual stack equipment for the next few decades. What matters is getting the large websites on IPv6 so that people browsing on mobile (usually NAT64) or developing nations (usual CGNAT) can get a non-sucky web experience.
Heck, if all the sites on that page where green, mobile Internet would suddenly be a lot better since the carrier NAT boxes would have to deal with ~90% less traffic.
The big issue here are AWS/azure dragging their heels (and I assume some CDNs, too)
It makes sense that Google would be fully IPv6 enabled, after all they are the mobile-first company and IPv6 can make mobile connection experiences a lot better, especially during peak network usage times.
NAT. If your server is only available via IPv4 then the client (user) needs an IPv4 address. Sadly there are so few IPv4 addresses that virtually everybody has to share with at least some people/devices and go through NAT (your home/office router, or for countries where ISPs don't have large ip blocks, some large NAT style router at your ISP). NAT is a horrible hack and causes all sorts of issues (port forwarding being the most common issue).
If you make your server available on IPv6, too, then I can use my non-shared IPv6 address to communicate with you which means that the packets don't need to undergo NAT which means a less horrible, faster connection without messy port forwarding requirements.