But bro, personalization bro. We need your relay list bro. We need your outbox relays bro.

Yeah iv wanted to suggest changes to the NIP07 api so that client's could just pull that data from my extension to be authoritative. Most clients either use hard-coded relays, or pull from nip65 (which is fine imo) but If I have an extension, that should ALWAYS be authoritative, but few clients, if any use that model.

i've thought about having the ability to shim in proxies for relay connections to intercept them on behalf of the client for user's privacy. So many clients just open shit loads of connections to hundreds of servers/relays without asking me permission. I have to use other extension like uBlock to help keep all of those requests down.

Reply to this note

Please Login to reply.

Discussion

Yeah, I often have the console open, from testing Alex, and then I switch to other webpages and it's just a flood of relays. This doesn't happen with us, because our relays are aggregators, and we always look at them first, and only check other relays if we can't find something or the person is logged in and has explicitly said for us to check their preferred relays.

And the personalization thing doesn't even count, as you can just login npub-only (read-only) and I can fetch your relay list and app settings from theforest.

You only need to login, to sign, and apps should reduce their reliance upon signing.

I have to sign on Jumble, everytime I look at the notifications, as he uses events to keep track of what I've read.

I really hate that.