Good question
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgewaehxw309aex2mrp0yhxummnwa5x2un99e3k7mf0qyt8wumn8ghj7ct8vaezumn0wd68ytnvv9hxgtcpz9mhxue69uhkummnw3ezumrpdejz7qgwwaehxw309ahx7uewd3hkctcqypftfgrkhjammsap4marwdvpdnm5nya3hrdjq2cpezputzl8ltvt6yl64du you're aggregating NIP70s. Seems sort of pointless. Or is there are use case for that?
Discussion
Well, aggr requires AUTH, right, so you should only be serving them up to the original pubkey. But that means they author can't use aggr to see the rest of the "-" thread, so it's not really useful.
Will fix eventually. Currently busy doing distributed systems
Yeah, no rush. It's public data.
Working on cursor queries currently. Instead of having to do created_at based pagination which can be problematic, you just pass the cursor in and resume where it left off.
Works across connections too.
May implement reverse queries as well as it is minimal effort