Would anyone be up to make a NIP for suggestions on client url routing standards? I think that at the begining the main clients were all forks off of branle, and therefore had the routing of
`{hostname}/event/` -> timeline view
`{hostname}/event/{eventhash}`-> thread view
`{hostname/{publickey}`-> profile view
`{hostname}/messages/{recipient}` -> dm view
I think it's pretty well structured and therefore could lead to a really nice experience of being able to just swap out the domain in order to move to a new client. I have been doing this and it is exciting to just be able to do so. I would keep it as a suggestion, but it would make linking to different clients more standardized.
javi /
npub1j6…7l7d2
2022-12-18 06:13:11
Author Public Key
npub1j6pvx0usynddkxllmamzcv2kuf454g6qm6xsdjgu55mles8akw5sk7l7d2Published at
2022-12-18 06:13:11Event JSON
{
"id": "4ca1d4f8d0e7bc0b6bc3c7eb1709cd50b8093f22042e8df3ddd0dfa9b7368001",
"pubkey": "9682c33f9024dadb1bffdf762c3156e26b4aa340de8d06c91ca537fcc0fdb3a9",
"created_at": 1671340391,
"kind": 1,
"tags": [],
"content": "Would anyone be up to make a NIP for suggestions on client url routing standards? I think that at the begining the main clients were all forks off of branle, and therefore had the routing of \n`{hostname}/event/` -\u003e timeline view\n`{hostname}/event/{eventhash}`-\u003e thread view\n`{hostname/{publickey}`-\u003e profile view\n`{hostname}/messages/{recipient}` -\u003e dm view\nI think it's pretty well structured and therefore could lead to a really nice experience of being able to just swap out the domain in order to move to a new client. I have been doing this and it is exciting to just be able to do so. I would keep it as a suggestion, but it would make linking to different clients more standardized.",
"sig": "7b0d94e3c75a845f558c37ab1953f7d3521dd40323b5d344b7a3e751fb0f47afcb56a77ffae834f25d66e78eaf5434c9ff8aa79b308ad569e3324cc25ca8a2dc"
}