Exactly, this fits perfectly in the `.well-known` use cases. What a shame.

I've worked for many years with both frameworks. I have the opposite view, since I prefer the Django ecosystem and Python.

Rails has nice things, but overall, I prefer Django's approach and the language it uses.

I'm not surprised

Awesome, looking forward to testing it out. I really like that idea of being able to gradually migrate WSGI (Django) apps, or even support running both at the same time.

Some time ago, I built a similar project: https://github.com/dethos/worker-ddns

The main difference is that, for security reasons, it uses a "Cloudflare worker" to change the DNS record.

> Since Cloudflare API Token permissions aren't granular enough to limit the token access to a single DNS record, we place a worker in front of it (this way the token with extra priviledges never leaves cloudflare's servers).

It works very well, no complaints until now.

I solved it by avoiding Google products and services, whenever possible.

That 'whenever possible' qualifier gets more significant everyday

Sounds great. I'm eager to try it, when a release with early Linux support is published. Keep it going.

`curl https://zed.dev/install.sh | sh`

Fairphone?

It is a good question, I assume that for the overall internet the adoption percentage will always be very low. However, the sites scanned are, theoretically, the top 1M, which include a high number of established businesses and other big organizations. So, I hoped that in this "sample" the percentage would be higher.

I guess that depending on the situation, people will use different mediums.

If I'm at the computer, I prefer to read and/or scroll an article. If I'm on the move, listening would definitely be better.