Thanks to nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprdmhxue69uhhyetvv9ujuam9wd6x2unwvf6xxtnrdakj7qgnwaehxw309amk7apww468smewdahx2tckuej4c for fixing my spaghetti code,  #haven can now run on a 1 core / 1gb ram VM

VMs like this cost less than a blue check...

If you ran the import previously, you'll need to run it again (sorry lol)

github.com/bitvora/haven


:thugamy:


Brilliant. Bravo.


Also, my procrastination has now paid off.


You rocked it out with this relay implementation!


Gonna try it!


Onward 🫡

Onward 🫡


Can we get similar improvments to wot deployment? 😬


The latest should be much more stable than before but wot relay is processing so much more it needs at least 2 cores and 2gb of ram minimum


Latest release or whatever is in main?


Whatever is in main, basically the badger DB update


yeah, making them into separate listeners would work better, each on a different port, then you can reverse proxy them to subdomains


Alright, lets see what happens. Ill turn notifications back on for nostr:npub1wsguarddmjs97h4m026fsmv5974jk2s2rgu2urt7remjz9nnah0qq2mlse and see if they relax


Sorry, you mean "master".


Get a cheap VM for sats at https://lnvps.net/ (not my service).


My fault. I started it by saying 'main'


Looks like they're integrating nostr. Love to see it


Haven looks awesome, I have a question though, is it available at a single url and adapts policy based on auth? Or is it available at multiple urls for use in different client settings? The "Four Relays in One" bit confused me.


Different endpoints have different policies

/private uses auth, only you can access
/chat uses auth, only your WoT can access
/inbox only your WoT can write, anyone can read
/outbox only you can write, anyone can read


And for /inbox only notes you are tagged in


bitlaunch.io also accepts bitcoin


Got it, you might add that information to the readme. Any particular reason you decided to use paths? In the past this has resulted in a single client being unable to deduplicate connections to a single logical server, sucking up resources unnecessarily (nostr.wine/pubkey being an example).


I don't like the 3 dot subdomains and see that as bad client design, they should fix it :)


this is a good question. 👍


Why would that be better?


What about putting them all in the same domain, all at the root path, using https://khatru.nostr.technology/cookbook/routing?

Not saying this is the best idea, I have nothing against paths -- or subdomains.


But in this case they are really different.


Clients should all be fetching only from my outbox to get my notes, my inbox/private/chat is only used by me, so shouldn't be any issues on resources


This actually could work but it's almost too smart/magical, I kind of like the idea of them feeling more distinct (I think)


Could it be spammed by a bot tagging the owner in many notes?


Only if the bot is in your web of trust


Ok I see. So only tagged notes will enter the relay if they are from somebody in the WoT. Thanks!


I see what you're saying now. It is potentially possible, but I do like it like this, I think it encourages clients to do outbox/inbox more by having more distinct relays for each job, also don't wanna use auth for all cases like just reading my outbox