Next sign of error, I'm off to middlecoin til all this crap is in working order. Prices are too low and going lower too quick to piss around.
Sorry, but business is business.
Topic: [ANN][Pool][Profit-Switch][Optional Auto-Exchange per Coin][Vardiff] ~ Hashcows - page 67. (Read 347332 times)
January 09, 2014, 01:20:56 PM
Ok....just...WOW all that wasted work last night. See this is what I meant about keeping us "in the know." I wouldn't have been mining with you all night had you specified it was not just a simple "stratum issue" or slow data imports, but actual factual ****ed up rounds with 0 payout.
Next sign of error, I'm off to middlecoin til all this crap is in working order. Prices are too low and going lower too quick to piss around.
Sorry, but business is business.
Next sign of error, I'm off to middlecoin til all this crap is in working order. Prices are too low and going lower too quick to piss around.
Sorry, but business is business.
January 09, 2014, 01:19:50 PM
Lol we are just after the hacking fiasco and now people are asking on simplifying password and pin code? Omg.
Btw admin, any intention to make a mobile app for hashcows?
Btw admin, any intention to make a mobile app for hashcows?
January 09, 2014, 11:47:32 AM
3 digit pin, lolz
Dont forget to set the maximum number of times you can try to enter a password before the site blocks your account to 999.
lol, nice one Dont forget to set the maximum number of times you can try to enter a password before the site blocks your account to 999.
January 09, 2014, 11:34:05 AM
I'm sorry I got this going 
January 09, 2014, 11:21:53 AM
Does anyone ever bother to read even the last 2 pages of a forum thread anymore before just jumping in and asking a question?
https://bitcointalksearch.org/topic/m.4408900
I did read most of it, but 90% is bitching about password restrictions so I missed it. Anyway, thanks. https://bitcointalksearch.org/topic/m.4408900
January 09, 2014, 11:08:53 AM
The problem is that if you don't enforce users to use capital letters, numbers and punctuation, they will use just lowercase chars, for lazyness.
Thus, if a hacker brute-forces with lowercase chars, he will be successful on most users.
Actually, brute force attacks works very well with dictionaries, so the real benefit would be not allowing common words, instead of enforcing capitals or numbers.
I have experience of this because I did security audits on unix machines back in the nineties: you could easily find most passwords by using a dictionary + some numbers and mixed caps.
Thus, if a hacker brute-forces with lowercase chars, he will be successful on most users.
Actually, brute force attacks works very well with dictionaries, so the real benefit would be not allowing common words, instead of enforcing capitals or numbers.
I have experience of this because I did security audits on unix machines back in the nineties: you could easily find most passwords by using a dictionary + some numbers and mixed caps.
I don't agree with the enforce of punctuation and uppercase for two reasons:
1) most (new) keyboard don't have the CAPS LIGHT, so you don't know if you are in uppercase or not, you have no idea how many customers bitches about the uppercase thing with the wireless keyboards, because they type it wrong several times and the passwords gets disabled, all because those keyboards don't have the caps light.
2) punctuation: about 70% of every computer i work on, have the keyboard language mapping wrong, so punctuation are everywhere except where you expect it, so, it is impossible (unless you remember the position of the punctuation keys) to type a password like that if you can't see what are you typing because the mapping does not match the real keyboard.
I think is better to use only lowercase letters and numbers, and a dictionary check, if the password is found in the dictionary, it will force you to choose another one.
agreed, i'm about to sign up to hashcows for testing and these password requirements are cumbersome
about 85% of the computers i use are 23 year old radio shack types and a variety of letters can be quite sticky
not to mention letters can be used to form words that some people find offensive
i say make required passwords be a 3 digit pin (no duplicate digits! i might hit the key twice on accident!) and leave it at that
LMAO...3 digit pin?! Ya know what, skip the PIN and just hand your BTC over to me as soon as you mine it.
You're just asking to get your balance stolen with a 3 digit pin. I could guess it in 10 mins.
The site password restrictions are quite common and more sites should use the restrictions. Sure, they can be a pain, but it's not unlike signing into Facebook or Yahoo!.
You don't want a new password system like the rest of the developed world because your computer is too old but you're mining with some fancy new graphics cards? I can't even...
January 09, 2014, 11:08:16 AM
Phbbtt reading is overrated 
Not like this is a forum...oh nm. :|
https://bitcointalksearch.org/topic/m.4408900
Not like this is a forum...oh nm. :|How often does "current balance" update? I've been mining for 16 hours with 2.3MH/s and I only have 0.00000522 balance which is ridiculous! I got 2 million accepted shares and 30k rejected (I think cgminer switched in between, so maybe this is just from last 1 hr, don't know).
Does anyone ever bother to read even the last 2 pages of a forum thread anymore before just jumping in and asking a question?https://bitcointalksearch.org/topic/m.4408900
January 09, 2014, 10:51:06 AM
How often does "current balance" update? I've been mining for 16 hours with 2.3MH/s and I only have 0.00000522 balance which is ridiculous! I got 2 million accepted shares and 30k rejected (I think cgminer switched in between, so maybe this is just from last 1 hr, don't know).
Does anyone ever bother to read even the last 2 pages of a forum thread anymore before just jumping in and asking a question?https://bitcointalksearch.org/topic/m.4408900
January 09, 2014, 10:44:17 AM
How often does "current balance" update? I've been mining for 16 hours with 2.3MH/s and I only have 0.00000522 balance which is ridiculous! I got 2 million accepted shares and 30k rejected (I think cgminer switched in between, so maybe this is just from last 1 hr, don't know).
January 09, 2014, 10:42:29 AM
3 digit pin, lolz
Dont forget to set the maximum number of times you can try to enter a password before the site blocks your account to 999.
Dont forget to set the maximum number of times you can try to enter a password before the site blocks your account to 999.
January 09, 2014, 10:41:01 AM
agreed, i'm about to sign up to hashcows for testing and these password requirements are cumbersome
about 85% of the computers i use are 23 year old radio shack types and a variety of letters can be quite sticky
not to mention letters can be used to form words that some people find offensive
i say make required passwords be a 3 digit pin (no duplicate digits! i might hit the key twice on accident!) and leave it at that
If this isn't sarcasm, I just don't quite know what to say . . . maybe . . . Wow! about 85% of the computers i use are 23 year old radio shack types and a variety of letters can be quite sticky
not to mention letters can be used to form words that some people find offensive
i say make required passwords be a 3 digit pin (no duplicate digits! i might hit the key twice on accident!) and leave it at that
January 09, 2014, 10:40:53 AM
They are working their butts off to get the site going, and there is a whole page dedicated to how people dont want to use uppercase letters in the passwords.
You guys must must be the happiest people in the world i guess.
If using uppercase letters is the biggest problem you currently have. Things have to be going great for you.
You guys must must be the happiest people in the world i guess.
If using uppercase letters is the biggest problem you currently have. Things have to be going great for you.
January 09, 2014, 10:20:10 AM
The problem is that if you don't enforce users to use capital letters, numbers and punctuation, they will use just lowercase chars, for lazyness.
Thus, if a hacker brute-forces with lowercase chars, he will be successful on most users.
Actually, brute force attacks works very well with dictionaries, so the real benefit would be not allowing common words, instead of enforcing capitals or numbers.
I have experience of this because I did security audits on unix machines back in the nineties: you could easily find most passwords by using a dictionary + some numbers and mixed caps.
Thus, if a hacker brute-forces with lowercase chars, he will be successful on most users.
Actually, brute force attacks works very well with dictionaries, so the real benefit would be not allowing common words, instead of enforcing capitals or numbers.
I have experience of this because I did security audits on unix machines back in the nineties: you could easily find most passwords by using a dictionary + some numbers and mixed caps.
I don't agree with the enforce of punctuation and uppercase for two reasons:
1) most (new) keyboard don't have the CAPS LIGHT, so you don't know if you are in uppercase or not, you have no idea how many customers bitches about the uppercase thing with the wireless keyboards, because they type it wrong several times and the passwords gets disabled, all because those keyboards don't have the caps light.
2) punctuation: about 70% of every computer i work on, have the keyboard language mapping wrong, so punctuation are everywhere except where you expect it, so, it is impossible (unless you remember the position of the punctuation keys) to type a password like that if you can't see what are you typing because the mapping does not match the real keyboard.
I think is better to use only lowercase letters and numbers, and a dictionary check, if the password is found in the dictionary, it will force you to choose another one.
agreed, i'm about to sign up to hashcows for testing and these password requirements are cumbersome
about 85% of the computers i use are 23 year old radio shack types and a variety of letters can be quite sticky
not to mention letters can be used to form words that some people find offensive
i say make required passwords be a 3 digit pin (no duplicate digits! i might hit the key twice on accident!) and leave it at that
January 09, 2014, 09:59:52 AM
I agree, this is 2014 where our GPU miners are also very good at brute forcing password hashes, so we need 2014 policies, otherwise you're open to some of the biggest security fiascos in computer history: Sony, Adobe, Target, etc...
January 09, 2014, 09:33:53 AM
The problem is that if you don't enforce users to use capital letters, numbers and punctuation, they will use just lowercase chars, for lazyness.
Thus, if a hacker brute-forces with lowercase chars, he will be successful on most users.
Actually, brute force attacks works very well with dictionaries, so the real benefit would be not allowing common words, instead of enforcing capitals or numbers.
I have experience of this because I did security audits on unix machines back in the nineties: you could easily find most passwords by using a dictionary + some numbers and mixed caps.
Thus, if a hacker brute-forces with lowercase chars, he will be successful on most users.
Actually, brute force attacks works very well with dictionaries, so the real benefit would be not allowing common words, instead of enforcing capitals or numbers.
I have experience of this because I did security audits on unix machines back in the nineties: you could easily find most passwords by using a dictionary + some numbers and mixed caps.
I don't agree with the enforce of punctuation and uppercase for two reasons:
1) most (new) keyboard don't have the CAPS LIGHT, so you don't know if you are in uppercase or not, you have no idea how many customers bitches about the uppercase thing with the wireless keyboards, because they type it wrong several times and the passwords gets disabled, all because those keyboards don't have the caps light.
2) punctuation: about 70% of every computer i work on, have the keyboard language mapping wrong, so punctuation are everywhere except where you expect it, so, it is impossible (unless you remember the position of the punctuation keys) to type a password like that if you can't see what are you typing because the mapping does not match the real keyboard.
I think is better to use only lowercase letters and numbers, and a dictionary check, if the password is found in the dictionary, it will force you to choose another one.
Nearmiss has made it clear and frankly, most people agree with the current password policy. Further argument is pointless and serves no positive purpose. Accept it and move on.
January 09, 2014, 09:23:18 AM
- Balances
You won't see a change to your BTC balance until payouts happen, once a day at GMT 04:00:00. Normally you'd have an "Estimated Un-Exchanged" and "Estimated Exchagned" value that grows and adjusts throughout the day, those are currently disabled, and being worked on. If you don't have a balance *after* payout time, its something to be concerned about, and let support know.
You won't see a change to your BTC balance until payouts happen, once a day at GMT 04:00:00. Normally you'd have an "Estimated Un-Exchanged" and "Estimated Exchagned" value that grows and adjusts throughout the day, those are currently disabled, and being worked on. If you don't have a balance *after* payout time, its something to be concerned about, and let support know.
Thank you for the update!.
one question, can I do manual withdraw or is disabled for now?.
happy to see the site back on track!, thank you!.
January 09, 2014, 09:19:45 AM
In my worker setting, there are "Round Shares Accepted (Adj)". Are these adjusted shares? How are they adjusted?
In the stats section, there are also pool accepted shares, are they adjusted?
Should be ratio of my accepted shares and the poll accepted share similar to the ratio of my hash rate to pool hash rate?
In the stats section, there are also pool accepted shares, are they adjusted?
Should be ratio of my accepted shares and the poll accepted share similar to the ratio of my hash rate to pool hash rate?
January 09, 2014, 09:18:06 AM
The problem is that if you don't enforce users to use capital letters, numbers and punctuation, they will use just lowercase chars, for lazyness.
Thus, if a hacker brute-forces with lowercase chars, he will be successful on most users.
Actually, brute force attacks works very well with dictionaries, so the real benefit would be not allowing common words, instead of enforcing capitals or numbers.
I have experience of this because I did security audits on unix machines back in the nineties: you could easily find most passwords by using a dictionary + some numbers and mixed caps.
Thus, if a hacker brute-forces with lowercase chars, he will be successful on most users.
Actually, brute force attacks works very well with dictionaries, so the real benefit would be not allowing common words, instead of enforcing capitals or numbers.
I have experience of this because I did security audits on unix machines back in the nineties: you could easily find most passwords by using a dictionary + some numbers and mixed caps.
I don't agree with the enforce of punctuation and uppercase for two reasons:
1) most (new) keyboard don't have the CAPS LIGHT, so you don't know if you are in uppercase or not, you have no idea how many customers bitches about the uppercase thing with the wireless keyboards, because they type it wrong several times and the passwords gets disabled, all because those keyboards don't have the caps light.
2) punctuation: about 70% of every computer i work on, have the keyboard language mapping wrong, so punctuation are everywhere except where you expect it, so, it is impossible (unless you remember the position of the punctuation keys) to type a password like that if you can't see what are you typing because the mapping does not match the real keyboard.
I think is better to use only lowercase letters and numbers, and a dictionary check, if the password is found in the dictionary, it will force you to choose another one.
January 09, 2014, 09:07:15 AM
Thanks for the answer, nearmiss!
January 09, 2014, 08:59:39 AM
- Red Rounds
Most are only a minute or two, there was a bug in the switching script triggered under certain conditions following a 0 coin round, that would cause us to potentially switch off the next coin way earlier than we normally would. This bug has been fixed, no more 1-2min rounds.
- Passwords
"Actually, brute force attacks works very well with dictionaries, so the real benefit would be not allowing common words, instead of enforcing capitals or numbers." This is the case, I believe. Common words are also rejected, to some extent. To be honest, the fact we enforce a capital letter is not something I'm going to spend any time thinking further about atm, we've got enough on the list to get to before revisiting a modification on password policy. 8+ chars, 1 uppercase, 1 number. It is what it is for now.
- Balances
You won't see a change to your BTC balance until payouts happen, once a day at GMT 04:00:00. Normally you'd have an "Estimated Un-Exchanged" and "Estimated Exchagned" value that grows and adjusts throughout the day, those are currently disabled, and being worked on. If you don't have a balance *after* payout time, its something to be concerned about, and let support know.
Most are only a minute or two, there was a bug in the switching script triggered under certain conditions following a 0 coin round, that would cause us to potentially switch off the next coin way earlier than we normally would. This bug has been fixed, no more 1-2min rounds.
- Passwords
"Actually, brute force attacks works very well with dictionaries, so the real benefit would be not allowing common words, instead of enforcing capitals or numbers." This is the case, I believe. Common words are also rejected, to some extent. To be honest, the fact we enforce a capital letter is not something I'm going to spend any time thinking further about atm, we've got enough on the list to get to before revisiting a modification on password policy. 8+ chars, 1 uppercase, 1 number. It is what it is for now.
- Balances
You won't see a change to your BTC balance until payouts happen, once a day at GMT 04:00:00. Normally you'd have an "Estimated Un-Exchanged" and "Estimated Exchagned" value that grows and adjusts throughout the day, those are currently disabled, and being worked on. If you don't have a balance *after* payout time, its something to be concerned about, and let support know.
Jump to: