I wonder what happens with most web-based clients of Nostr when you open them considering there's zero actual need for a backend for them to run as there's no hidden user/pass-based DB involved that needs protecting since everything is in the open, if they all run Nostr directly from the front-end are therefore all of them single-page applications?
Many load and feel as if they were SPAs (saying this as an Angular 2.0+ first and React second developer). They have that clunkiness, specific of a browser loading a massive bunch of node modules, and storing far too much data to show a page.
There's a reason we evolved into Angular Universal, Next.JS and many other formulas that pushed all the processing back into a server. Which is that SPA assume always
1. The browser is on a PC that has enough humph to run it all.
2. The browser doesn't have 30 other tabs open, reducing too the processing power of the user's PC let alone reducing RAM availability.
Elixir Phoenix would be ideal to build a Nostr client. I'll definitely give that one a thought once I finish comprehending the full list of NIPs.
It feels like an SPA due to LiveViews being a non-complicated implementation of sockets (yes even simpler than JavaScript frameworks) while it keeps all the processing powers in the server. Let alone you could use Oban to create user desired indexes based on multiple keywords.
I seriously need to get started with Flutter too, since I want to build a dating app, using the Nostr protocol. One where the goal is for you to delete your profile, not to keep you eyaballing and scrolling eternally to shove as many ads to you as possible.
#Elixir #Nostr #WebDev
