We are running a lot of IPv6 only clusters and don't have any issues. The key solution is to have a NAT64 gateway somewhere at the edge.

To be fair, it really isn't designed to rely on one server. And if you don't want to run your own, you can always have someone host the server for you.

The article has nothing to do with IPv6.

The whole point of the article is that Google's sender identity scoring system is more strict when the sending IP is an IPv6 one. That's a pretty clear cut link to IPv6, no?

Google is really strict in general about these kinds of things. I had to go a few rounds with my VPSes before emails from them would consistently not end up in spam, but looking at the headers I'm mostly using IPv6 so I don't draw the conclusion "don't use IPv6" just "if you have IPv6, which is more likely than not now, be careful and read the docs"

Let me rephrase: the whole article is equally valid for IPv4. Being more or less strict is a claim the article makes without proof. And as far as my experience goes, there is no difference.

So standing by it: the article has nothing to do with IPv6 per se.

Huh? I'm not even sure how you came to that conclusion.

Gmail is probably tougher on mail servers using IP6 addresses because they're plentiful and I suspect spammers were having a field day setting up temporary mail relays forcing google to play whack-a-mole.

I used to run my own email server years ago but spam and spam protection measures have made it time consuming and annoying. I'll leave it to the professionals.

thanks for the feedback, I'll tune the sound quality for the next episode

Just a heads up: we have just launched the 1000eyes project on https://1000ey.es that tries to give you ready-to-use Open Source and IPv6 enabled cameras without any configuration needed.

That is correct, CHF prices are more or less the same as USD nowadays.

In case it matters for you: Compared to DO this service is running on a zero carbon infrastructure and your IP address is located in Switzerland.

I doubt that this is true. Given the amount of advantages you have from learning in the Internet and avoiding mistakes locally.

There is no business model behind has-a.name. It's main motivation came from our customers, who are using the IPv6VPN quite intensive.

Many of our customers are app developers (ruby, python, clojure, you name it) and they develop on their notebooks that are IPv6 enabled (usually a /64 or /48 per device).

To be able to share in-development state with other remote developers, the common thing to do would be to pass around a http://[2a0a:e5c0:...] url that was http only.

This is not only cumbersome (no one likes to type square brackets), but also potentially risky, as there is no MITM protection whatsoever.

To fix this problem we created has-a.name, because customers/developers now go ahead and just create a docker container and share it as https://2a0a-e5c0-...has-a.name with their co-developers.

Because our whole company consists of a bunch of Open Source Hackers we decided to make it public to allow others work around the same problem.

Even though we promise to never change the automatic resolution (that's work, doesn't make sense to do that for us), you don't have to trust has-a.name. You can register your own domain and replicate our setup and use your domain instead.

I hope that clarifies a bit the business model question.

While that is true, you can still fully run your network IPv6 only. At the border router, you can simply use NAT64 to reach the IPv6 Internet.

Indeed, you can do that. I am actually doing that at various places at the moment. If you want to discuss how to do it, you can reach me directly on https://IPv6.chat