Here you go sir @PABLOF7z 
An idea that solves a lot at once imo.  

 Nice idea and, as usual, great execution Niel!
But we should pay attention to move the discussion outside the plain kind:1 model, because some clients could loose content. I don't know how zap replies are structered, but I suppose it's possibile to make them standard-reply compliant, maybe simply using two ["e", <event-id>, "reply"] tags. 

 I don't know either haha 😅 so good point sir.
But I could imagine ways for them to be readable by all clients using some kind of tag combo indeed.  

 What is this and why is it cool? 

 Like it! ... but this requires that custom zaps messages are used. I wonder if people find them when they are hidden behind a long press. 

Maybe it would be better to be able to "attach" sats to a regular reply (from a UI point of view). 

 1. Why? Is there no way to just reference the zap in the comment? (while also adding some tags that even makes it readable in clients that have no idea this exists)
2. Haha agreed, but it's probably to late for that and at this point that would probably make things even more confusing.  

 @PABLOF7z already made a tag happen for all the weird event types most clients don't natively show.
So, is there a big difference between "This is a Stemstr music track by UserName" and "This is a Zap of 10K by UserName, Message: I love carpet" 

 I just meant people need to use custom zap messages. Sure, we can attach comments to zap events. 

 Oooooh yes, I see 🤦
That's a good point. 
I've got a solution for that though. 
I'll mock up asap.