Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
bitmagnet
A self-hosted BitTorrent indexer, DHT crawler, content classifier and torrent search engine with web UI, GraphQL API and Servarr stack integration.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
https://github.com/uber/kraken?tab=readme-ov-file#comparison...
"Kraken was initially built with a BitTorrent driver, however, we ended up implementing our P2P driver based on BitTorrent protocol to allow for tighter integration with storage solutions and more control over performance optimizations.
Kraken's problem space is slightly different than what BitTorrent was designed for. Kraken's goal is to reduce global max download time and communication overhead in a stable environment, while BitTorrent was designed for an unpredictable and adversarial environment, so it needs to preserve more copies of scarce data and defend against malicious or bad behaving peers.
Despite the differences, we re-examine Kraken's protocol from time to time, and if it's feasible, we hope to make it compatible with BitTorrent again."
Just the other week I used Nix on my laptop to derive a PXE boot images, uploaded those to IPFS, and netbooted my server in another country over a public IPFS mirror. The initrd gets mounted as read-only overlayfs on boot. My configs are public: https://github.com/jhvst/nix-config
This happens to be one of the pipe dream roadmap milestones for bitmagnet: https://bitmagnet.io/#pipe-dream-features
I used to use magnetico and wanted to make something that would use crawled info hashes to fetch the metadata and retrieve the file listing, then search a folder for any matching files. You'd probably want to pre-hash everything in the folder and cache the hashes.
I hope bitmagnet gets that ability, it would be super cool
I did something similar some years ago, https://github.com/ceritium/fuse-torrent
I had no idea what I was doing, most of the hard work IS done by the torrent-stream node package
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
Maybe something like this? https://github.com/containers/fuse-overlayfs
https://github.com/whipper-team/whipper
https://github.com/thomas-mc-work/most-possible-unattended-r...
Finding a good CD drive to rip them is the first step.
https://flemmingss.com/importing-data-from-discogs-and-other...
IME Discogs had the track data most often.
And obviously rip to flac
https://github.com/whipper-team/whipper
https://github.com/thomas-mc-work/most-possible-unattended-r...
Finding a good CD drive to rip them is the first step.
https://flemmingss.com/importing-data-from-discogs-and-other...
IME Discogs had the track data most often.
And obviously rip to flac
https://github.com/whipper-team/whipper
https://github.com/thomas-mc-work/most-possible-unattended-r...
Finding a good CD drive to rip them is the first step.
https://flemmingss.com/importing-data-from-discogs-and-other...
IME Discogs had the track data most often.
And obviously rip to flac
https://github.com/anacrolix/torrent has a fuse driver since 2013. I'm in the early stages of removing it. There are WebDAV, 3rd party FUSE, and HTTP wrappers of the client all doing similar things: serving magnet links, infohashes, and torrent files like an immutable filesystem. BitTorrent v2 support is currently in master.
This project still seems alive to my pleasant surprise.
https://github.com/automatic-ripping-machine/automatic-rippi...
I never had it fully working because the last time I tried, I was too focused on using VMs or Docker and not just dedicating a small, older computer to it, but I think about it often and may finally just take the time to set up a station to properly rip all the Columbia House CDs I bought when I was a teen and held on to.
This project still seems alive to my pleasant surprise.
https://github.com/automatic-ripping-machine/automatic-rippi...
I never had it fully working because the last time I tried, I was too focused on using VMs or Docker and not just dedicating a small, older computer to it, but I think about it often and may finally just take the time to set up a station to properly rip all the Columbia House CDs I bought when I was a teen and held on to.
Pretty sure AccuRip is only a collections of checksums to validate your rips. http://cue.tools/wiki/CUETools_Database actually improved on it to provide that healing feature (via some kind of parity, I guess?).
Related, I use and recommend https://github.com/cyanreg/cyanrip on modern UNIXes.