@fce803cc Yes, I think that memory starving happens when updating rss feeds during playback: it gets worse when there are a lot of subscribed podcasts and when some podcast has very large rss feeds. These are very difficult bugs to reproduce and catch, but the new version should mitigate the issue cancelling current RSS updates when the system sends a memory warning to the app.
The more I refine code and fix bugs for calculating splits, the more the thing gets complicated.
With value time split many splits can result in less than 1 sat payments.
Should we discard them?
Should we round them to 1 sat and send a total amount greater than the one the user selected?
Should we delay and aggregate them?
The first and last options would completely screw the splits used to do stats.
@fce803cc somebody about to undergo larynx surgery, or affected by a chronic degenerative disease to any part of the breathing / speech apparatus, brain included (SLA/Lou Gehrig disease for example).
Notes by e9b8f5a9 | export