Those guys of course. Though you could make a technical argument that something like Ed25519 is a better choice for this kind of use case. Or ML-KEM for interop with Chrome's post quantum hooks. Or this or that.
Anyway, we're not talking about reinventing the whole internet based on secp256k1.
Right?
I wasn't. I was just talking about hosting Nostr clients in a way that is independent from domain names.
If your client is just client-side assets these can be hashed and downloaded from many different places, they don't have to come from one canonical URL controlled by one guy.
That part makes sense.
But how would you make a nostr metrics client? If I remember right Artur was from a web-crawling background and made is own nostr crawler from scratch.
Or you mean just for publishing, like writing daily stats events to the relays?
No, the metrics and search stuff are unrelated, these definitely require special servers.
But I think the main note was about nsec.app, or maybe I misread.
In any case I wasn't talking only about that, that was just one example, my point is valid for many other cases.
