Nice! Article didn't mention but ~/.claude/plans is where it stores plan md file when running in plan mode. I find it useful to open or backup plans from the directory.
Because the software is owned by the user - it is same as buying a music or movie CD. How long would the CD work? Here a similar question to ask is how long would the Cloud Providers be available for "lifetime"? The current supported cloud providers are Hetzner, AWS Lightsail, DigitalOcean, Akamai Linode and Vultr. They all seem to be around for quite a while and so I expect product to keep working for forseeable future by which time a user can easily get the value for the price they paid for the product.
For sake of argument for "lifetime": even if some of these cloud providers go out of business the probablity of all of going out of business is low, and so software will keep on working.
I'm also expecting new cloud providers to appear over long period of time worth adding support for.
Other than that I'll answer the questions some of which already have information on website or the installation or product walk-through videos.
how much it will cost you to run on whichever cloud you use: Hetzner being the chepeast at the moment ~$4/mo. Ofcourse your own hardware $0/mo
will this software get updates to support new API versions or other changes these clouds might make?: So far I haven't seen a cloud provide deprecate their APIs (please do provide real example if so) but this would be handled as software update
Will it automatically support new regions?: Via software updates
Will it automatically support new instance types?: Yes already supported, more info on website and product walk-through video
If you'd like to have civil discussion other than calling "scam", futher questions are welcome
I shipped desktop app for all three major OS Linux, Windows and macOS.
Because of the programming choices of Rust for application/backend and Typescript for frontend - Tauri was perfect fit for me.
So far Tauri documentation has been sufficient (and good) for me to achieve what I wanted inside the application. However, platform specific packaging required extra effort because the app required installation of system service/daemon in addition to the frontend app binary - so platform specific pre-install and post-install scripts which setup (or remove on uninstall) those daemon services were not natively supported in Tauri packaging.
You can browse the code here to see what it takes to package and sign installer for various desktop platforms: https://github.com/upvpn/upvpn-app
Yeah, you have a point. For security, implementation goes like this: the keys are generated once for a page load and are not recorded (for obvious reason - security), keys are gone after closing the browser tab, so, as far as tool is concerned keys are ephemeral. To generate new keys simply reload the page.