Magnetico VS bittorrent-tracker

This is really neat. I'll need to check it out. A couple years ago I ran my own instance of Magnetico (https://github.com/boramalper/magnetico), but this project looks a lot more polished.

This is likely your best bet, but I'd recommend you use postgres over sqlite, this is however where development died so some features like search or stats aren't implemented while using pg as the db.

You can create decentralized bittorrent indexers though (see https://github.com/boramalper/magnetico as an example)! This means you can search for bittorrent files without having to rely on a centralized service (although building the index does require some time & storage space of course).

https://github.com/boramalper/magnetico

Someone else did this a while back, universe continues to exist.

I just get a rickroll gif on your link. Did you mean this project?

"Autonomous (self-hosted) BitTorrent DHT search engine suite."

https://github.com/boramalper/magnetico

Although I admit, that I would love to see a maintained DHT search solution (like magnetico or dhtcrawler2).

Yeah, you probably found it. Abandoned, yes, but not necessarily unfinished.

A magnet search is easy enough to self-host, I can provide you with instructions to self-host a clearnet magnet search engine over I2P in the meantime, but you can probably figure it out from this: https://github.com/boramalper/magnetico which is an easy to self-host DHT search engine.

It works great! By default it leverages public WebTorrent trackers to connect users, but you can also host your own with https://github.com/webtorrent/bittorrent-tracker.

aquatic_http is a BitTorrent over HTTP over TLS tracker and aquatic_ws is a WebTorrent over TLS tracker. I don't have full current benchmarks comparing them to other options, but in a previous one, aquatic_ws handily outperformed both wt-tracker and bittorrent-tracker.