Oddbean new post about | logout
▲ ▼
Laeserin | 6 months ago (raw) | root | parent | reply | flag +3 
 They already give up with my npub, sometimes. I have mutes bleed into my feed because they hide too slowly.

It works better in the clients that filter out mutes in the base query.
▲ ▼
mleku | 6 months ago (raw) | root | parent | reply | flag +3 
 adding a negation to filter fields would go a long way to making that work better but the source-routing-style blacklist strategy is gonna cause big problems there too
▲ ▼
Laeserin | 6 months ago (raw) | root | parent | reply | flag 
 It's just lists, really. So, they just need to say "include these lists and excluded these lists", right?
▲ ▼
mleku | 6 months ago (raw) | root | parent | reply | flag +2 
 that would intrude a bit into the clean separation of the database, it requires an expansion of the query API, and the bigger these negation filters get the more problematic they will be for performance

probably at some point the simple filter query strategy will give way to a cleaner GraphQL syntax
▲ ▼
Laeserin | 6 months ago (raw) | root | parent | reply | flag +1 
 Yeah, starting to outgrow the efficient complexity.
▲ ▼
mleku | 6 months ago (raw) | root | parent | reply | flag +2 
 i think it is starting to outgrow using a simple numbered proposal list for the protocol specification in general, because implementation details like this actually make a big impact on what the protocol on the network level should be
▲ ▼
mleku | 6 months ago (raw) | root | parent | reply | flag +1 
 we need to start thinking about Nostr 2.0 like how we have HTML 5 now
▲ ▼
Low Information Voter | 6 months ago (raw) | root | parent | reply | flag +1 
 That is going to be a problem for gathering data for Minitru. Velvet's npub was hard to get data from, this is probably why!