pull down to refresh
0 sats \ 4 replies \ @l0k18 1 Mar 2023 \ parent \ on: What are you working on this week? bitcoin
A http-to-nostr bridge, of sorts! Very nice. The protocol has a natural mapping in it just a matter of translating it into domain/path format to encode it. I personally favor the idea of working through working through the implementation rather than building a spec in detail first. Implementation tends to show you gotchas that you would still have to work on even if your spec seemed bulletproof.
A http-to-nostr bridge,
What I'm working on is not a bridge. Rather, these websites would exist on Nostr relays. You would post a special note (containing HTML) to several relays. Hyperlinks in that note would point to other notes (which could be on any relay). Interactivity would also be possible (I'm still working on the details of that).
I personally favor the idea of working through the implementation rather than building a spec in detail first. Implementation tends to show you gotchas that you would still have to work on even if your spec seemed bulletproof.
There isn't much to implement. HTML browsers are a dime a dozen, and any of them could be modified to access websites on Nostr.
reply
It's a namespace translation system. Effectively every link can be loaded from the local nostr node, there is not a "location" for notes. So I call it a bridge. But yes, the notes themselves are html so, idk. You could call it HTTostr or something :D
reply
It's a namespace translation system.
I don't understand what you mean by this. What I'm designing involves no translation of any kind. Moreover, there are no namespaces involved.
there is not a "location" for notes.
There absolutely are locations for these notes. The notes are posted to specific relays and nowhere else.
You could call it HTTostr or something
That name would be totally inappropriate, because HTTP is not involved in any way, shape, or form.
reply
I'm no expert on deploying distributed data networks, usually centralised clusters have to have failovers as at any given time a, potentially critical, request may fail and a whole segment of a document or a data source is unavailable. So I think it needs a DHT, at minimum, and due to the requirements, a key to URI encoding scheme.
reply