HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
lmatteis
torrent-net
C2017–2022
lmatteis / torrent-net

torrent-net

Distributed search engines using BitTorrent and SQLite

8Distinct people
11Mentions
0Explicit recommenders
1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Distributed search engines using BitTorrent and SQLite

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year11 dated mentions

Observed mentions: 2017-04-27 20:50:30 UTC to 2022-01-13 12:29:59 UTC.

012342017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC303
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC413
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101

What Hacker News says

11 sources
Continuing my looking into this, the SQLite range requests trick was implemented in this [0] project. It turns out that project was inspired by a few others [1], two of which [2][3] implement a vfs for SQLite on top of bittorrent doing exactly this suggestion, but with a bittorrent hosted file rather than IPFS. They only download the parts of the SQLite files needed when querying. 0: https://github.com/phiresky/sql.js-httpvfs 1: https://github.com/phiresky/sql.js-httpvfs#inspiration 2: https://github.com/lmatteis/torrent-net 3: https://github.com/bittorrent/sqltorrent
In Database-less torrent website
A torrent client that exposes torrent content as files: https://github.com/distribyted/distribyted It's pretty fun to work on it and implement new use cases. Right now it supports FUSE mounts, but I'm thinking to make it work as a WebDAV server too. Also, I'm working on several demos, like SQLite compatibility, similar to https://github.com/lmatteis/torrent-net, or CSV analysis using Jupyter notebooks for huge datasets like https://ghtorrent.org/
In Ask HN: What is your “I don't care if this succeeds” project?
I honestly think that the idea of letting people search inside a torrent before fully downloading it has been overlooked and might be the next big step in P2P file-sharing: https://github.com/lmatteis/torrent-net The idea is that you can actually query stuff inside a torrent; like actually perform an SQL query and only the pieces relevant to the query will be downloaded. This sort of allows for distributed querying if you think about it, since your query could be satisfied by many different peers that are seeding/leeching. Imagine a Web built this way. Where sites are served by people that visit them and are not just static sites, but fully queryable as you'd expect in the normal HTTP web. I wrote more on this here: https://medium.com/@lmatteis/torrentnet-bd4f6dab15e4
In Ask HN: What comes after BitTorrent?
This is awesome. If only we could share this huge dump of PDF files as a more structured format, perhaps using SQLite [1, 2], we could search through the torrents without having to wait for all of them to download beforehand. Although I guess the fact of having to "download them all beforehand" forces the data to be spread across various computers, hence increases availability of the data. One idea I had regarding this is perhaps structuring the contents of torrents as "append-only binary trees". So as new dumps are released every month, one can simply start downloading the torrent and has "search capabilities" for new data as well. 1. https://github.com/lmatteis/torrent-net 2. https://www.youtube.com/watch?v=EKttt8PYu5M&feature=youtu.be
In Sci Hub repository torrents of scientific papers
I think what he's more talking about is something more akin to a distributed search system than a blockchain - you could make the magnet links last forever in a blockchain, but that doesn't really make sense if no one holds the files anymore you're just keeping useless links around and storing them on every single node for no reason. A search DHT makes much more sense, look up keywords based on hash. Think the Kademlia network from the ED2K days. Maybe I'm being too academic by even suggesting a DHT be used, you could do it in simpler ways like flood search in the style of Gnutella - any distributed search means would work really. I believe there are a few attempts at this in the bittorrent world, like Tribler, which is probably the most practical implementation to date, there's a few others too, none of which look particularly mature yet
Read the rest
: https://sourceforge.net/projects/aresgalaxy/editorial/?sourc... https://github.com/lmatteis/torrent-net https://github.com/boramalper/magnetico The problem with distributed search is that perfecting it is hard - bittorrent has won out because websites could be used to prevent spamming of malware, track reputation and discussion of torrents and individuals, etc. Tribler has some proposed alternatives here and I seem to remember Kad having done a decent job preventing this from becoming a significant problem, but it never had the popularity. If someone manages to knock out all the big torrent and usenet indexes overnight, these systems will become a lot more necessary and probably get a lot more popular.
In Better than Free (2008)

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.