Allow to identify a boost/stream; clarify uuid
#621
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, the description of
uuid
seems ambiguous—it is not clear whether the payment refers to the one made by the listener or the one sent out the individual recipient. Podverse and Podcast Guru interpret it as the latter.Anyway, identifying the boost or stream by the listener is still useful. For example, suppose there are feed recipients Alice and BoostBot, and, during a value time split, another feed is referenced with recipients Bob and BoostBot. BoostBot is likely to receive two identical TLV records (except for
uuid
). It is then not clear whether to count this as a single boost or two boosts for analytics' purposes. Looking at the splits and the timing of the payments, it's possible to make good guesses, but none of them are foolproof.Therefore, I'm proposing
boost_uuid
, which uniquely identifies the payment made by the listener.Here's the pseudocode of how apps may handle it: