#p2panda — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #p2panda, aggregated by home.social.
-
v0.6.0 of #p2panda has been released! 🌱 🥰
The star of the show is undoubtedly our new Node API ✨
If you've been dreaming of an out-of-the-box #p2p stack with built-in networking, discovery, bootstrap, #localfirst sync, event streaming, causal ordering, storage and more...this one's for you!
Here's an example of a simple, collaborative TODO list CLI application for a first taste of the new Node API in action:
https://github.com/p2panda/p2panda/blob/main/p2panda/examples/todo.rs
Release notes here:
-
-
-
-
Hui! This is #p2panda doing #localfirst sync over #LoRa in a #mesh network 🐼 📻
We're experimenting currently with a log-based, replicated delay tolerant / store-and-forward protocol using the RNode transceiver firmware. All very early but fun!
-
Hui! This is #p2panda doing #localfirst sync over #LoRa in a #mesh network 🐼 📻
We're experimenting currently with a log-based, replicated delay tolerant / store-and-forward protocol using the RNode transceiver firmware. All very early but fun!
-
Hui! This is #p2panda doing #localfirst sync over #LoRa in a #mesh network 🐼 📻
We're experimenting currently with a log-based, replicated delay tolerant / store-and-forward protocol using the RNode transceiver firmware. All very early but fun!
-
Hui! This is #p2panda doing #localfirst sync over #LoRa in a #mesh network 🐼 📻
We're experimenting currently with a log-based, replicated delay tolerant / store-and-forward protocol using the RNode transceiver firmware. All very early but fun!
-
Hui! This is #p2panda doing #localfirst sync over #LoRa in a #mesh network 🐼 📻
We're experimenting currently with a log-based, replicated delay tolerant / store-and-forward protocol using the RNode transceiver firmware. All very early but fun!
-
Managed to hack #Multiplex to use #p2panda (using the GObject bindings for Go) for it's P2P playback position sync. Was ... pretty painless? Lots of things left to do and UX feedback (discovery, showing other nodes etc.) to get from folks, but it just kind of ...
-
Managed to hack #Multiplex to use #p2panda (using the GObject bindings for Go) for it's P2P playback position sync. Was ... pretty painless? Lots of things left to do and UX feedback (discovery, showing other nodes etc.) to get from folks, but it just kind of ...
-
Managed to hack #Multiplex to use #p2panda (using the GObject bindings for Go) for it's P2P playback position sync. Was ... pretty painless? Lots of things left to do and UX feedback (discovery, showing other nodes etc.) to get from folks, but it just kind of ... works already, even when you join after the first node leaves!
-
Managed to hack #Multiplex to use #p2panda (using the GObject bindings for Go) for it's P2P playback position sync. Was ... pretty painless? Lots of things left to do and UX feedback (discovery, showing other nodes etc.) to get from folks, but it just kind of ... works already, even when you join after the first node leaves!
-
Managed to hack #Multiplex to use #p2panda (using the GObject bindings for Go) for it's P2P playback position sync. Was ... pretty painless? Lots of things left to do and UX feedback (discovery, showing other nodes etc.) to get from folks, but it just kind of ... works already, even when you join after the first node leaves!
-
Managed to hack #Multiplex to use #p2panda (using the GObject bindings for Go) for it's P2P playback position sync. Was ... pretty painless? Lots of things left to do and UX feedback (discovery, showing other nodes etc.) to get from folks, but it just kind of ... works already, even when you join after the first node leaves!
-
Managed to hack #Multiplex to use #p2panda (using the GObject bindings for Go) for it's P2P playback position sync. Was ... pretty painless? Lots of things left to do and UX feedback (discovery, showing other nodes etc.) to get from folks, but it just kind of ... works already, even when you join after the first node leaves!
-
-
-
#p2panda for syncing playback positions next? :P
-
#p2panda for syncing playback positions next? :P
-
#p2panda for syncing playback positions next? :P
-
#p2panda for syncing playback positions next? :P
-
#p2panda for syncing playback positions next? :P
-
That should make it that much easier to generate new bindings or even generate them during the build, e.g. for something like #p2panda
-
That should make it that much easier to generate new bindings or even generate them during the build, e.g. for something like #p2panda
-
Finally managed to push those two big #puregotk PRs I've been working on!
1) fixes a bug with `throws` generation: https://codeberg.org/puregotk/puregotk/pulls/46
2) makes the generation 15x faster: https://codeberg.org/puregotk/puregotk/pulls/47That should make it that much easier to generate new bindings or even generate them during the build, e.g. for something like #p2panda
-
Finally managed to push those two big #puregotk PRs I've been working on!
1) fixes a bug with `throws` generation: https://codeberg.org/puregotk/puregotk/pulls/46
2) makes the generation 15x faster: https://codeberg.org/puregotk/puregotk/pulls/47That should make it that much easier to generate new bindings or even generate them during the build, e.g. for something like #p2panda
-
Finally managed to push those two big #puregotk PRs I've been working on!
1) fixes a bug with `throws` generation: https://codeberg.org/puregotk/puregotk/pulls/46
2) makes the generation 15x faster: https://codeberg.org/puregotk/puregotk/pulls/47That should make it that much easier to generate new bindings or even generate them during the build, e.g. for something like #p2panda
