Results:

- The BitTorrent client uses the Rust library rqbit.
- For eDonkey and Kademlia it uses its own implementation. But I told it to compare it with the implementation of the eMule 0.70b code to make sure it was compatible.
- NAT traversal and IPv6 have been added as suggested by David Xanatos for future versions of eMule.
- The client can download from the three networks at the same time; you add a Torrent or an eLink and it searches for the hash across all the networks.
- Automatic updating of Kademlia nodes through the clients of the eDonkey network.

And most importantly, it works.

It’s quite tedious to build, and obviously you have to know what you’re asking for. At first I gave it the NeoLoader code, which is essentially the original client created by David Xanatos that has the same function but is obsolete, and I wanted to make changes to it, but that meant working on an old architecture, so I thought, let’s start over, and with Rust.

Would I entrust critical code like that of a nuclear reactor to Codex? No.

Would I build office applications so I wouldn’t have to depend on Microsoft? Yes.

Can you build critical code? Yes, as long as you review all the generated code.

Is this a revolution? In 2024, no. Now, yes. It’s literally incredible that in one morning I was able to accomplish all this in Rust.

👊💪

Quien es este puto tumor fetal?

🤔

In just over three hours, I have a literally functional version of a client written from scratch in Rust in the style of Neoloader, i.e., eMule + torrent, without dragging along errors from the past and adapted to the new times.

This is a totally new paradigm. With AI, you will be able to build your own applications that only do what you want them to do.

The Spanish government is now targeting VPNs under the pretext of soccer piracy.