𝑻𝒉𝒆 π‘«π’‚π’“π’Œ 𝑴𝒆𝒕𝒆𝒐𝒓 π‘­π’“π’π’Ž π‘¨π’π’…π’“π’π’Žπ’†'s avatar
𝑻𝒉𝒆 π‘«π’‚π’“π’Œ 𝑴𝒆𝒕𝒆𝒐𝒓 π‘­π’“π’π’Ž π‘¨π’π’…π’“π’π’Žπ’† Lorena@NostrAddress.com 4 months ago
PWA sucks. Forced updates, no decentralisation, reliant on a browser to use, just a patch for those who didn't create an APK. Jumble is a great client, and indeed the PWA is very good, but it's not ideal. I prefer to use it on the PC rather than on my phone as a nice client, but not a definitive one.
↑ Parent

Replies (2)

Cody's avatar
Cody cody@jumble.social 4 months ago
There are plenty of choices, and everyone can pick what they like. I also mostly just use Jumble on desktop, haha. But I don’t really see the points you listed as disadvantages of PWAs: - Forced updates mean an early client can quickly fix bugs and ship features. You might be worried about β€œmalicious” updates, but does an APK really solve that? How many people actually review Amethyst’s source code, and even if they do, how many compile it themselves? - Jumble is a purely static site and could even be deployed directly on nostr via
nsite - Decentralized Static Website Hosting on Nostr
nsite enables decentralized static website hosting using Nostr public keys and Blossom content-addressed storage.
 . If needed, I’m sure someone would mirror it, it’s open source after all. Isn’t that actually more decentralized than an APK? - Depending on the browser means Jumble runs anywhere a browser exists. An APK, in contrast, depends on Android and doesn’t easily run elsewhere.
1 replies ↓
↑