0 sats \ 7 replies \ @k00b OP 27 Jun 2023 \ parent \ on: Booger Pro free relay is live nostr
You mean run your own instance? Because you want to custody your own notes or custody them for other people.
It's just a prototype so I'd only really recommend using it for local dev right now until I fix all the bugs it probably has.
write
preview
0 sats \ 6 replies \ @franzap 27 Jun 2023
Sorry, I was not clear. What I meant is why should I run it vs other relay implementations? As I clicked on the website and saw no info. But then I saw it explained on the repo README
reply
0 sats \ 5 replies \ @k00b OP 27 Jun 2023
Yeah idk tbh. It has a different architecture and aims to be a little more extensible. If you're happy with other implementations, I'd run those. They've seen more real world usage.
The goal was to create what I want in a production relay implementation (and in a lot less code).
reply
0 sats \ 4 replies \ @franzap 27 Jun 2023
That's great man, it looks awesome and Deno must be fun. I started writing a browser-based relay (on Sqlite WASM running on OPFS), to which I want to add a sync layer to power more offline scenarios – especially now with PWAs being all the rage
reply
0 sats \ 3 replies \ @k00b OP 27 Jun 2023
Oh sweet! Do you have the code hosted somewhere?
I was hoping booger could eventually be a relay in the browser for offline usage and for a cache that worked like I was communicating with a relay.
reply
0 sats \ 2 replies \ @franzap 27 Jun 2023
When I said started writing I literally meant it. It's just a bunch of ideas and pieces of code.
a cache that worked like I was communicating with a relay
Exactly my goal!
Honestly if booger aims to do this it might be more productive to contribute to it instead. You probably know way more than me about relay internals.
What was your plan to make it work in the browser? Postgres WASM? (I thought this going to be a joke but it actually exists)
reply
331 sats \ 1 reply \ @k00b OP 27 Jun 2023
To booger work in the browser, we'd have to:
  1. move note storage into a booger plug so that we could swap out postgres and swap in something more suitable for the browser (either sqlite wasm or dexie or something)
  2. create some abstraction around the http server such that it could be swapped out for some other communication mechanism
If I were to begin working on this today, I'd just create a booger fork that could run in the browser, then work towards (1) and (2).
reply
10 sats \ 0 replies \ @franzap 27 Jun 2023
Super interesting. I'll have a look later
reply