Nostr Web Client

everyone who doesn't have it? maybe first ask "do you have these id's? respond with list of NOES matching sequence plz"

we can argue all day long about broadcast mechanisms but if the origin is the original origin then definitely you want to broadcast them

group messages, maybe you want to only send them to group relays, but kind 0, 1, 10002s and all those other fun public things should be sent everywhere from the first second, second round, shouldn't be necessary if first round worked

when i say broadcast in practical terms that means epidemic transmission, meaning that you send them to several nodes, and say "plz share" and they send them to several nodes until everyone sez "stop sned plz"

Reply to this note

Please Login to reply.

Discussion

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

also, git r done with making relays that can keep the newest stuff new and not blow up their disks by not pruning off boring and old shit

fiatjaf 1y ago

Why do everybody has to see everything? This makes no sense and is not scalable. You just put your stuff in some servers such that others who are interested in them can go and ask those servers.

fiatjaf 1y ago

The primary assumption of Nostr clients should be that relays will reject your events by default.

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

that is pretty ridiculous, especially if the client just authed to the relay as a paid up customer

fiatjaf 1y ago

Of course in that specific situation the default assumption doesn't apply. I mean when you know nothing about a relay and you just got it from the nostr.watch API, for example, then there is no point in even trying to send stuff to it.

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

so NIP-11 was just pissing in the wind then? because you can't trust it?

you should read some bitcoin code especially the section about version codes and capabilities

fiatjaf 1y ago

You definitely can't trust it, but you could still use it to orient yourself.

Versioning and capabilities are a shitcoin, manual hardcoding is the only way.

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

so what's your position, seems like you want to agree with whoever is posing the question

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

seriously, this is well established protocols on network protocols since forever

i don't think you are stupid, because i read your code and i assume you wrote it who types right now but you clearly have holes in your understanding, and a lack of courage to stand by positions

you won't get anywhere long term if you don't stand for yourself at least

MichaelJ 1y ago

This is a hot take, but I'm listening... 👀

sandwich 1y ago

yes!!!!

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

it's scalable because it only has to apply to current data, so old stuff can be reduced in its replication count, relays don't have to store everything, they just have to be ready to deliver what people ask for, and what is new

fiatjaf 1y ago

You know you're describing how Farcaster works? They have a requirement that nodes store everything, and they have it hardcoded that stuff older than whatever time can be deleted.

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

so because stupid people have some elements of sense throw out the sense with the stupid?

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

also, none of this stuff is new

cache management should be standard procedure for an unbounded level of data storage

the disk doesn't magically grow in size bro