One of the most interesting things of this refactoring to get Amethyst into the outbox model is the realization that many parts of nostr don't provide guidance for relay hints.
For instance, when you follow a hashtag. Which relays are you following the hashtag on? Is it one relay for all hashtags or each hashtag you follow needs to have a relay list for itself?
Same for locations, labels, reports, products, DVMs, blogs, etc, etc, etc.
Following keys is the easy part.
You know, I never thought of that. I guess I would assume it would be my inbox relays for all of those? Which would mean we'd have to slightly update the definition of what inbox is. It's not just for comments and reactions. It would be for content that I want to consume.
Yeah, we just used the General relay list for everything. But that is going away.
I'm pretty sure this is where the personalized intelligence agents come in ...
Not to be { That_Guy } and "sprinkle it with AI" , but ... how else can those outputs be responsive to the mix of issues around surfacing accurate data based on the cloud or relays all showing variations of the nostr-verse posts.
Dang, I never thought of where I'm following #Catstr from.
never late for people to finally realize the obvious
I have people define search relays. Then it searches on those relays. But by default it just searches the local database. In gossip people aren't following hashtags (...yet).
But yes.
I imagine this would have to be a learned thing, in that if you are following a hashtag from a text note, you'd start with that pubkey's outbox relay list, and then any other notes that show up for that hashtag, you'd scape the author of those notes outbox and add the relays to the list.
This doesn't solve de novo following a hashtag with no context, however.
