Audit and Suspension Score Overview
On the storage node dashboard you will now see the audit and suspension score for all satellites on one screen. A score lower than 76% will be displayed as a yellow warning. A score lower than 60% will be displayed in red.
Payout History
In the last release the payout history was showing the first payout by default. Now it will show the latest payout by default.
For Customers
We are working on a new design for the satellite UI. You can already see the new UI structure. Some of the colors are currently wrong. We are going to fix that with the following release in 2 weeks.
i hate the loading screen especially that it pops up sometimes when it really wasn’t needed… maybe my system is slow or something… but didn’t seem that slow before the loading screen lol
and in regard to comments… i think it may have to do with the many people having update issues on windows when upgrading to 1.13.1, seems to stall the service and has to be manually restarted.
also v1.13.1 hasn’t been released to docker yet… so lots of people waiting for it still…
i look forward to seeing the new features in action. should be out any day now i think
Why don’t they remove the loading screen? Probably someone senior in engineering created that loading screen, and now won’t acknowledge that it was mistake and remove it
For me it seems with the v1.12.3 release that the loading screen doesn’t stay around any longer than needed (previously appeared to be locked to a minimum amount of time), which is a welcome update from v1.11.1. But there are still certain elements that probably don’t need the loading wheel to pop up for.
I agree with the use of some kind of loading indicator, even though browsers have their own, it’s a nice touch, but not one that covers what you’re trying to load, might as well not have it then!
Having that spinner overlayed on the top center of the page, like in Android apps, would looks very professional too, but still allow you to use the page.
We had to stop the release of v1.13.1 due to bugs that caused issues. We fixed them in v1.13.3 with is rolling out currently. I expect that the full rollout is achieved by 6PM UTC tomorrow.