Posts by bgrift
**Veilid Framework v0.5.0 is live in all the usual places!**
The changelog is too much for a skeet so here's the link: gitlab.com/veilid/veili...
New:
DHT Transactions support
Automatic default record encryption
API level improvements and bug fixes
(Thread with details)
I'm going to start live-coding Veilid on a more regular basis as we march toward a 1.0.0 release.
If anyone wants to join our Discord and follow along, feel free, the invite is here:
veilid.com/discord
And the live coding channel is specifically here:
discord.com/channels/107...
Happy Thanksgiving to those in America!
And to the rest of the world, Happy Thursday!
This year I am grateful for my team at the Veilid Foundation and all the @veilid.com contributors and supporters.
2026 is going to be a lot of work, but we got this, fam!
We are doing the thing.
Tune in to FLOSS Weekly today at 9:30AM Pacific to hear @bgrift.dev and me nerd out about the current status of @veilid.com
Hacking stuff in Las Vegas this week? Be sure to check out what EFF is doing and say hello! www.eff.org/vegas
Hey folks, we are in the final days of our summer fundraiser for Veilid! Consider getting some cool gear while helping make privacy accessible for all!
#privacy #cultofthedeadcow #hackerfashion
www.customink.com/fundraising/...
Hey Veilid supporters, we are starting our summer fund drive for Veilid Foundation. Donations are tax deductible! Help us keep spreading the word and building our community!
www.customink.com/fundraising/...
Unfortunately Veilid WASM can't run on secure origins yet, which happens to be a requirement to make PWAs installable. That will be solved once we add WRTC or WebTransport protocols.
developer.mozilla.org/en-US/docs/W...
My guess would be that you'd need to URI-encode the "did:123" part of the URL, which will replace the colon with "%3A", making it "did%3A123".
Docs for encodeURIComponent()
developer.mozilla.org/en-US/docs/W...
I've been wondering the same thing.
Interactive controls could be disabled before hydration, but if hydration fails (ex: due to runtime errors or JS load issues), then users are left with disabled controls and no hint as to why they are disabled. Might be better than interactive but unresponsive?