Nostr View

mleku @mleku - 2d

yes that's how i do it also, https://n.mleku.dev/.well-known/nostr.json i should just point out that it's a hyphen not an underscore https://n.mleku.dev/.well_known/nostr.json => 404 this is my names object: {"names":{"_":"4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f"} there is no space in that for a path separator aside from the key string if i am running a git-http service, i tried to do this, it's a serious PITA and the documentation is awful, but the point is related to how you translate that USERNAME for the web server, and how does the web server use that to differentiate same named repos from different users, it's just simplest, IMO to just make it a path prefix eg: https://example.com/lez/somerepo because nip-05 only gives you https://example.com there is no space in the json to specify any detail about anything other than the name match itself, and the pubkey you could use the pubkey as a subpath also, you could put it in a header, this is http, maybe you guys are just not familiar with the retardation of http

0
0
3

mleku @mleku - 2d

yes, but that resolves only to an NPUB hex pubkey, not a URL this is for a git-http service right? why leave this unclear, make an exact specification how the name goes into the path that is resolved, and it should be a path, not a subdomain, because not everyone has *cough* wildcard certs (and letsencrypt are bitches about ratelimiting)

0
0
3

mleku @mleku - 2d

i can't believe you don't get it the URL format is fine, good but the semantics of [email protected] is entirely dependent on the protocol, and it's two pieces, the router, and the server how does the username relate to the nip-05 json and the - optionally - npub (the name is unique anyway) just define a mapping, and nobody screws it up if you are gonna leave that thing open you are inviting trouble but idk what to say i ported a C implementation of the hamming code and i had a lot of trouble imputing the ACTUAL type that was being used by the compiler so that my code produced the same result, in Go, you don't implicit type casting, it has to be explicit this is exactly the same kind of mental model issue you are demonstrating, typical C programmer, you have some mapping in your mind, but you won't say it if you don't, have fun supporting irritated devs using more strict typed languages, you thought this evening was fun, hahaha i'm done, gonna sign off on this

1
0
3

mleku @mleku - 2d

don't just submit to the stupidity of arbitrary nonsense recommend... in RFCs they use the SHOULD verb a lot for this case, meaning this is preferred because it maes implementation more clear and differences in implementation should be avoided if possible, because they lead to remapping errors, so define a standard mapping, and you will have no problems with people who want to use apache vs nginx or their own homespun golang or C http server

1
0
3
Showing page 1 of 1 pages