81–90 of 103 posts
I'm the author of https://github.com/anacrolix/torrent (started in 2013) and https://github.com/anacrolix/dht (started in 2015). I have a DHT indexer implementation I developed in 2021. It's currently closed source but available for use as part of https://www.coveapp.info/ . I have found that after several hours the search is excellent and stays up to date with ease.
Earlier quoted context omitted.
You don't need an indexer for that. All you need is a static list with all your music, and people can click on links to download your music. Give them qbittorrent and it'll be running smoothly.
Sure, but I'd like to go beyond magnet links and make it properly decentralized, with the discovery happening in the DHT and torrent swarm.
I like your idea of giving its name back to a technology that just works better, and I think it pairs really well with giving back a humane touch to how we use the internet, computers, and putting people back at the center rather than thinking about tools first !
Earlier quoted context omitted.
Then you have a user reputation problem instead… me and my 5 million alts say this is the REAL korn_blind.mp3.exe. Nothing is new under the sun since the internet was created, these are the same problems that email has tried and failed to solve for 50 years.
Its going to be an unpopular take, but crypto solves this. As in currency. Make people attest to things with locking a very small amount of money.
So claims Elon on Twitter, a platform that is very obviously to anyone who uses it completely overrun with bots who have found it very profitable to validate their spam accounts and get preferential listings for a mere eight dollars, while scaring off legitimate users who (fairly) do not trust a service with no functioning security department with their payment information.
The web UI is super slow. It's slow with the default view of 10 results per page and unbearably slower at 100. These aren't big numbers and my computer isn't old, something was poorly done here and setting the default number of results per page to 10 clearly is not the correct fix. (For the record it only has a mere thousand results so far..) Also, the content classification is so bad it might as well not exist. How…
This project only started a few months ago. It's just young and being worked on - no need to dis this as half-baked.
"Unlike well-moderated torrent sites, Bitmagnet adds almost any torrent it finds to its database. This includes mislabeled files, malware-ridden releases, and potentially illegal content. The software tries to limit abuse by filtering metadata for CSAM content, however." This is by far the biggest hurdle to something like this. You'll eventually have to end up again with a centralized curator.
"Unlike well-moderated torrent sites, Bitmagnet adds almost any torrent it finds to its database. This includes mislabeled files, malware-ridden releases, and potentially illegal content. The software tries to limit abuse by filtering metadata for CSAM content, however." This is by far the biggest hurdle to something like this. You'll eventually have to end up again with a centralized curator.
Further more, the filter itself can be made to limit disclosure of the original data while still providing a binary decision regarding filtering a content or not. Hashing, bloom filters, ai models and so on are common tools for filtering data like emails and link reputation.
Is it possible to use bots or use a riaa enforcement group equivalent to get ad blockers to green lights specific ads? Personally I trust easylist as long the community does so, and would discard it the moment it lost the community trust. That makes it a kind of centralized curator, but also very much not.
The web UI is super slow. It's slow with the default view of 10 results per page and unbearably slower at 100. These aren't big numbers and my computer isn't old, something was poorly done here and setting the default number of results per page to 10 clearly is not the correct fix. (For the record it only has a mere thousand results so far..) Also, the content classification is so bad it might as well not exist. How…
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.
Who remembers Skytorrents ( https://news.ycombinator.com/item?id=13423629 )? Posted as a "Show HN" here, it was a DHT-sourced index and stack written in C with no JavaScript, no cookies, no ads, no tracking. Skytorrents was unbelievably fast, friendly, and complete, and this translated into rapid adoption and traffic growth that caused the site to shut down due to server costs after just a year ( https://torrentfreak…
Earlier quoted context omitted.
> You have to be participating in a torrent swarm in order to bootstrap yourself into DHT at all. This is not correct. > Bittorrent's DHT is not a network independent of torrent swarms. This is also wrong. People have used the DHT for non-torrent-related purposes. > You need the address of a peer who is already part of the network in order to join it, and you have to get a list those addresses from somewhere. And not…
Which of these methods is not obtaining the address of a node in a swarm, or hitting a tracker for a list of nodes in a swarm? > People have used the DHT for non-torrent-related purposes. This is simply non-responsive. People have used a DHT overlaid on the collection of torrent swarms for non-torrent related purposes. > And nothing dictates that that has to be obtained via the bittorrent peer protocol. This is a sil…
The "find bootstrap nodes via a bunch of DNS records, then persist long-lived contacts locally" approach is quite common.
> People have used a DHT overlaid on the collection of torrent swarms for non-torrent related purposes.
No, the software does not involve joining any bittorrent swarms at all.
Implementing sample_infohashes opens your torrent client to abuse. UDP responses are much larger than queries and this protocol (BEP51) allows attackers that can spoof source IP addresses to use a large number of clients as mules for amplified distributed denial of service attacks.
And ISPs are in a much better position to solve this problem anyway. They should ask for higher peering fees from peers that don't do source-filtering.