it makes me think about how both reactions and zaps could be integrated into replies, and then to link the two parts together to prioritise them or highlight them

would just entail probably adding a multi-letter tag like "associated" and the reply ID with the zap/reaction on the input side and pulling that out of the set of events that refer to the parent note, and then parsing that for display so reactions get attributed more visibly... and for fun, add a priority feed that puts zaps at top and reaction comments below it 

 Yeah, raise the signal. 

 I've sometimes got 10 feeds going simultaneously and I need to know what to look at, first.

I turn off likes, usually.
I look at my favorite follows' replies first, then I look at zapper's stuff, then I turn off replies and look at boosts and quotes.

I only reply to all replies if it's a slow time, like Monday morning in Europe.

And now that we're moving the projects from Simplex and Slack to Nostr, and my gitstuff is high-prio, I'll need more filtering.

A reply to an issue should be top-level, for me. 

 AND I NEED MY PROJECT GROUPS IN MY NOTIFICATIONS 💯  

 If they write me, 

yo Stella, server is 404, I need to see that ASAP 

 Especially if it's a private group ffs.
We literally formed a secret club. I want to see what they wrote. 

 it would be really good to assemble a feature set for a serious slack/github style deployment

i think if such tools exist there is money for hosting, managing and maintaining it 

 That's what GitRepublic will be. 

 The feature set 
nostr:naddr1qvzqqqrcvgpzphtxf40yq9jr82xdd8cqtts5szqyx5tcndvaukhsvfmduetr85ceqydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcpr3mhxue69uhhg6r9vd5hgctyv4kzumn0wd68yvfwvdhk6tcqpdnkjarjv4c82cnvd93s7v6gs5 

 You should ditch the code editor imo. A lot of effort for a feauture no one wants to use. You're not gonna get people to switch from their editor of choice.