torrent-net
sqltorrent
Our great sponsors
torrent-net | sqltorrent | |
---|---|---|
12 | 5 | |
1,019 | 269 | |
- | 1.1% | |
0.0 | 0.0 | |
4 months ago | about 8 years ago | |
C | C | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
torrent-net
- Database-Less Torrent Website
-
distributed internet search
Another suggestion, sqltorrent has been used to do something like this...torrent-net
-
How to circumvent Sci-Hub ISP block
I believe this is the project mentioned
https://github.com/lmatteis/torrent-net
- torrent-net - distributed search engines using BitTorrent and SQLite
- Distributed search engines using BitTorrent and SQLite
sqltorrent
-
BTFS (BitTorrent Filesystem)
Or even better store data as an sqlite file that is full-text-search indexed. Then you can full-text search the torrent on demand: https://github.com/bittorrent/sqltorrent
- SQLite BitTorrent Vfs
-
How to circumvent Sci-Hub ISP block
"There was that project some guy posted a while back that used a combination of sqlite and partial downloads to enable searches on a database before it was downloaded all the way."
https://github.com/bittorrent/sqltorrent
- Hosting SQLite databases on GitHub Pages (or any static file hoster)
-
Distributed search engines using BitTorrent and SQLite
Interesting question. I looked at the source code to understand that.
SQLite knows where to look for when you open a SQLite database and you run a query, right? It just asks the underlying filesystem to provide N bytes starting from an offset using a C function, then it repeats the same operation on different portions of the file, it does its computation and everybody is happy.
The software relies on sqltorrent, which is a custom VFS for SQLite. That means that SQLite function to read data from a file stored in the filesystem is replaced by a custom function. Such custom code computes which Torrent block(s) should have the highest priority, by dividing the offset and the number of bytes that SQLite wants to read by the size of the torrent blocks. It is just a division.
See: https://github.com/bittorrent/sqltorrent/blob/master/sqltorr...
What are some alternatives?
torrent-paradise - Decentralized DHT search site for IPFS
sql.js-httpvfs - Hosting read-only SQLite databases on static file hosters like Github Pages
edge-sql - Cloudflare Workers providing a SQL API
ipfs - Peer-to-peer hypermedia protocol
GreenTunnel - GreenTunnel is an anti-censorship utility designed to bypass the DPI system that is put in place by various ISPs to block access to certain websites.
datasette - An open source multi-tool for exploring and publishing data
fatcow-icons - FatCow icons v3.9.2 (I was given a permission to host these on GitHub by FatCow support.)
IPSQL - InterPlanetary SQL
apsw - Another Python SQLite wrapper
dqlite - Embeddable, replicated and fault-tolerant SQL engine.
SkySQL