DashCentral.org - masternode monitoring and budget voting

I keep forgetting to tell you this but on chrome for android the background of the text areas always gets cut alot shorter than your text, making the comments impossible to read sometimes, even when I turn my phone landscape mode. Any ideas or shall I dig into the code for ye?

Click to expand...

Ha ha, yeah this one really sucks. If you want to dig through the CSS, go ahead. I'd love to implement a fix

If someone else with a real android phones wants to check maybe that will help to, I just have some crap galaxy express $100 Android phone, could be lack of phone intelligence maybe I'm an outlier lol.

Anyways what happens is simply that the background of the comments section doesn't span as far as each comment usually and your background image is dark so the text isn't legible anymore.

I would say just throw a fix all for anything like this into the css: (also might want to add <p> tags around whatever is outputting your comments to make it easier to target them.)

Dashwhale updater is a script, you install on the server you run your masternode. It collects the version and the blockheight of your masternode and checks, if your masternode is operating correctly. The data is pushed to the Dashwhale server, so you have comfortable access to your masternode data via the Dashwhale website and mobile apps.

All data is interpretated and in case your masternode is determined to be unfunctional for at least 10 minutes, it is automatically restarted. In addition, you are notified by email, mobile push notification or slack. Automatic restart makes sure your masternode does not drop of the payment list and you don't miss payments.

Thank you for making this. I am trying to get it set up but I appear to be doing something wrong. When I try to run the dashwhale-updater/dwupdater I get
Data POST to Dashwhale failed with code: 401
Data POST to Dashwhale with message: Unauthorized

I am a beginner and have managed to set up a few masternodes but I seem to be missing out on payments as they drop off every so often. I tried to follow the directions and am wondering if I put the api key in correctly.

Dashwhale has been rebranded to DashCentral, to give the plattform a more professional appeal. I know, we all love the whale. But it had to go. The whale with big cigar theme is suboptimal if we want to attract new DASH investors and is problematic when screenshots are shown at cryptocurrency events. DashCentral user and visitor amount is increasing heavily. It has become an important place for new masternode owner onboarding. At some size, things become political. But hey, didn't we all have a great time with the whale?

The proposal creator has been updated to cover some errors (whitespaces within proposal name) and now makes clear the payment conditions in a written summary to avoid unintended proposal payment settings.

A new button to mark all comments as read is now available within the "Budget" section. The button shows up on the up-right corner only, in case there are unread comments.

The proposal creator has been updated to cover some errors (whitespaces within proposal name) and now makes clear the payment conditions in a written summary to avoid unintended proposal payment settings.

A new button to mark all comments as read is now available within the "Budget" section. The button shows up on the up-right corner only, in case there are unread comments.

Click to expand...

But shouldn't people actually be reading the comments rather than ignoring them and blindly voting anyways? I feel as if those comments are rather important to the proposals.... Why make it easier to ignore them?

1. MNO badge: If you own at least one masternode and verified the ownership of the masternode within the section "My masternodes", a MNO badge will be displayed within the proposal discussion and shoutbox close to your username. You can also disable the badge within the "My account" section.

2. Notification categories: A category has been added to the subject of notifications (e.g. proposal, payment, error, working, restart) to allow better distinguishment of DashCentral notifications. In addition we added the USD value of the current MN payment within the notifications.

3. Improved nextpay status: The nextpay status was jumping erratically from time to time. The underlying issue has been resolved.

Masternode Owner/Operator

@rango Hey Rango, there seems to be some issue with the e-mail masternode notifications. It says the test notification is "Delivery: Ok", but i'm not receiving any e-mail. I have, of course, double checked the e-mail for typos There was a guy on the Dashcentral chat that seemed to have the same issue but i cannot remember the username.