From 33953d6b9ed99d8da07006230d97eb527287a7f6 Mon Sep 17 00:00:00 2001
From: fria <138676274+friadev@users.noreply.github.com>
Date: Thu, 21 Nov 2024 13:46:32 -0600
Subject: [PATCH] add server info

---
 blog/posts/pwa-vs-iwa.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/blog/posts/pwa-vs-iwa.md b/blog/posts/pwa-vs-iwa.md
index 52e47f4d08..949b557528 100644
--- a/blog/posts/pwa-vs-iwa.md
+++ b/blog/posts/pwa-vs-iwa.md
@@ -14,4 +14,6 @@ license: BY-SA
 
 The concept of a Progressive Web App is enticing: an app using web technologies that’s inherently cross platform (since it runs in a browser) and acts like a native app, even working offline. Support in traditionally locked-down platforms like iOS means that PWAs can give users the freedom to install apps without having to go through Apple’s App Store.
 
-Attempts at similar things have been made before, notably the infamous Electron allows developers to easily create cross-platform apps by essentially bundling the browser in with the app. This has its drawbacks, though. Browsers have huge attack surface so it's important to keep them updated, but many Electron apps ship outdated versions, leaving those apps vulnerable. 
\ No newline at end of file
+Attempts at similar things have been made before, notably the infamous Electron allows developers to easily create cross-platform apps by essentially bundling the browser in with the app. This has its drawbacks, though. Browsers have huge attack surface so it's important to keep them updated, but many Electron apps ship outdated versions, leaving those apps vulnerable.
+
+So why isn't every app shipping as a PWA? The answer is an old problem with web content: the fact that you have to trust the server every time you use it.
\ No newline at end of file