The number of listeners has not been directly readable for some time now. I calculate these by comparing two values of the streamed time (bottom on bitrad.io)
But this is not quite accurate, because this number also includes unpaid streaming time. This means that the number of listeners is even smaller than I expect in my calculations.
In truth, the payout is not "only" 20% too low, it's probably more than 50% too low.
I compared the values of the last 144 hours (last 6 days):
payout (increased): 7,824.6517 BRO / 144 = 54.338 BRO per hour
streamed (increased): 1,616,985 hrs / 144 = 11,229 streamed hrs per hour = 11,229 listener per hour?
I checked these figures last year when the calculation was still correct.
And then 120 BRO per hour were paid out, today only 54 BRO per hour.
This means, Uwe "saves" per hour 65.662 BRO = 47276 BRO per month = 23600 € per month (more than 2 BTC).
Yes that´s the idea but in the last few days there are some issues with paying the AP.
The Dev Uwe know about that an is working on that with other developers.
We all hope that there is a fst solution.
Enjoy the Music and be patient
@7onsti07 My only feedback is that Recaptcha is trying to make my life as difficult as possible. Earlier, I did a lot of Recaptchas on various faucets and now they are punishing me. Doing 100+ captchas/day was not uncommon. Just like Google did with adsense on faucets, the same thing is happening with captchas.
app menu > help > debug window > information > network > number of masternodes
it's not a spending, it's deposit (or pledge). you can create additional bro-coin address in your own wallet and send pledge to it, info of this transaction got to be used in node settings (node.conf). on youtube you can get some howtos about starting a bro node. pledge for node is 2500 bro, and, of cource, you need a server too )