You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now if we put a static file containing { "names": { "team": "faf5d2e8ffb56fa201bc04cd8bf74a3e38de7d0439ada7fb15310d3d374ed5b1" } } at https://www.trustroots.org/.well-known/nostr.json it should work, it returns the same if ?name=team is added.
Maybe returning the same npub for nostr.json?name=foo is a lil tricky?
Maybe for the collective we could try to add a profile field for npub. Then we could add an API endpoint that resolves usernames into npubs and returns the appropriate JSON. Seems like quite a small change to the current codebase, but would open up nip05 options. Would lay the groundwork for simple trust verifications and so on.
Seems easy to implement early 2024:
npub field on user profile, which is not displayed initially"names": { "bob": "b0635d6a9851d3aed0cd6c495b282167acf761729078d975fc341b22650b07b9" } }
UPDATE: better provide nsecs for everyone right away
probably add another section here, replace ELSEWHERE with NOSTR:
(and NOSTR can even link to a page with apps that can use this)
The text was updated successfully, but these errors were encountered: