picotorrent VS sql.js-httpvfs

While the torrent client included in the owntinfoil zip is open source, the two .exe's included are not, and he's actually violating the open source license for https://github.com/picotorrent/picotorrent

You can look the code of PicoTorrent, is a clean and small client (based on libtorrent too) : https://github.com/picotorrent/picotorrent

Love Transmission but went to picotorrent a few years ago, even smaller footprint https://github.com/picotorrent/picotorrent

I wish some of the other BT clients took off besides the big 3 (Qbt, Deluge, Transmission and I guess rtorrent+rutorrent as well). There are some other simple BT clients out there that mimic early uTorrent GUI, one of the most notable was Hadouken, which was headless. It had a web UI that's reminiscent of uTorrent 2.0.4. https://github.com/hadouken/hadouken Sadly the project seems dead, as the last official release was in 2015. There's another minimal torrent client named Picotorrent available for Windows https://github.com/picotorrent/picotorrent, but I am not sure how well this works on heavy libraries, and I doubt many private trackers allow it because it's so niche. Another client I used to use back in the day was Halite, but that also died in 2015.

Not really true - v0.20 of PicoTorrent [1] was released the same day as libtorrent released support for v2 torrents. I think this predates BiglyBT 2.5 with v2 [2] support with about two weeks.

[1] https://github.com/picotorrent/picotorrent/releases/tag/v0.2...

Picotorrent which I have never personally used but which I have heard good things about: https://github.com/picotorrent/picotorrent

A new windows client built on C++, picotorrent

I couldn't find do these wrappers support read-only SQLite databases with HTTP range requests, like in this famous post [1]. Phiresky's wrapper supports it, but it seems to be rebuilding the whole sql.js [2], I'd rather have it as VFS on top of sqlite.org's own WASM module. I like the idea of HTTP range requests, but I don't want to run a fork, that will be unmaintained in few years.

[1]: https://news.ycombinator.com/item?id=27016630

[2]: https://github.com/phiresky/sql.js-httpvfs

Oh that’s an interesting idea. I saw someone built SQLite over HTTP with the Range header: https://phiresky.github.io/blog/2021/hosting-sqlite-database...

So presumably in a similar manner as https://github.com/phiresky/sql.js-httpvfs you could map SQLite pages to leaf torrents too and get the chunking you are looking for.

But ripgrep has to read the whole file; if your intended use case is searching a blog, I'd recommend using something which makes an index, so you don't need to download everything. For example, sql.js-httpvfs is SQLite ported to wasm, with the DB file read over HTTP. If you use FTS to make an index, it works astonishingly well for text search.

How close is Python SQLite and Datasette Lite to accessing a hosted SQL database using HTTP range requests as can be done in sql.js like https://github.com/phiresky/sql.js-httpvfs?

I put together a Pyodide-based web app where users need a few indexed queries from a 600mb SQLite database but it isn't very practical for them to download the whole thing into the browser.

https://observablehq.com/@thadk/life

You can also access sqlite databases directly from an http server that supports range requests (like s3). There are a bunch of implementations of this in different languages including Go[0] and Javascript[1].

[0]: https://github.com/psanford/sqlite3vfshttp

[1]: https://github.com/phiresky/sql.js-httpvfs

Thanks to SQLite VFS abstraction, it is possible to implement your own file system on which SQLite parks data and structures. Inspired by Phiresky's sql.js-httpvfs which uses HTTP Range requests to lazy load blocks of storage from a static web server, I changed few lines of code to point the VFS read() calls to a database seeded by peers as a torrent. A 300 MiB db with 2 million records can be queried from seeders for full text searches in less than 2 MiB traffic with the BitTorrent protocol, all inside the browser, in a static website.

Hosting SQLite Databases on GitHub Pages" https://news.ycombinator.com/item?id=28021766 : DuckDB can query [and page] Parquet from GitHub, sql.js-httpvfs, sqltorrent, File System Access API (Chrome only so far; IDK about resource quotas and multi-GB datasets), serverless search with WASM workers

https://github.com/phiresky/sql.js-httpvfs :

> sql.js is a light wrapper around SQLite compiled with EMScripten for use in the browser (client-side).

> This repo is a fork of and wrapper around sql.js to provide a read-only HTTP-Range-request based virtual file system for SQLite. It allows hosting an SQLite database on a static file hoster and querying that database from the browser without fully downloading it.

> The virtual file system is an emscripten filesystem with some "smart" logic to accelerate fetching with virtual read heads that speed up when sequential data is fetched. It could also be useful to other applications, the code is in lazyFile.ts. It might also be useful to implement this lazy fetching as an SQLite VFS [*] since then SQLite could be compiled with e.g. WASI SDK without relying on all the emscripten OS emulation.

It doesn't have to be range requests, you could split the file instead of depending on the range requests. Essentially it's the same as the chunking instructions for hosters who have a maximum file size as is demonstrated here: https://github.com/phiresky/sql.js-httpvfs/blob/master/creat...