Don't popular repos have like a thousand commits?
Seems excessive having to parse a thousand events just to rebuild the current state.
If a repo was its own event with updates posted in reply, a repo would have animmutable ID. This is similar to what I propose in https://github.com/nostr-protocol/nips/pull/483/commits
Discussion
Also, is there a way to get some feedback from someone who would know, say,
how big I can make a kind-0 before relays start rejecting it?
I tried tagging 4 devs but not one seems to care... I tried asking someone
who runs a relay before and got no answer.
nostr:npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr
I have found its really hard to get feedback. Its probably a reputation thing. The small number of core devs are probably tagged in more messages than they have time to read given the growth of nostr.
Working on a bounty or two might be a good way to build relationships?
Nostr is permissionless. Perhaps just broadcast a bunch of different sized messages to lots of relays under a fresh pubkey and see which ones get rejected?
There is a bounty?
I did just end up trying to see if it fails...
It went through but it has to fail at some length... Surely relays have limits...
I meant smaller bounties that you could do deliver within a much smaller time frame.
Yes. If it doesn't fail now, the features will be added to relays to block larger events if lots of them get posted.
only a subset of events would be needed to rebuild the state.