websockets are indeed a problem for mass adoption. They don't scale well cause they take resources even when idle. I'd add a rest get API for lot of use cases, i.e. the profile fetches nip1.
websockets are indeed a problem for mass adoption. They don't scale well cause they take resources even when idle. I'd add a rest get API for lot of use cases, i.e. the profile fetches nip1.
Indeed!