Different endpoints have different policies

/private uses auth, only you can access

/chat uses auth, only your WoT can access

/inbox only your WoT can write, anyone can read

/outbox only you can write, anyone can read

Reply to this note

Please Login to reply.

Discussion

And for /inbox only notes you are tagged in

Got it, you might add that information to the readme. Any particular reason you decided to use paths? In the past this has resulted in a single client being unable to deduplicate connections to a single logical server, sucking up resources unnecessarily (nostr.wine/pubkey being an example).

I don't like the 3 dot subdomains and see that as bad client design, they should fix it :)

What about putting them all in the same domain, all at the root path, using https://khatru.nostr.technology/cookbook/routing?

Not saying this is the best idea, I have nothing against paths -- or subdomains.

This actually could work but it's almost too smart/magical, I kind of like the idea of them feeling more distinct (I think)

agreed. domain/app is more natural than app.domain and requires less dns config/certs

this is a good question. 👍

But in this case they are really different.

Clients should all be fetching only from my outbox to get my notes, my inbox/private/chat is only used by me, so shouldn't be any issues on resources