>How are the security issues regarding knowing that you're always running that code and that the server isn't compromised and sending altered code? A unique so

>How are the security issues regarding knowing that you're always running that code and that the server isn't compromised and sending altered code? A unique solution might be to use service workers to handle content "updates". The assets could be cached locally, and a single network request could be fired to check for updates. If one exists, the user is prompted to update. This would at least alert you to review the code being sent to your browser if you're so inclined. Ultimately though it comes down to yet another tradeoff of security vs convenience. Such a feature might be better off as an opt-in extra security feature.