Wow! This is great stuff! Really appreciate you taking the time to lay this out.
I get your point: in high-stakes, security-conscious environments like yours, needing a persistent internet connection is a non-starter. Your two conditions (sync only on verified safe networks + trusted server endpoints) are a clear, actionable framework I hadn’t articulated so well before-thank you.
Cheers for calling out the muddiness around purpose. I started this as a tool to scratch a personal itch, but I’ve been deliberately open-ended in trying to understand where others see value. Still, the lack of clarity does become friction-especially when account creation is required up front. I’ll be rethinking that flow and messaging.
Also noted (and agreed) on the accessibility issue. I’ll fix the <button> vs <a> problem-thank you for catching that.
what would a deployable/self-managed version for an environments like yours look like?
Wow! This is great stuff! Really appreciate you taking the time to lay this out.
I get your point: in high-stakes, security-conscious environments like yours, needing a persistent internet connection is a non-starter. Your two conditions (sync only on verified safe networks + trusted server endpoints) are a clear, actionable framework I hadn’t articulated so well before-thank you.
Cheers for calling out the muddiness around purpose. I started this as a tool to scratch a personal itch, but I’ve been deliberately open-ended in trying to understand where others see value. Still, the lack of clarity does become friction-especially when account creation is required up front. I’ll be rethinking that flow and messaging.
Also noted (and agreed) on the accessibility issue. I’ll fix the <button> vs <a> problem-thank you for catching that.
what would a deployable/self-managed version for an environments like yours look like?