icanhazaxfr.com is a service that transfers the zone file of 'icanhazaxfr.com' to anyone.

The goal of the service is to provide a freely available axfr service with a concise enough zonefile that it is practical to use it for unit tests.

Please choose another hill to die on. This is just not worth it. Clearly it's possible to do this on device like mozilla did it.

>If you're making all your config changes from a prompt it's easy to forget how or why you set something up a specific way [...]

The correct way would be to just document the changes.

I tried that, but I'm not sufficiently superhuman. Things slowly but inexorably drift out of sync as changes get made in one place but not the other, despite my best efforts. Declaring how things should be and then letting the computer make it so is both less work and more reliable. (This is why I call it "executable documentation".)

Codeberg is a customized version of gitea[0].

They have a repo[1] with the patches that are used on on codeberg.

[0]: https://gitea.io

[1]: https://codeberg.org/Codeberg/build-deploy-gitea

Is there a link somewhere where he published the result?

I found it, but clicking it caused my computer to run out of available memory.

Edit: on a more serious note, a site[0] that tracks these records says:

> Downloading of digits is no longer available due to the massive bandwidth requirements. Your best bet is to directly contact one of the record holders and see if they still have a copy of the digits.

[0] http://www.numberworld.org/digits/Pi

The compressed representation requires 44 TB of disk space.

Assuming the author has a typical home internet connection with about 5 Mbps upload rate, the transfer would take 2 years longer than it took to actually run the calculation in the first place!

Here’s more info about the race between calculating and downloading digits of pi

https://opendata.stackexchange.com/a/4024/1511

It's still important to donate to them so they can stay independent.

Say Wikimedia would become dependent on the donations of a company, that company could technically force them to publish misleading information.

In regards to mozilla they are currently not financially independent.

Most of their money comes from google (in exchange google is the default search engine).

"Dependent" suggests a necessity is being fulfilled, and that's the point of my comment. We're past necessity. Both Mozilla and Wikimedia are already bringing in several times over the amount of cash they need to operate.

AIUI, both organizations have plenty of worthwhile projects which are constrained by available funding. They're not just maintaining a web browser + hosting an encyclopedia.

Of course, this is not to say that funding the Archive isn't also important.

> both organizations have plenty of worthwhile projects

Yes of course.

But both projects' biggest constraints are not (lack of) funding. It's bad mismanagement, or in the case of Mozilla, really bad mismanagement.

This isn't exactly correct (at least not in all cases): https://blog.cloudflare.com/cloudflare-onion-service/

[Nitpick: it's Tor not TOR]

While they do have a favicon they however still show the url.

Is this similar to cjdns or yggdrasil?

No, Ouroboros rethinks the whole network architecture, from the ground up. cjdns and yggdrasil build on top of IPv6, which we believe has the same architectural flaws as IPv4.

For accuracy, Yggdrasil doesn't "build on top of IPv6", it merely uses IPv6 over TUN in the current binaries because that most closely translates to a usable experience for real people today without having to rewrite their applications. It has been a good way to get users to help scale-test.

The underlying routing scheme, virtual switch/router implementation, specification etc are not aware of (nor do they care about) IP.

IIRC they disabled autoplay for videos with sound. In the settings you can also completely disable autoplay for all videos.