Replies (26)
it's getting too complicated
We need to make it complicated before we can simplify it.
How will that be on battery use lol... imagine when someone gets their app relay hammered with REQs
It's an online relay. You just deploy and control it from the app.
Oh gotcha, thought the relay was in the phone... who's infra is it leveraging?
We should be able to use any VPS out there. They all have APIs.
Is this worth the performance/UX tradeoff?
Nostr reduces app risk in a different way than “perfect sovereignty in every client.”
It reduces risk through exit.
Because users can verify, compare, and leave, **the ecosystem** can be safe enough even when individual clients are imperfect…
We will see... All I know is that I didn't join Nostr just to build another Twitter - centralized in the app's own servers.
Use a different client then
Don't you make a one-click easy to deploy CloudFlare relay 👀
They have an in-phone relay over Tor, I thought. This seems to be a relay launcher.
Sure do... but Vitor said no "centralized" so I suspect that would mean self-hosted homeserver only and no VPS provider such as DO, Linode, Google, AWS, Cloudflare, etc...
I see my relay monitor 😍
Generate more interesting info about the relay.. these reports are too dry.. we already know most if it from nip11s.
I see my relay! 🤩
i see fiatjaf needs better nip11s! 😅😁✅
I'm still waiting for a relaytools name field, too (you told me to remind you 🫠😅)
ahh yesss, hehe, ok im putting it on my liste now for a hopeful tomorrow 😁
Yeah, I'm working on it, today. Want to monitor all of the relays, as well, and not just one set.
oo nice, yeah if you have classifications for any of them, that's what i think will blow everyones minds (eg. look for PrivateInbox or Directory) 👀
How can I tell If they have a limited kind list, or no AUTH but with whitelist? I always have to add 5 randoms, to make sure at least 1 works. Effective, but not very efficient
Should I just have an automated test run over each, trying stuff out?
Oh, yeah good questions.. I was kind-of just doing a more human type tagging, like tagging the relays I know about that are "good for Directory" purpose or etc, even if I don't run them, just to help discovery.. I also really dislike the wording on nip11 and clients saying "payment required" vs "payments accepted". Same for auth, "auth required" vs. "auth capable". We've evolved so far past nip11 and relays being just one single dumb thing. The relay may accept payment, but that does not mean it requires it to use.
So yeah, if you're automating, it might take some kind of testing of the relay capabilities, or if you have nip86 access you can pull allowedkinds that way (but that requires the access which is usually only owners and mods).
I don't really know how you'd do this for random relays.. That's why relays should all have their own monitors, where the operator can at least seed some of this info.. (or fix/augment their nip11s)
Keep going, into the fog of war 🤙
LOL Broodje Zeedijk IYKYK 😅
