I'm launching a new thing. It's very early stages, but it is building off the work I've already done with feedbuilder. If damus relay is indeed dying out, you're going to want this. Because it will keep you hooked to the network in the aftermath. And right now, I don't even have payments hooked up, so you can try it out for free if you want. #grownostr #relays

Replies (17)

I took a different approach to this three years ago with multiplextr. Ultimately, someone has to handle the heavy loading stuff, which sort of pushes us towards bluesky's central relay/appview model in terms of censorship. But at least it's optional. The main problem with this is either the client or the relay needs to handle outbox, but not both — people used to put nostr.wine relays in their inbox/outbox relay selections, which just messed everything up.
So I could remove the inbox relays from my list except this and it'll serve up content from all my follows? And then I can maintain my own personal relay as a singular outbox relay, in theory? Sorry if the questions are a bit nooby I'm just trying to work my head around how it's all working.
I would not remove any of your current relays, you can add this one to your list and if your client (like Damus IOS does not support outbox) then you will not miss anything from your follows.. That is the idea, still in-progress.. More updates to follow.
Bullish on all the building in the wake of some big relays going down. This is how we win. #grownostr image
cloud fodder's avatar cloud fodder
I'm launching a new thing. It's very early stages, but it is building off the work I've already done with feedbuilder. If damus relay is indeed dying out, you're going to want this. Because it will keep you hooked to the network in the aftermath. And right now, I don't even have payments hooked up, so you can try it out for free if you want. #grownostr #relays
View quoted note →