Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

despite the downvotes, there is some substance to this. mutability is useful.

however, as implemented, all that is needed is for the user of p2psearch to refresh and the browser to pick up the latest database. i imagine most users are not keeping torrent search open 24/7, so this doesn't seem onerous.

it's probably a bit of a process for the host of the frontend to update the database, prepare a new torrent, update the code [0], and then rebuild the bundle regularly, but this could be automated.

regardless, it doesn't seem so unreasonable from an end user perspective, and i personally don't mind if my torrent search index is behind by a few days.

[0] https://gitlab.com/boredcaveman/p2psearch/-/blob/main/src/Me...



> it's probably a bit of a process for the host of the frontend to update the database

Right, I suppose I didn't put my point very well, but as I see it there are only two options:

* Everyone gets their code (with the built-in torrent for the database) from the same source, presumably the source that created / seeds the database. In this case the host is arguably just as vulnerable to the authorities as The Pirate Bay. If p2psearch doesn't make torrenting more resilient than TPB, what purpose does it serve?

* One brave citizen creates and hosts a single copy of the database, and it goes viral. Lots of people host it. It never gets updated, because the whole point of using IPFS / torrents is that everything can be addressed statically. In this case the advantage of p2psearch is obvious - it functions as a DHT with a built-in search that is more or less impossible to take down! On the other hand, the lack of mutability greatly reduces the value, since as I said in my OP most torrenting is focused on new releases.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: