This weekend wraps a replatforming of the #stigmerge CLI onto a high level #filesharing API. A necessary step towards a #Transmission like interface. Experimenting with #tauri now.
A few bug fixes happened as well :)
https://github.com/cmars/stigmerge/releases/tag/stigmerge-v0.5.7
Need to fix #rust docs.rs, they're not building yet 🤦
This weekend wraps a replatforming of the #stigmerge CLI onto a high level #filesharing API. A necessary step towards a #Transmission like interface. Experimenting with #tauri now.
A few bug fixes happened as well :)
https://github.com/cmars/stigmerge/releases/tag/stigmerge-v0.5.7
Need to fix #rust docs.rs, they're not building yet 🤦
Some exciting #stigmerge updates to share!
All stigmerge peers are now seeders -- there are no #leechers in official stigmerge releases. Sharing is caring! #veilid private routing mitigates the privacy hazards normally associated with sharing content over public networks directly.
Peers gossip with each other constantly, advertising themselves and discovering new neighbors -- and they store these contact lists in the #veilid DHT like a pheromone trail. So even when an original seeder is long gone and goes offline -- if just one of its last-known neighbors is online, future travelers still have a chance to join a live swarm of active peers.
Fetchers can balance downloads among multiple peers, gravitating towards the most productive ones.
It's also super-easy to run stigmerge from an OCI container now (#Docker or #Podman as you like).
Check out the updated README for more details -- and the 0.5.6 release to try these new superpowers out for yourself!
https://github.com/cmars/stigmerge
https://github.com/cmars/stigmerge/releases/tag/stigmerge-v0.5.6
Some exciting #stigmerge updates to share!
All stigmerge peers are now seeders -- there are no #leechers in official stigmerge releases. Sharing is caring! #veilid private routing mitigates the privacy hazards normally associated with sharing content over public networks directly.
Peers gossip with each other constantly, advertising themselves and discovering new neighbors -- and they store these contact lists in the #veilid DHT like a pheromone trail. So even when an original seeder is long gone and goes offline -- if just one of its last-known neighbors is online, future travelers still have a chance to join a live swarm of active peers.
Fetchers can balance downloads among multiple peers, gravitating towards the most productive ones.
It's also super-easy to run stigmerge from an OCI container now (#Docker or #Podman as you like).
Check out the updated README for more details -- and the 0.5.6 release to try these new superpowers out for yourself!
https://github.com/cmars/stigmerge
https://github.com/cmars/stigmerge/releases/tag/stigmerge-v0.5.6
#stigmerge update!
The stigmerge-peer crate has been heavily refactored into an actor-based architecture, a very CSP-like design with supervisors. i have a strong aversion to frameworks, so I implemented my own model inspired by https://ryhl.io/blog/actors-with-tokio/.
I still need to implement much of that advice.. Deal with backpressure, etc. but...
Last night I sent a file through successfully with share announcer, resolver, seeder and fetcher actors!
Hoping for a new major version release in the next couple of weeks. It will likely be a protocol and CLI breaking change.
