Laeserin @Laeserin - 15h
NIP70 >> NIP29 Results are in.
That is a normal OP, followed by a community reply, followed by a normal reply. 😂🤌🏻😎
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgewaehxw309aex2mrp0yhxummnwa5x2un99e3k7mf0qyt8wumn8ghj7ct8vaezumn0wd68ytnvv9hxgtcpz9mhxue69uhkummnw3ezumrpdejz7qgwwaehxw309ahx7uewd3hkctcqypftfgrkhjammsap4marwdvpdnm5nya3hrdjq2cpezputzl8ltvt6yl64du you're aggregating NIP70s. Seems sort of pointless. Or is there are use case for that?
semisol @semisol - 15h
Good question
Laeserin @Laeserin - 14h
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.
semisol @semisol - 14h
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
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1nlk894teh248w2heuu0x8z6jjg2hyxkwdc8cxgrjtm9lnamlskcsghjm9c
So, last-read, but relay-side?
This can be used for that as well
Laeserin @Laeserin - 10h
I still haven't figure out how to setup communikeys for theforest. 😂 I have a TheForest npub, now what?
