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.

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

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!

This is a Scala re-implementation of the Chromaprint/AcoustID audio fingerprinting algorithm.

I had a few reasons for picking Chromaprint. I was interested in building a media player with Scala (still working on that on-and-off). I noticed that Python seemed to be a more popular language for this type of thing and was frustrated that some key libraries I wanted to use, particularly this one, are available for Python but not on the JVM. The more I looked into Chromaprint the more it intrigued me; I wanted to understand how it works and in a way set the algorithm free as it's almost become a standard for audio identification. I found a few reimplementation attempts in other languages on GitHub but couldn't get any of them working, so I guess I saw it as a challenge, you could also call it a rabbit hole. Aside from that, I was looking for an excuse to use Scala in a project. Kotlin looks interesting too and I'll hopefully get the chance to work with it someday, I can see that it is probably easier to pick up and might be a better choice for a big team - but Scala seems more faithful to functional programming principles and I find the style more elegant.

I agree it's a slightly quirky name. The "chroma" refers to chromatography. In order to create the finger"print", an image is first extracted from the audio. An image fingerprinter would probably use many of the same techniques (e.g. fourier transform).

It's funny you say that, I learned it because I believe it's in demand commercially, and is also a joy to work with. I perceive that companies using Scala would be on average better to work for (from a developer's point of view) than those using say NodeJS or PHP.

This has been my testbed project for learning Scala, I also learned a lot about audio analysis, signal processing, fourier transforms etc. There were already Python bindings for the original C++ library but no easy way to use it on the JVM. I hope someone might find it useful/interesting. All feedback welcome!