he is depressing me
thanks
nick radino
and why still miners crashing from pool? something is wrong again = 181 and 183 versions of miners
today more users on pool had crashed miners
Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 689. (Read 243376 times)
January 22, 2018, 12:17:07 PM
bible_pay pls response on our questions !!!! ppl got BBP on your pool where cant join via nick+password + reseting doesnt working ... please fix it
he is depressing me
thanks
nick radino
and why still miners crashing from pool? something is wrong again = 181 and 183 versions of miners
today more users on pool had crashed miners
he is depressing me
thanks
nick radino
and why still miners crashing from pool? something is wrong again = 181 and 183 versions of miners
today more users on pool had crashed miners
January 22, 2018, 11:46:40 AM
For all Sanctuaries
I make some stuff to send email notification about change status of Sanctuary.
My sofware will notify by sending a email everytime when Sanctuary change status (eg. from ENABLED to NEW_START_REQUIRED).
I now only have limit offert to 10 Sanctuaries for 10k BBP [it's less than one day mining].
Anyone who want this, just send PM to me with email address, BBP Mining Address OR TX signed to Masternode.
I make some stuff to send email notification about change status of Sanctuary.
My sofware will notify by sending a email everytime when Sanctuary change status (eg. from ENABLED to NEW_START_REQUIRED).
I now only have limit offert to 10 Sanctuaries for 10k BBP [it's less than one day mining].
Anyone who want this, just send PM to me with email address, BBP Mining Address OR TX signed to Masternode.
Awesome!, I wonder if the work Andrew? is doing implementing the Dash web governance stuff for us will give us that ability in the near future?
Any plans to open-source the work you did? Will gladly pay BBP for open-source, Im sure you could also be heavily rewarded from the budget as well if you went the proposal route too
http://wiki.biblepay.org/Create_Sanctuary_2#SUBMIT_PROPOSAL
...
).Now I need make some test, I never have a Masternode (Sancturay it's my first).
After all tests I want make it as SAAS and open-source for all Masternode coins.
January 22, 2018, 11:39:36 AM
For all Sanctuaries
I make some stuff to send email notification about change status of Sanctuary.
My sofware will notify by sending a email everytime when Sanctuary change status (eg. from ENABLED to NEW_START_REQUIRED).
I now only have limit offert to 10 Sanctuaries for 10k BBP [it's less than one day mining].
Anyone who want this, just send PM to me with email address, BBP Mining Address OR TX signed to Masternode.
I make some stuff to send email notification about change status of Sanctuary.
My sofware will notify by sending a email everytime when Sanctuary change status (eg. from ENABLED to NEW_START_REQUIRED).
I now only have limit offert to 10 Sanctuaries for 10k BBP [it's less than one day mining].
Anyone who want this, just send PM to me with email address, BBP Mining Address OR TX signed to Masternode.
Awesome!, I wonder if the work Andrew? is doing implementing the Dash web governance stuff for us will give us that ability in the near future?
Any plans to open-source the work you did? Will gladly pay BBP for open-source,
Im sure you could also be heavily rewarded from the budget as well if you went the proposal route
http://wiki.biblepay.org/Create_Sanctuary_2#SUBMIT_PROPOSAL
===
Related Dash Info:
https://www.dash.org/forum/threads/mn-v3-updated-receive-text-message-or-email-notifications-upon-masternode-payment.2805/
https://www.dash.org/forum/threads/how-to-send-masternode-status-to-email.17147/
https://www.dash.org/forum/threads/how-to-send-masternode-status-to-email-from-the-server.18107/
https://dashpay.atlassian.net/wiki/spaces/DOC/pages/8880256/Down+Notification
January 22, 2018, 11:35:35 AM
Regarding the Sanctuary crash issue, the problem is not showing in the logs with full logging on, so I had to rent a quad core VPS to help find the issue (since it needed a public IP to reproduce, with 1.55M locked funds in prod).
Now I'm running a brand new sanctuary in the cloud in debug mode in prod - so hopefully the problem will be revealed soon then we can fix the line of code in the core that is causing the issue.
Now I'm running a brand new sanctuary in the cloud in debug mode in prod - so hopefully the problem will be revealed soon then we can fix the line of code in the core that is causing the issue.
January 22, 2018, 11:29:15 AM
For all Sanctuaries
I make some stuff to send email notification about change status of Sanctuary.
My sofware will notify by sending a email everytime when Sanctuary change status (eg. from ENABLED to NEW_START_REQUIRED).
I now only have limit offert to 10 Sanctuaries for 10k BBP [it's less than one day mining].
Anyone who want this, just send PM to me with email address, BBP Mining Address OR TX signed to Masternode.
I make some stuff to send email notification about change status of Sanctuary.
My sofware will notify by sending a email everytime when Sanctuary change status (eg. from ENABLED to NEW_START_REQUIRED).
I now only have limit offert to 10 Sanctuaries for 10k BBP [it's less than one day mining].
Anyone who want this, just send PM to me with email address, BBP Mining Address OR TX signed to Masternode.
January 22, 2018, 11:15:24 AM
I do believe we need some sort of grouping as the issue with BBP is that we're getting big numbers.
Yes, absolutely. Horrible without, that's why I posted the link to the PDF, which shows spaces as a more modern alternative. Not a must have, but maybe a good solution for everybody.
As said, it is not the biggest thing in the world, nobody dies because of it, I only know that problem from my own experience, in my daily job that already caused some real problems
(Customer: You said 1 Meter! -> No, 1000 Meter....) January 22, 2018, 11:10:59 AM
I think you misunderstood my point which was what's confusing for you may be clear for another, and what's clear for you may be confusing for another so the only winning solution would be 1) no formatting 2) only using "." to separate the decimal part (maybe less confusing?) 3) getting the visitor regional preferences which I won't do.
See my first post on that topic:
Quote
Best would be to use "." (US) or "," for decimal separator, and spaces for number grouping -> "$37 267"
That might give the best result without to much confusion.
https://www.bipm.org/utils/en/pdf/Resol22CGPM-EN.pdf
"declares that the symbol for the decimal marker shall be either the point on the line or the comma on
the line,
reaffirms that ìNumbers may be divided in groups of three in order to facilitate reading; neither dots
nor commas are ever inserted in the spaces between groupsî, as stated in Resolution 7 of the
9th CGPM, 1948."
That might give the best result without to much confusion.
https://www.bipm.org/utils/en/pdf/Resol22CGPM-EN.pdf
"declares that the symbol for the decimal marker shall be either the point on the line or the comma on
the line,
reaffirms that ìNumbers may be divided in groups of three in order to facilitate reading; neither dots
nor commas are ever inserted in the spaces between groupsî, as stated in Resolution 7 of the
9th CGPM, 1948."
You can indeed use "." or ",", but for decimal not for the number grouping. That is where it starts to get confusing
The hashes are a good example: "7,443 MH/s"
Might be good for you, but for a big part of the world a really low number
Better "7443 MH/s" or "7 443 MH/s" ("7443.99 MH/s" or "7 443.99 MH/s" are fine, indeed)
I do believe we need some sort of grouping as the issue with BBP is that we're getting big numbers.
Also, as I said at the end of my previous post, I believe that the "American way" is the most common form in the anglosphere and that is confirmed by your wikipedia link.
The BX is in english so it makes sense to format numbers in the english way. I think that form is common enough for everyone to recognise and that's why I chose it.
I apologise if it confuses anyone.
January 22, 2018, 11:07:15 AM
I think you misunderstood my point which was what's confusing for you may be clear for another, and what's clear for you may be confusing for another so the only winning solution would be 1) no formatting 2) only using "." to separate the decimal part (maybe less confusing?) 3) getting the visitor regional preferences which I won't do.
See my first post on that topic:
Quote
Best would be to use "." (US) or "," for decimal separator, and spaces for number grouping -> "$37 267"
That might give the best result without to much confusion.
https://www.bipm.org/utils/en/pdf/Resol22CGPM-EN.pdf
"declares that the symbol for the decimal marker shall be either the point on the line or the comma on
the line,
reaffirms that ìNumbers may be divided in groups of three in order to facilitate reading; neither dots
nor commas are ever inserted in the spaces between groupsî, as stated in Resolution 7 of the
9th CGPM, 1948."
That might give the best result without to much confusion.
https://www.bipm.org/utils/en/pdf/Resol22CGPM-EN.pdf
"declares that the symbol for the decimal marker shall be either the point on the line or the comma on
the line,
reaffirms that ìNumbers may be divided in groups of three in order to facilitate reading; neither dots
nor commas are ever inserted in the spaces between groupsî, as stated in Resolution 7 of the
9th CGPM, 1948."
You can indeed use "." or ",", but for decimal not for the number grouping. That is where it starts to get confusing
The hashes are a good example: "7,443 MH/s"
Might be good for you, but for a big part of the world that is a really low number
Better "7443 MH/s" or "7 443 MH/s" ("7443.99 MH/s" or "7 443.99 MH/s" are fine, indeed)
For me, it is not a really big thing, but if you can make it more understandable for many people, I think that would be great.
January 22, 2018, 11:03:19 AM
Thanks inblue,
I will see if more people think the font size should be bigger. However, you can also use the zoom function to make it look bigger. Try 110% or 120%. If you're using Chrome, it will remember it and use it on all the pages.
I will see if more people think the font size should be bigger. However, you can also use the zoom function to make it look bigger. Try 110% or 120%. If you're using Chrome, it will remember it and use it on all the pages.
Yep, I do that for other sites already, so no issue.
By the way, I don't recognize this type of explorer (like Iquidus), so I guess you built it from scratch?
It did start as a fork of Iquidus. However, I think it is only sharing 5% of the code with it now (if not less) so we're the only coin with that specific BX. That also means that it may have more bugs lol
January 22, 2018, 10:58:39 AM
The US, GB, Australia way of writing numbers is 0,0.0
Yes, and they are only a portion of the world.
https://en.wikipedia.org/wiki/File:DecimalSeparator.svg
I could argue that it would be confusing for these people also if I choose to swap '. 'or ',' or started to do my own thing.
From the point of view of a german, do did swap "," and "."
Now I have looked into all the BX for the popular coins and they all follow the 0,0.0 way of formatting numbers.
You might be suprised to hear that, but some sites imply shows the numbers in a way typical to your region. For example, coinmarketcap.com shows it as $999,99 for me, but $999.99 for you. So simply saying "they all use my system" is true and wrong at the same time.
It is not the end of the world, only a minor point, but it can confuse people.
I am aware websites could implement some modifications depending on the region of the users. I did take that into account when I said I checked the BX of popular coins and said all used 0,0.0
I think you misunderstood my point which was what's confusing for you may be clear for another, and what's clear for you may be confusing for another so the only winning solution would be 1) no formatting 2) only using "." to separate the decimal part (maybe less confusing?) 3) getting the visitor regional preferences which I won't do.
Now, I do believe that the "American way" is the most common form in the anglosphere and that is confirmed by your wikipedia link (the BX is in english). I believe it
is common enough for everyone to recognise and that's why I chose it. I apologise if it confuses anyone.
January 22, 2018, 10:43:37 AM
The US, GB, Australia way of writing numbers is 0,0.0
Yes, and they are only a portion of the world.
https://en.wikipedia.org/wiki/File:DecimalSeparator.svg
I could argue that it would be confusing for these people also if I choose to swap '. 'or ',' or started to do my own thing.
From the point of view of a german, do did swap "," and "."
Now I have looked into all the BX for the popular coins and they all follow the 0,0.0 way of formatting numbers.
Some sites imply shows the numbers in a way typical to your region. For example, coinmarketcap.com shows it as $999,99 for me, but $999.99 for you.
It is not the end of the world, only a minor point, but it can confuse people.
January 22, 2018, 09:54:45 AM
Thanks inblue,
I will see if more people think the font size should be bigger. However, you can also use the zoom function to make it look bigger. Try 110% or 120%. If you're using Chrome, it will remember it and use it on all the pages.
I will see if more people think the font size should be bigger. However, you can also use the zoom function to make it look bigger. Try 110% or 120%. If you're using Chrome, it will remember it and use it on all the pages.
Yep, I do that for other sites already, so no issue.
By the way, I don't recognize this type of explorer (like Iquidus), so I guess you built it from scratch?
January 22, 2018, 09:13:46 AM
I revamped the BX (you may have to purge your cache). The old BX is still available at legacy.biblepay-explorer.org for w/e function is still missing in the new one.
Excellent job Alex, finally if we want to see the latest blocks, we don't have to deal with the recent transactions clutter anymore!
https://biblepay-explorer.org/blocks
I just wish the font size was not so small throughout the explorer, my worn out eyes can barely see what it says.
Anyway, I donated you 1,000 BBP (
) for starters.By the way, it would be awesome if in the explorer you could display a message which was included in the transaction. For now, you can see my message in your wallet in the Transactions tab, then right-click on the transaction and "Show transaction details".
Thanks inblue,
I will see if more people think the font size should be bigger. However, you can also use the zoom function to make it look bigger. Try 110% or 120%. If you're using Chrome, it will remember it and use it on all the pages.
January 22, 2018, 09:05:25 AM
The format for numbers is 0,0.0 which is consistent with everything in the BX and is the way numbers are written in the US.
This format is definitly not the greatest for a lot of countries
In germany, some of the numbers would mean something completely different: "$37,267" would be "37 Dollar & 276 Cent"
Best would be to use "." (US) or "," for decimal separator, and spaces for number grouping -> "$37 267"
That might give the best result without to much confusion.
https://www.bipm.org/utils/en/pdf/Resol22CGPM-EN.pdf
"declares that the symbol for the decimal marker shall be either the point on the line or the comma on
the line,
reaffirms that ìNumbers may be divided in groups of three in order to facilitate reading; neither dots
nor commas are ever inserted in the spaces between groupsî, as stated in Resolution 7 of the
9th CGPM, 1948."
But aside from that, the design is really nice
The US, GB, Australia way of writing numbers is 0,0.0
I could argue that it would be confusing for these people also if I choose to swap '. 'or ',' or started to do my own thing.
Now I have looked into all the BX for the popular coins and they all follow the 0,0.0 way of formatting numbers.
January 22, 2018, 08:58:58 AM
I revamped the BX (you may have to purge your cache). The old BX is still available at legacy.biblepay-explorer.org for w/e function is still missing in the new one.
Excellent job Alex, finally if we want to see the latest blocks, we don't have to deal with the recent transactions clutter anymore!
https://biblepay-explorer.org/blocks
I just wish the font size was not so small throughout the explorer, my worn out eyes can barely see what it says.
Anyway, I donated you 1,000 BBP (
) for starters.By the way, it would be awesome if in the explorer you could display a message which was included in the transaction. For now, you can see my message in your wallet in the Transactions tab, then right-click on the transaction and "Show transaction details".
January 22, 2018, 08:57:33 AM
best idea is w/ , and .
37 000 is 37 000
37 000 is 37 000
January 22, 2018, 08:43:45 AM
The format for numbers is 0,0.0 which is consistent with everything in the BX and is the way numbers are written in the US.
This format is definitly not the greatest for a lot of countries
In germany, some of the numbers would mean something completely different: "$37,267" would be "37 Dollar & 276 Cent"
Best would be to use "." (US) or "," for decimal separator, and spaces for number grouping -> "$37 267"
That might give the best result without to much confusion.
https://www.bipm.org/utils/en/pdf/Resol22CGPM-EN.pdf
"declares that the symbol for the decimal marker shall be either the point on the line or the comma on
the line,
reaffirms that ìNumbers may be divided in groups of three in order to facilitate reading; neither dots
nor commas are ever inserted in the spaces between groupsî, as stated in Resolution 7 of the
9th CGPM, 1948."
But aside from that, the design is really nice
January 22, 2018, 06:29:26 AM
so they got mishmash too 
4755 / 4755
correct is 4,775
but 4775 is good for nonUS ppl
4755 / 4755
correct is 4,775
but 4775 is good for nonUS ppl
FYI it's not just the US.
January 22, 2018, 06:28:36 AM
so they got mishmash too
4755 / 4755
4755 / 4755
They may have chosen not be consistent everywhere but I chose to be. I don't want "mismatches" as you say. Not all has to be modified to just accommodate you lol.
January 22, 2018, 06:24:24 AM
so they got mishmash too
4755 / 4755
correct is 4,775
but 4775 is good for nonUS ppl
4755 / 4755
correct is 4,775
but 4775 is good for nonUS ppl
Jump to: