Automate forwarding of payments

[MoritzKa]

From: https://habla.news/alby/1690364668026 comment id d4935613aeb825b8a32e20863c926364eff1914aca794505f033683c84f7aa09

Wondering whether it would be interesting to add the ability for the funding to "trickle down". The package developer could add a recursive property in the package.json funding area, which would be a decimal between 0 and 1 describing how much of any received funding would be automatically sent further down to other packages devs. It could be achieved even more granularly by combining PkgZap with ZapSlitter.

[bumi]

I do not see that comment, but this is already possible.
The library has support to decide the depths you want to load (meaning to also get the dependencies of a dependency).

In the CLI we do not set this for simplicity reasons. the user would need to be asked another question.
https://github.com/getAlby/pkgzap/blob/main/cli/bin/index.js#L112

With the lightning prism idea the package developer already can pass on the payment and split up received payments.

[fanismichalakis]

Author of the comment here! Good to know that depth is already supported, and could be made easily accessible to users should their be demand for this feature.

However, I tend to think that leaving the ability to trickle down donations in the hands of the package developer makes more sense. This would allow them to configure a more granular split using Lightning prisms. For example, a library that was very helpful could receive more than other "less useful" packages. After all, the package developer is the best placed to categorise their dependencies "usefulness".

Furthermore, the getFundingDetails and fetchFundingInfo methods seem perfect to gather all the funding data. What would be a nice addition would be an import feature in ZapSlitter (for example) where the user can upload/past the fundingInfo JSON. The JSON is then parsed to populate the usual form in ZapSlitter, and all the user has left to do is define the weights.