local relays definitely are a thing. especially they should have little crons that fetch from other relays. and also there is a great need for inbound routing so users can also have their frens write straight to their relay.
some of these obstacles are systemic issues on the internet that bias against p2p, and most p2p protocols are quite deficient, but largely because of the restriction of routing.
I'm focused on everyone having a local, personal relay that aggregates across a filter, and background-syncs with their client, and remote community relays, and some big search relays.
And the local relays on different devices talk to each other over Bluetooth, WIFI, or remote relays.
I find lists interesting for bookmarks and categorizing npubs, but labels and badges might do that better, so I'm implementing both.
Labels and badges, yuuuussss!
it reminds me, that would be a neat thing, a service you pay a little rent like $2/month and your personal local relay has a custom wireguard style VPN client that uses your nsec for its encryption. i'm pretty sure p256 keys at least (secp256r1) already can be used and 99.99999% of valid secret keys for secp256k1 are valid for p256. this would simplify configuration a lot. you configure the relay with your nsec and the VPN endpoint and you get a username.example.com subdomain.
i could build something like this to add to realy in a matter of a week or less. in fact, i already have a http reverse proxy that could be extended to add a user database that fetches from the service's relays to configure npub->name using nip-05 and that username would also be your subdomain. just probably need to have round-robin DNS to run multiple endpoints and configure the multiple endpoints in the relay and it would switch to another one if it couldn't reach the first option.
if only i had the resources to build this. i do hope i don't get stuck without a serious job prospect by the end of next month, i'm gonna be in a pickle.
That was supposed to be 🫂, sorry. Emoji fat-fingered typo.
Didn't nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl implement something like that?
he did, but i wouldn't want to run a javascript based relay when i have my own perfectly good relay. plus i already have a customised reverse proxy so a lot of the parts required already exist, just needs a bit of glue to join it together and make it easy to install and use. it could directly use your nostr identity also, to make things even simpler. some kind of 30k series configuration kind that is marked privileged that the relays on the connectivity services use to set and read your configuration and subscription status and whatnot.
it's probably a month's work for me to do it. i'm gonna think about it, since i can't be job hunting all day long since there isn't even that many realistic job options for me anyway.
