Alex Gleason

I [changed](https://gitlab.com/soapbox-pub/nostrify/-/commit/027e8cd98527e04f126eff25ee28d893a6c569e5) my NIP-05 function to not parse the full document, but instead assemble the pointer and then parse/validate that instead. So as long as I can access the specific...

I think it depends on who we're trying to target here. For mainstream adoption, I don't see people managing petnames or even understanding how they're supposed to work. NIP-05 is...

Agreed, see: https://arethetypeswrong.github.io/?p=pino%409.6.0  More info: https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/docs/problems/MissingExportEquals.md

I agree with @staab ActivityPub has Question and Answer types. We should do that.

> Which event kinds do you use? I haven't implemented it on Nostr yet, but I have a whole UI ready to go for polls once we decide the data...

I am kind of against this. IF we do it, we should use `nostr+:` eg `nostr+1:` as the protocol, so it at least matches the existing URI standard of [`web+`...

Relays are URLs. URLs must have a path. Without the path it is an "origin" not a full URL. I worked around this by normalizing both URLs before comparing in...

It's because of this: ``` > new URL("https://example.com").href "https://example.com/" ``` Also, "https://example.com/relay" is not the same URL as "https://example.com/relay/" and could actually be a completely different relay

I don't know, but I am very convinced it's wrong. I'm hitting the same issue in Elixir. URLs have paths.

RFC7235 talks a lot about origins, but the "u" tag is a full URL