perhaps there's a simple fix here. the backend ser...
# graviton-browser
m
perhaps there's a simple fix here. the backend servers can advertise which frontend version you should use. so, if the user types in "foobar.com" then we do an HTTP GET to /.well-known/graviton/app-version which returns a pointer to a maven repo, and a coordinate. and then that's what's executed. if the browser can't access foobar.com then the last version that was accessed is used, but it's informed it's offline.