Careful what you wish for. 😅 nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj ??
Spam it guys, testing with nostr:npub1k5f85zx0xdskyayqpfpc0zq6n7vwqjuuxugkayk72fgynp34cs3qfcvqg2
nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc nostr:npub1t3ggcd843pnwcu6p4tcsesd02t5jx2aelpvusypu5hk0925nhauqjjl5g4 nostr:npub1jk9h2jsa8hjmtm9qlcca942473gnyhuynz5rmgve0dlu6hpeazxqc3lqz7
Discussion
Give it your best shot 😝😂 nostr:npub1k5f85zx0xdskyayqpfpc0zq6n7vwqjuuxugkayk72fgynp34cs3qfcvqg2 asked for it 😏
Hmm… don’t mind if I do
I do not believe Nostream supports cancelling queries so you could rapidly open/close subs. The event tags index is not implemented properly leading to all events with a certain tag being loaded for a JOIN. If this exceeds about 32-64MB for a single query it will start spilling over to disk and amplify the attack by wasting your resources on context switches, leading to disk IO being wasted and more CPU cycles to load/save from/to disk.
Bonus points for using IPv6 to get around ratelimits.