You can test myrelay.page before you build and deploy. You can even edit the configuration from the demo page. Note: Only works for wss (secured) relays.
Thanks! While that may appear to support many cases, it doesn't support the case where a relay isn't at root (in a subdirectory). Unset url case is handled here:
https://github.com/sandwichfarm/myrelay.page/blob/main/src/lib/core/MRP.ts#L119-L128
It additionally handles potential issue where someone attempts to connect to `wss` from `http` or vice-versa (would throw client-side errors) by clamping websocket/http SSL in alignment with browser limitations, which is implicitly compatible with onion.
Coracle stripped the line number hash on me `#L119-L128`
Thanks! While that may appear to support many cases, it doesn't support the case where a relay isn't at root (in a subdirectory). Unset url case is handled here:
https://github.com/sandwichfarm/myrelay.page/blob/main/src/lib/core/MRP.ts#L119-L128
It additionally handles potential issue where someone attempts to connect to `wss` from `http` or vice-versa (would throw client-side errors) by clamping websocket/http SSL in alignment with browser limitations, which is implicitly compatible with onion.
Ok, I think I understand. In general, you shouldn't have to set the URL. It handles detection and handles both ws (necessary for edge-cases and onion relays) and wss in the url setter. There's no harm in setting it manually ofc, but it's an unnecessary step.
wanna send a gist or a patch? not parsing well in client?
awesome! General config + theming coming soon.
what if... (and you probably know what I'm going to say...)
we publish these features on nostr.
Say for example I add "pin-note" support to nostr:npub1w0rthyjyp2f5gful0gm2500pwyxfrx93a85289xdz0sd6hyef33sh2cu4x
I publish a new event kind tagging my NIP-89 entry of Highlighter. Thus I signal that Highlighter supports that feature.
That way, say for example I later add "mute-list" support; I could just publish the event.
There is NO WAY someone, not even nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5 , will be able to keep up with all the clients and all the features we are all constantly pushing.
But we can push it to the edges, me as a developer, it is basically no extra work to publish an event indicating the new feature when I cut a new version.
yes.
for the record, I was joking https://emojipedia.org/face-with-tears-of-joy
It's the hole in the wall that gives you internets.
totally funtional government
it wasn't loud enough so I'll say it again tomorrow
https://cdn.satellite.earth/fa25bb879a2b5d56d42b84a183caeb1b0813ba348988a6a7c9b318af5ef8dc2f.mp4
lol
