Topic: 📈 NastyFans: The Bitcoin Enthusiast Fan Club (est. 2012) - page 131. (Read 959381 times)
Sorry to be so harsh about them, but they do screw a lot of people over. Then you see a company like KnC and ASICMiner that meet deadlines, and do not treat customers like garbage. With BFL's track record and the current network hashrate... I just do not think these will workout to more BTC than you paid for them. Since I own some seats I hope that I am wrong though
No way that anyone actually thought these would ship before March 2014... These will never ROI.
Asicminer product's are already more profitable than Monarchs. Monarch was really really bad investment.
I can't tell if you guys are serious... Do you even look at power usage? I know a lot of you are emotional about placing late orders with BFL and not getting rich instantly like you thought, but this pitchfork stuff is getting out of hand.
Power usage doesn't matter until diff 5 billion or so. And by then monarch will mine peanuts throughout it's lifetime. Even the first one shipped.
No way that anyone actually thought these would ship before March 2014... These will never ROI.
Asicminer product's are already more profitable than Monarchs. Monarch was really really bad investment.
I can't tell if you guys are serious... Do you even look at power usage? I know a lot of you are emotional about placing late orders with BFL and not getting rich instantly like you thought, but this pitchfork stuff is getting out of hand.
No way that anyone actually thought these would ship before March 2014... These will never ROI.
Asicminer product's are already more profitable than Monarchs. Monarch was really really bad investment.
No way that anyone actually thought these would ship before March 2014... These will never ROI.
https://bitcointalksearch.org/topic/bfl-monarch-update-323844
Apparently November delivery for BFL is out of the equation.
Apparently November delivery for BFL is out of the equation.
What is your stand on implementing Two-Factor Authentication to the fan page?
I personally do not need it because I use a unique and very secure password. But if fans think it is important and I can implement second-factor authentication without linking against non-C libraries or using proprietary APIs then I can add it to my to-do list.
https://code.google.com/p/google-authenticator/
Not sure what your definition for "proprietary APIs" is...
Despite the name "google authenticator" it's hardly proprietary.
This project's license is OSI approved "free / open source" and it's based on the "OATH" standard which is well known, documented, and able to be used with iPhone, android devices, blackberry, etc. etc. etc. without any modification. I myself use OATH (google authenticator just happens to be a convenient implementation) on my own personal website, and it's good enough for mtgox as well. (( citation / info: https://bitcointalksearch.org/topic/how-to-use-2-factor-auth-on-mtgox-even-without-a-smartphone-111943 <-- steps for explaining how it works on mtgox, and you can even use it without a phone or mobile device... the instructions in this thread are pretty good ))
This implementation is in C, and the only requirement is that your application support PAM
(which is pretty standard & easy enough to add to pretty much anything, not just stuff written in C)
Distribution 267348 is complete. Thank you to our donators!
Horrible luck this week for P2pool (75%)... Might not be a bad time to consider switching to Nasty Pool, those of you who are mining. 
The web interface moved to the new server. We now wait for nastyfans.org domain to update. Thank you for your patience.
OP updated. Thanks for the effort nonnakip.
BITFUNDER UPDATE:
I've claimed the last of our BitFunder holdings. We had 31 shares of BTCINVEST that are being liquidated with funds getting distributed through coinlenders.com. The first liquidation payment totaled 2.69154 BTC and was deposited into our holdings account to be used for debt repayments.
The web interface moved to the new server. We now wait for nastyfans.org domain to update. Thank you for your patience.
Also - thanks to whoever sold me seats at .1 - appreciate your generosity
Amazing! Yes thank you!
This have anything to do with this guy?
https://bitcointalksearch.org/user/squirrel-dearing-138372
Kidding aside though - I hadn't heard about that - really cool way to use QR codes though :-)
Also - thanks to whoever sold me seats at .1 - appreciate your generosity
https://bitcointalksearch.org/user/squirrel-dearing-138372
Kidding aside though - I hadn't heard about that - really cool way to use QR codes though :-)
Also - thanks to whoever sold me seats at .1 - appreciate your generosity
nonnakip, would you consider implementing SQRL?
https://en.wikipedia.org/wiki/SQRL
https://www.grc.com/sqrl/sqrl.htm
http://twit.tv/show/security-now/424
https://en.wikipedia.org/wiki/SQRL
https://www.grc.com/sqrl/sqrl.htm
http://twit.tv/show/security-now/424
I wonder if that's the reason that I can't log into the site using Chrome (or my Android phone)
No big deal.. just wondering.
No big deal.. just wondering.
Hmmm.... I have been using Chrome to log in to Nasty Fans since inception (still do) and I haven't had a problem.
My Password uses a "special" symbol: @ in it somewhere.. I think that's what nonnakip was mentioning..
Either way, it doesn't really bother me much..
I wonder if that's the reason that I can't log into the site using Chrome (or my Android phone)
No big deal.. just wondering.
No big deal.. just wondering.
Hmmm.... I have been using Chrome to log in to Nasty Fans since inception (still do) and I haven't had a problem.
I personally do not need it because I use a unique and very secure password. But if fans think it is important and I can implement second-factor authentication without linking against non-C libraries or using proprietary APIs then I can add it to my to-do list.
C is the only language I trust. And I only trust software where I see the code.
If nastyfans is hacked via web interface there is only 1 person to blame. Me. That is how I want it.
I wonder if that's the reason that I can't log into the site using Chrome (or my Android phone)
Older Windows Internet Explorer versions use unusual methods for encoding CGI strings. This has a side-effect for people using symbols in passwords when they set their password with Internet Explorer. In that case passwords fail on all other browsers including newer Internet Explorers.
I am aware of this issue since beginning and know how to remedy it. But it is low priority for me. But maybe many fans experience same trouble and do not report. So I will remedy it soon. I will post again after this is done.
Thank you for reporting.
EDIT: Fix quoting.
I personally do not need it because I use a unique and very secure password. But if fans think it is important and I can implement second-factor authentication without linking against non-C libraries or using proprietary APIs then I can add it to my to-do list.
I wonder if that's the reason that I can't log into the site using Chrome (or my Android phone)No big deal.. just wondering.
I have sold all my shares recently. Thank you all for this ride. It was a very interesting experience. Perhaps one day I will come back.
Sorry to hear. I wish you well for your future Bitcoin adventures.
I have sold all my shares recently. Thank you all for this ride. It was a very interesting experience. Perhaps one day I will come back.
Jump to: