
They’re done! I have 25 “V is for #Veilid” stickers up on our Ko-Fi! These are hand cut and laminated holographic stickers that also glow in the dark! Fight for your future with one of these stickers lighting up your cyberdeck!


They’re done! I have 25 “V is for #Veilid” stickers up on our Ko-Fi! These are hand cut and laminated holographic stickers that also glow in the dark! Fight for your future with one of these stickers lighting up your cyberdeck!
They’re done! I have 25 “V is for #Veilid” stickers up on our Ko-Fi! These are hand cut and laminated holographic stickers that also glow in the dark! Fight for your future with one of these stickers lighting up your cyberdeck!
I am one of likely many people who follow Veilid with interest, but from a distance. There is something not entirely clear to me wrt Veilid positioning.
AFAIU it now #Veilid is not a protocol effort, where an ecosystem starts to implement an open standard (similar to AP and ATProto) - which I originally thought it was.
Now I have the impression that Veilid is server software + app framework, to get started right away writing secure, privacy-respecting #p2p apps.
Or is it both?
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
A space for Bonfire maintainers and contributors to communicate