Oddbean new post about | logout
▲ ▼
someone | 1 months ago (raw) | root | parent | reply | flag 
 as much as i like developments regarding nostr, i think relays will need to choose a path after this:

1. a queryble data store / note store with a big db
2. being a tor node with a short db

i am leaning towards 1 and i am happy to serve as 1. not much inspiration towards 2. 


nostr:note1skq6njq098cmune3mz35s9snxuftdz3yx35cqyrlux3nv7vpdzlsfygf0l
▲ ▼
Vitor Pamplona | 1 months ago (raw) | root | parent | reply | flag 
 Shortish db (only last 3 months), but for small and large notes. 

Be the hub that connects every human post in realtime. Neither Tor, nor archival stuff.
▲ ▼
someone | 1 months ago (raw) | root | parent | reply | flag 
 TLDR: excellent content will be getting more resources from my relays.


i have really positive thoughts about OGs of Nostr and it was fun and it is still fun but that doesn't mean it is going to be fun all the way 😄  

i am making an LLM based on thoughts and ideas of many people here and it is really a service to humanity because of the truth being shared on this platform. i am hoping nostr never loses this vibe. 

when you say "every human" that includes every human and it is not ideal to serve every human. i won't be able to discern what they are doing using the relay. so i will probably do some LLM based rate limiting (which I was planning anyways). 

LLM will check the notes and articles and adjust rate limits. if someone does nws only they will be effectively getting lower rate limits. but if someone does many wise notes and articles they will get higher rate limits. i will tell Ostrich 70B to objectively do a content analysis and decide whether the content has idea, opinion, knowledge or wisdom and return a number for user. that number will be used to adjust the existing default rate. 

this will also help with existing slow-spam which is meaningless notes but they are still served because they are slowly posted.
▲ ▼
Vitor Pamplona | 1 months ago (raw) | root | parent | reply | flag 
 Nice! I hope this dynamic relay command can help you change those limits on demand and let Clients adjust their queries. 
https://github.com/nostr-protocol/nips/pull/1434
▲ ▼
someone | 1 months ago (raw) | root | parent | reply | flag 
 i don't know how this will be possible in strfry. maybe the write policy script can write the limits to a new lmdb (with pubk being the primary key) and the relay can read from that.