Thread

Well said

Primal?

The first time I sent a note from nostrudel running on local host totally blew my mind.

These are not just clients, they are tools like a metrics dashboard, search engine, and remote signer. But yes, there needs to be a way to access these tools that doesn’t depend on DNS and hosting providers.

This is the way @fiatjaf

yes, we should go back to http, and make the encryption protocol level :p

🔴 Muslims follow all prophets and messengers, peace be upon them ⚠️ God has said in the Quran: { They say, "Be Jews or Christians [so] you will be guided." Say, "Rather, [we follow] the religion of Abraham, inclining toward truth, and he was not of the polytheists."( 2: 135 ) Say, [O believers], "We have believed in Allah and what has been revealed to us and what has been revealed to Abraham and Ishmael and Isaac and Jacob and the Descendants and what was given to Moses and Jesus and what was given to the prophets from their Lord. We make no distinction between any of them, and we are Muslims [in submission] to Him." (2:136)}

those can run - own relay - own app server - use own browser mobile / pc need nothing else - POWER + INTERNET and npub to read/post that simple

Perhaps the old IRC could inspired?

Web apps are just as "real nostr clients" as any other app. They all requires servers one way or another, and if a relay doesn't update their certificate, no data will flow, no matter if your app is deployed from a centralized corporate approval system (Play Store/App Store), that can wipe your app off the earth by will, or if your app is downloaded from a git repo or web server to be installable, or if it's retrieved using web technology. There is also a big difference between a client web app and server web app. Any server web app has an online dependency. Any client web app is just like any other native app, just using web tech for rendering.

The whole debate is mixing up two different issues: protocol design and reliability of the surrounding infrastructure. From the reliability perspective, it does not matter whether the client is a native app, a web app, or a “pure” static Nostr client – you always depend on some combination of relays, DNS, TLS, and distribution channels for the client itself. ​ Even if you run your own relay and connect directly by IP, you usually still want authenticated, encrypted transport, which means certificates of some kind. If you use self‑signed certificates, you lose the usual WebPKI trust guarantees; if you use CA‑issued certificates, you inherit the same centralization and expiry risks as any other TLS‑protected service. Either way, the problem is not “web vs native” but how much you trust and can operationally rely on these components staying valid and reachable. ​ Web clients that are static (HTML/JS/CSS only) and talk directly to relays are, in that sense, “real Nostr clients” just like native apps: they hold keys locally, speak the protocol, and connect to relays without an app‑specific backend. The practical question is how to minimize centralized points of failure (DNS, single relay, single app store, single certificate chain), not to argue that one UI technology somehow magically avoids the need for trust, certificates, or servers altogether.