i am going to take the plunge and learn me some javascript web app dev
forking #jumble https://github.com/mleku/jumble and not going to do any features or anything at this point, just going to spend some time studying how this thing works and where everything is inside it
i may end up adding features once i am confident with understanding how this stuff works, but probably i think i want to more focus on creating a web UI that is deployed by the relay at its root address when there is no websocket upgrade or nip-11 Accept header, and lock it down to the relay's own feed plus doing the "following" which will fan out to other relays and cache queries.
this will also let me do something i have been thinking a lot about lately, the idea of creating a proxy function that lets the client auth to other auth-required relays either the user's relay list items or those listed for in/outboxes of user's followed. it will basically be a proxy that pretends to the client that it is the other relay, so it requires pieces on the back end to add a new event kind or something that initiates connections out to other relays but then once the socket is authed, the relay takes over and pulls data from the other relay and caches everything that the user requests over this socket by saving it and then connections from the client direct to the relay will find these events
it's a bit complicated, and i have to work on figuring out how that will work exactly, but auth proxying by relays is an essential part of solving teh problem of eliminating redundant repeated requests for results that drains bandwidth on clients, and slows down the process of fetching results especially for outbox model. yes, it may also involve a special type of request that also applies to non-auth-required outboxes and inboxes of other users, so if you post an event to the relay, it will also propagate it to the other relays in your list automatically, and enable the authing where that is required.
mleku
npub1fj…mleku
2025-06-05 09:58:27
Author Public Key
npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmlekuSeen on
wss://theforest.nostr1.comPublished at
2025-06-05 09:58:27Event JSON
{
"id": "2fe1ed1d510cc6f0ea7393357733db332e3bd7dbf0fd2d622c5244b7aed7675c",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1749117507,
"kind": 1,
"tags": [
[
"t",
"jumble"
]
],
"content": "i am going to take the plunge and learn me some javascript web app dev\n\nforking #jumble https://github.com/mleku/jumble and not going to do any features or anything at this point, just going to spend some time studying how this thing works and where everything is inside it\n\ni may end up adding features once i am confident with understanding how this stuff works, but probably i think i want to more focus on creating a web UI that is deployed by the relay at its root address when there is no websocket upgrade or nip-11 Accept header, and lock it down to the relay's own feed plus doing the \"following\" which will fan out to other relays and cache queries.\n\nthis will also let me do something i have been thinking a lot about lately, the idea of creating a proxy function that lets the client auth to other auth-required relays either the user's relay list items or those listed for in/outboxes of user's followed. it will basically be a proxy that pretends to the client that it is the other relay, so it requires pieces on the back end to add a new event kind or something that initiates connections out to other relays but then once the socket is authed, the relay takes over and pulls data from the other relay and caches everything that the user requests over this socket by saving it and then connections from the client direct to the relay will find these events\n\nit's a bit complicated, and i have to work on figuring out how that will work exactly, but auth proxying by relays is an essential part of solving teh problem of eliminating redundant repeated requests for results that drains bandwidth on clients, and slows down the process of fetching results especially for outbox model. yes, it may also involve a special type of request that also applies to non-auth-required outboxes and inboxes of other users, so if you post an event to the relay, it will also propagate it to the other relays in your list automatically, and enable the authing where that is required.",
"sig": "5392c1c7bdf4423770b6a8d5328a6c8dfe80eb1d8e0a0ea8bea7e4e6bdfa9793d72652224e7f7b91549e263292ff3f052042490a334bf4b79dcd3614daaced7b"
}