kind 3 is a bad idea due to large following lists, but 10002 was enough. more than enough.

Reply to this note

Please Login to reply.

Discussion

sure but the point stands. basic metadata has been exploded across kinds. coupled with the fact it’s on a distributed network makes the complexity so high for basic stuff. it’s like splitting your simple backend into 100 nano services 😂

you first need to use relay hints to find the 10002, then check the 10002 is up to date, then get kind 0 profile and the reply, and then get if they have a nut”zap” crap to see if you want to use nutzaps, then check if they support specialized relays for the sole fucking purpose of reaction counting so on

we just need read/write and a public/private distinction

there’s a fucking reason we have NIP-11, to announce which features a relay supports

the relay should simply say if it supports DMs or not or whatever, or even that isn’t needed. try and see, if it fails you wasted like. 5KB of data

there are only a few “types” of relay which should be a dropdown or even be specified in NIP-11.

- where I want to read from

- where I want to write to

- and if I want others to fetch/write content there (this can be in NIP-11 as “policy”, but nothing wasted)