jabiko

> V-dem, Bertelsmann, and EDI literally has scores for China.

I think you confuse being listed on those indices with being a democracy.

On V-dem China takes place 177 of 179, the Bertelsmann index categorized China as "hard-line autocracy" and EDI categorizes it as "authoritarian"

> China is a democracy

Regardless of which democracy index (https://en.wikipedia.org/wiki/Democracy_indices) you consult, they all disagree with that statement.

I'm not trying to defend DNSimple and their decision to not keep the legacy plan around for existing customers. Sure, that's a hostile move that seems the be designed to squeeze more revenue from their existing customer base. I'm just wondering why the author didn't at least try to explore that avenue.

I'm wondering what prevented the author from having the sales call and seeing what rates they are willing to offer. Best case they might even be better than the current rates.

I don't see how publicly shaming someone (and yes, this is how I interpret the intend of your question) for the act of thanking the author of a project is going to help anyone.

It is offered free of charge, so why should it be despicable to use it free of charge? Maybe they do actually donate to the project, contribute code, or support in other means.

For example this very post where they thank the author is probably a source of motivation and acknowledgement that might have a positive impact on the project. They could have refrained from doing this but instead they took the time to write a very enthusiastic comment.

> The reason it’s considered a “3-way” handshake is mostly latency relate

Its not latency related. Its because there 3 packets involved in completing the handshake.

> If the delay sending a packet between the client and server is k, there are 3 hops involved in establishing a connection so the time is 3k.

Also I think calling it "hops" is not correct. A hop occurs when a packet passes through a router.

> Confusingly, this has nothing to do with how many devices are involved.

In a TCP handshake there are only two devices involved (disregarding any middleboxes that meddle with the connection).

I'm not sure what radical changes you are referring to. There was a orthography reform in 1996 (with a transitional period until 2005). But other than that only minor changes occurred.

> Capital ß is a shit show, and it only confuses native speakers, because close to none of them have ever seen that glyph before.

I don't think it's particularly confusing, but it is a great addition. As of 2017 the rules allow both "SS" and "ẞ".

Moreover, the current version of DIN 5008 (Rules for Writing and Design in Text and Information Processing) actually recommends preferring "ẞ" over "SS".

Apparently its behind a flag because the feature is not completely ready yet. However I was unable to find what work is still needed for it to be considered ready: https://bugzilla.mozilla.org/show_bug.cgi?id=1106626#c18

Or add a signed timestamp to the URL after which it isn't valid anymore. So the URL can't be used without opening the actual comment on GitHub.

I worked on a project team implementing TR-Notruf 2.0¹ for a regional ISP. TR-Notruf is the technical specification for routing calls and signalling caller location information for emergency calls in Germany.

In that project I wrote the software that receives the call, matches the caller number to the customer record, encodes the customer location information in the metadata of the call, and (based on the location) routes the call to the local emergency services call center.

While the task was quite simple most of the complexity of the project was to make sure that this service was highly available since downtime could have a detrimental effect on the health of customers.

¹ https://www.bundesnetzagentur.de/DE/Fachthemen/Telekommunika...

Maybe I'm a bit to naive since I don't know the US banking system, but at least in the EU you just need to tell someone your IBAN and Name and they can transfer money to your account. Is it that much harder in the US?

This reminds me of the time I worked for a local telecommunications company and wrote software to interface with EWSD (Elektronisches Wählsystem Digital) switches. Honestly, working with telecommunications systems was the best time I had in my entire career.

I would have liked them going more into the details of the caching issue. It sounds like they think the cache library was responsible for the issue, but a more technical analysis of what exactly went wrong within that library would be great.

> Actually, how do people buy stuff in Germany?

Most of the options I observed are either PayPal, direct debit, Giropay, collect on delivery or credit card.

I absolutely prefer direct debit. Just enter your name and IBAN and you are done. No 3rd party websites, no fuzz.

If you look at Googles IPv6 statistics the latency seems to be lower with IPv6 in almost all countries: https://www.google.com/intl/de/ipv6/statistics.html#tab=per-...

Here is an interesting article by Airbus regarding the 90 degree nose wheel landings: https://safetyfirst.airbus.com/landing-with-nosewheels-at-90...

This is just speculation, but maybe there is a secondary rupture disk that vents the helium inside the room when the primary path (the exhaust to the outside) is blocked. And maybe that secondary rupture disk is too strong, so another random part of the helium containment fails, blowing up the machine and possibly injuring the patient. But please note again that this is pure speculation.

I didn't want to imply that its brand new or beta. Just that it is still being actively developed. For example the compacted topic support did get into GA in May 2023.

Since LinkedIn is using Kafka quite extensively, I'm wondering whether Azures poor support of Apache Kafka is at least partially responsible for this.

Azure is developing its own inhouse message broker that they call EventHubs. And while it is able to speak the Kafka protocol it has some weird limitations and quirks¹. I'm wondering why they are so hellbent on developing their own inferior version of something when they could just use the real deal and host it as SaaS.

¹ No support for KIP-71 (Enable log compaction and deletion to co-exist), limited to 10 topics (Azure lingo: EventHubs) per broker (Azure lingo: EventHubs namespace), mandatory client config parameters that you must not forget to set, even though the documentation just calls it "recommended" (https://learn.microsoft.com/en-us/azure/event-hubs/apache-ka...), some weird protocol level incompatibilities that are nowhere documented, for example a consumer group state transitions to "Dead" after the last consumer left instead of "Empty", and auto scaling that only ever scales up, but never down.

I'm wondering how your two quotes "security of our customers is of the utmost importance to us" and "we believed there was something" fit together given that the issue stayed open for three years?

So for three years you believed there was something, yet you didn't invest sufficient resources to reproduce and/or understand the issue, while at the same time, all these three years security was of utmost importance?

And so is my apartment door. But I can open the door whenever I want and its not up to my landlord to decide which guests I invite.

Intel doesn't charge licensing fees. You might have to pay a lab to certify your device as Thunderbolt 5 compliant, but that's a one time cost and nothing that Intel charges for.

As a German speaker it felt really weird reading it. Like your brain is in English mode, reads over the word, then backtracks, switches to German, reads it again and then continues with English.

> Can't be cheap to run the registry given the obscene size of some terraform providers.

Some providers are also hosted externally. I guess if traffic is going to be a problem they might also just switch to hosting every provider that is build on GitHub to GitHub releases (and hope that GitHub won't change its policy)

  curl -s https://registry.terraform.io/v1/providers/carlpett/sops/0.7.2/download/linux/amd64 | jq .download_url
  "https://github.com/carlpett/terraform-provider-sops/releases/download/v0.7.2/terraform-provider-sops_0.7.2_linux_amd64.zip"

  curl -s https://registry.terraform.io/v1/providers/hashicorp/helm/2.10.1/download/linux/amd64 | jq .download_url
  "https://releases.hashicorp.com/terraform-provider-helm/2.10.1/terraform-provider-helm_2.10.1_linux_amd64.zip"

Maybe they updated their TOS to allow them to do something new with the users data (selling it, storing it in another region, etc) and they want to get rid of accounts that haven't accepted the change.

Its just a guess on my side what a possible rationale may be. Its equally likely that someone just put in a feature request for account expiry without really having a good reason and fully understanding the consequences.

Lets be honest. The more likely thing is that either the coworker would use an unchecked exception or that they would change the callsite to:

  try {
    theUpdatedFunction();
  } catch (MyNewCheckedException e) {
    logger.warn("Whoopsie doopsie", e)
    throw new SomeUncheckedException("Something failed, idk", e)
  }

Which really is a zero sum game. The code still breaks the same way, but the checked exception gets eventually wrapped in an unchecked one. We still would have the situation that someone changed the behavior of the function in a way that is incompatible with your usage.

That bug should have been caught by tests, code reviews and good communication.

I think that's pretty much detailed in the "Why did we update our license to CC BY-SA 4.0?" section of the article.

Thanks. It's always a bit annoying when someone throws around percentages of changes without giving the time frame.

I just researched it a bit more. So while you don't have an entitlement to a Zwischenzeugnis per se, you are entitled if you have a "good reason" to request one. According to some judgements a "good reason" is for example a change of your superiors or if you want to apply for a job elsewhere.

In my career I've requested quite a few Zwischenzeugnisse and never been denied. Probably a place where you have to fight to get one is not a place where you want to be employed anyways.