Nostr Web Client

The app is no longer using your NIP-65 relay list as the default relays to get your feed. This is in perpetration for using the gossip model to get the feed.

also In future updates my plan is to start prompting users to set their Inbox and Outbox relays correctly (4-5) instead of what it is right now with 20+

So now you can configure 20+ relays locally for the app to use and keep your Inbox / Outbox set to a reasonable 4-5

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

if users say "i wannan this relays" and client uses them and publishes duly

then this app is dogshit

seriously, "gossip model" is the most retarded shit and has retarded the client development because what the fuck, i publish a relay list, and then i go to another client and it goes GOSSIP fuck you

Reply to this note

Please Login to reply.

Discussion

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

i should point out that this is a big problem for relay developers

how do you find a client that is gonna actually test your relay if it's running off on its own choosing arbitrary random, probably dev chosen relays?

uh, no. respect the 65 bro fucks sake

hzrd149 1y ago

noStrudel is not using a gossip model yet. but its something I would like to implement. however whats been keeping me from implementing it is I need to find a way to ask the users permission (or make them aware) that the client is going to connect to random relays to get the feed.

Its also the reason I have not implemented NIP-42 yet. because I don't want to sign auth requests for the user in the background without at least making them aware first

atyh 1y ago

its nice to encounter developers with humility and integrity. thanks.

fiatjaf 1y ago

What is the problem of using arbitrary random or dev chosen relays? That's good.

Laeserin 1y ago

I've chosen specific relays, for good reason.