Here's what the guys at Alby say:

One option is to create a new namespace or expand the existing one. However, an alternative approach could be to leverage the RSS namespace extension for podcasting, which already includes the necessary tags. For instance, the value tag can be used to define the payment method and recipient, while the new medium tag allows for easy differentiation of content types, such as "blogpost", "newsletter", "video", or "music", as specified values. This approach streamlines the implementation process, utilizing existing infrastructure and established standards.

Maybe something like:

<podcast:value type="lightning" method="address" suggested="0.00000006900">
  <podcast:valueRecipient name="ejzys" type="address" split="95" address="ekzyis@stacker.news"/>
  <podcast:valueRecipient name="Stacker News" type="address" split="5" address="sn@stacker.news"/>
</podcast:value>

If I was elite and skilled in Rust I'd either contribute to the breez SDK or leverage it into building something that complemented one of my other strengths

https://github.com/breez/breez-sdk

A 2 with a handful of wallets for software testing. My current view is that lightning is pocket money, and bitcoin is the bank. If I acquire more lightning than I need for current use, I'll transfer on chain to my Umbrel node for posterity. Having multiple wallets with different features that Sats can easily be switched between offers the best variety of capabilities. Expecting one wallet to do everything is wishful thinking.