would be nice if nak.nostr.com would link to nostr.com
i.e. if I write hex 8175ceee2524b1a3828bb584480ba88c3e3d3dc88e85c7efc31aa8f87ae13bac, then the nprofile encoding could link to nostr.com/
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6
Can you please fix nostr.com?
What happens? 😬
301 to bluesky.com?
I mean the previews are not always working, it's hard to debug and I'm lazy.
I know, tongue-in-cheek
it's golang, I haven't used go in ages; maybe something for nostr:npub1mygerccwqpzyh9pvp6pv44rskv40zutkfs38t0hqhkvnwlhagp6s3psn5p once he finishes nostrocket in two weeks?
What's the problem, and where is the repo?
https://github.com/fiatjaf/njump
The problem is that sometimes fails to load events, but when I try locally it always work.
Should we really create this kind of hardcoded centralized entities? Feels like a bad idea to me. What about NIP-89?
I like that nostr.com gives me the JSON very easily (the 10% of the time it works 😂)
if I see an npub on nak.nostr.com I probably don't want to just see their profile but their kind 0 event
the part where you link it to a nostr:
I should publish nostr.com as a NIP-89 app.
