Re:Bitmagnet: A self-hosted BitTorrent indexer, DHT crawler,...
by the8472 on Thursday October 05, 2023 @11:25AM
(#37779825)
It seems like every single of these things always cut corners and don't implement proper, spec-compliant nodes that provide the same services as they use. You know, the "peer" in p2p.
BEP51 was designed to make it easier to not trample on the commons, and yet...
[ Parent
| on HN ]
Re:Bitmagnet: A self-hosted BitTorrent indexer, DHT crawler,...
by e12e on Thursday October 05, 2023 @11:32AM
(#37779919)
Appreciate that you took the time to file an issue:
Re:Bitmagnet: A self-hosted BitTorrent indexer, DHT crawler,...
by zolland on Thursday October 05, 2023 @12:41PM
(#37780825)
Without the peers all we have is to!
Re:Bitmagnet: A self-hosted BitTorrent indexer, DHT crawler,...
by mgdigital on Thursday October 05, 2023 @01:30PM
(#37781415)
Author here. FWIW I wasn't intending this to make it onto HN, having posted about this on Lemmy looking for beta testers. The current version of the app is very much a preview. There's much further work to be done and this will include as far as possible ensuring Bitmagnet is a "good citizen". The suggestions made on the GH issue look largely feasible and I'll get round to looking at them as soon as I can.
The issue and my response on GH: https://github.com/bitmagnet-io/bitmagnet/issues/11
Re:Bitmagnet: A self-hosted BitTorrent indexer, DHT crawler,...
by Y-bar on Friday October 06, 2023 @10:49AM
(#37791538)
Hey! Don't know if the Github repo or here is the best way to ask since the Discussions on the repo are not active.
I have started the docker-compose.yml file in WSL and it has been running for an hour slowly accumulating a few megabytes of redis data running at about 5% CPU usage. Inspecting it shows magnet links. It appears to be working.
But visiting the the web interface at localhost:3333 just yields "Firefox can’t establish a connection to the server at localhost:3333." after a 30 second timeout.
Would you have a guess why?