Should hashtags be interpreted as channels?

There are a few cases where this would be nice. For example, having #patchwork-next magically turn into a hyperlink.

Another thought: Should mentioning a channel assign that post to the given channel in the same way that at-mentioning a people in private messages includes them as recipients? Maybe we would need to allow multiple channels per post for this to be good.

since we use markdown, you'd have to have to make sure that parsing markdown headers and hashtags is not ambigious. I think maybe headers are on their own line, with a space after? or maybe hashtags can't be the start of the first line?

Anyway, would merge #good-idea

++ this and multiple channels per post

I got some markdown working for this. However, my attempt was to be based on replacing the string channel value with a map {"chan1": 1, "chan2": 1}, which I thought would keep the ssb-query filter working. However, it instead causes ssb-query to crash (with a TypeError coming from bytewise). Is there a better way to do this, that is queryable?

ohh, this is actually not currently possible with ssb-query - we need a way to specify wildcard paths in flumeview-query / map-filter-reduce. we need this to do mentions too. So currently, you specify paths into objects like ['value', 'content', 'type'] but for mentions it would need to be something like ['value', 'content', true, 'name'] where true means any element in the array.

The second tricky bit, is that if an query hits an index that matches a message more than once, how do you handle that? do you stream that same message multiple times?

I do want to implement this, but in the short term, it might be easier to add this to ssb-links

The second tricky bit, is that if an query hits an index that matches a message more than once, how do you handle that? do you stream that same message multiple times?

that would be okay. sbot.links does this sometimes so i'm already used to adding a pull.unique('key') in pipelines