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/...

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?