general mad scientist | electronics enthusiast | human | (he/him)
Mastodon: @[email protected]
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...
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...
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.
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.
#privacy #cultofthedeadcow #hackerfashion
www.customink.com/fundraising/...
#privacy #cultofthedeadcow #hackerfashion
www.customink.com/fundraising/...
www.customink.com/fundraising/...
www.customink.com/fundraising/...
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?
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?