mgdigital

Can I take a wild guess that you're using Firefox? I have noticed Firefox performance is much worse than any other browser. I think this is due to issues in the Angular and Material components being used.

As stated in the big red notice in the website, the software is currently in alpha preview. Given time, Bitmagnet will be trying to mitigate the Firefox performance issues (the <5% market share means it's prioritised accordingly), but it's important that users of all browsers can have acceptable experience in the app.

Some of the features in your screenshots look interesting, but why is Cove closed source?

Or connect with trusted curators over a decentralized network, similar to the fediverse?

Bitmagnet may download metadata about CSAM content, which is automatically deleted with fairly high accuracy. You would never be redistributing it. No outgoing peer protocol is currently implemented. This is planned but it will give users control of what they're sharing rather than indiscriminately sharing everything.

Incoming and outgoing are both limited, I think the worst such an attack could do is prevent responding to legitimate incoming queries - this shouldn't slow down the DHT crawler in a noticeable way.

Bitmagnet has rate limiting on incoming UDP requests (both overall and per-IP) so I don't know that it would be vulnerable; if there's anything else that should be done to mitigate any risk I'd like to know.

I guess the takeaway is that a public torrent site can (probably) never be sustainable while acting in users' best interests?

I'm also open to more feedback, if there are specific areas that need attention let me know :)

I have worked with the8472 to get Bitmagnet's BEP5 & BEP51 implementations working and ensure it's a good citizen on the network - there is more to be done and more protocols to be implemented, but unlike Magnetico, BM is not simply scraping without responding to incoming requests.

Thanks - I only condone accessing the legal content available on BitTorrent, and my screenshots now embody this moral stance.

Why tsinject? Having used DI containers for other languages, I was looking for something simple with a clean functional interface. Most existing TypeScript solutions rely on decorators or are restrictive and clunky in other ways. I've used something similar to this in a few projects and thought I'd open source it, I hope it's useful for someone!