Also, it looks like v0.5.0 of @VeilidNetwork is in the process of dropping. I haven't been able to update it on my Ubuntu box via apt yet, but I figure it'll take time to propagate out to all the appropriate repos and whatnot and become available for casual upgrade.
It's a pretty significant upgrade with a lot of breaking changes, so #VeilidNodeOperators should take note and keep an eye out.
Rumor has it that an updated #veilidchat beta will "follow shortly, taking advantage of the upgrades to the framework". Hoping that these updates to the chat client will make it more reliable on Android! 馃
Keep an eye out, kidz! Exciting times!
https://masto.hackers.town/@VeilidNetwork/115760652908742507
**Veilid Framework v0.5.0 is live in all the usual places!** The changelog is too much for a toot so here's the link: https://gitlab.com/veilid/veilid/-/blob/main/CHANGELOG.md New: DHT Transactions support Automatic default record encryption API level improvements and bug fixes There are many breaking changes in this release so if you update your headless node and start seeing a bunch of punishment logs, this is expected and in some instances a good thing.
#stigmerge #flutter app is coming along! Just figured out how to wire up the Android initialization in #veilid core.
Follow along at https://codeberg.org/cmars/stigmerge_ui if you like. If you can build #veilidchat you might be able to build & run this.
Fair warning it's super unstable and I've only tested Android & Linux so far.
Playing around with @coagulate this evening/morning with the CI fam, and it prompted a question about #veilid
Does the 'network' hold onto a copy of data-in-flux? Or do we both need to have our (in this case) Coagulate app open simultaneously in order to sync contact information (or location information, as the case may be)?
Same question I guess for #VeilidChat; If someone sends a message and then closes the app, and then the recipient opens their app, will the message show up?
One day I'll get around to understanding how Veilid works, but in the interim I'm going to lean on the fediverse 
So #veilidchat and @VeilidNetwork server received big updates, and the #velidchat 0.4.8 finally hit the Android platform and I've been playing around with it this morning.
Chief among the updates for me is that hitting the back button no longer makes the app crash! It's still a bit slow due to the lack of node density, but the chat interface has been reworked slightly and it seems to be more stable and reliable.
I'm still having some trouble connecting with folks that seem to be further away from me, so I don't know what that means, but the app is slowly getting to be more solid and it's been fun watching it grow.
If you haven't updated it in a while, give it a go and give it a try! The more people that use it (and run veilid-server nodes!) the better it will get!
New commit in Veilid: Merge branch 'feature/veilid-features-api' into 'main'
Add veilid_features API and logging
See merge request <a class="gfm gfm-merge_request" href="https://gitlab.com/veilid/veilid/-/merge_requests/401" title="Add veilid_features API and logging">!401</a>
https://gitlab.com/veilid/veilid/-/commit/059b21dc8a1d59ee569290b928e626c2dfd9ae5d
New commit in Veilid: Merge branch 'feature/wasm-example-bench' into 'main'
Add test-bench example for veilid-wasm
See merge request <a class="gfm gfm-merge_request" href="https://gitlab.com/veilid/veilid/-/merge_requests/397" title="Add test-bench example for veilid-wasm">!397</a>
https://gitlab.com/veilid/veilid/-/commit/ec887d3becdd11a0cf47db756bd8dce06cba8751