Damn volume is low... Had a stack of bullshit guvpaper finally convert to real money and I can't buy in without crapping on my own buy values...
Be happy to let some short-term daytrader make money off of selling to my long hodl... te he!
Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 5192. (Read 9723733 times)
June 17, 2014, 12:55:42 PM
June 17, 2014, 12:51:44 PM
Which pools, exchanges and other services failed to update in time for the last fork?
We should compile a list of these, and check if they've announced that they have updated yet, and contact them if not.
Those who fail to respond saying that they've updated, well, that's 3 strikes. Broadcast the blacklist far and wide in time for the next fork.
+1 Definitely something to think aboutWe should compile a list of these, and check if they've announced that they have updated yet, and contact them if not.
Those who fail to respond saying that they've updated, well, that's 3 strikes. Broadcast the blacklist far and wide in time for the next fork.
All in agreement please upvote this for visibility:
http://www.reddit.com/r/DRKCoin/comments/28dx2e/which_mining_pools_exchanges_etc_failed_to_update/
June 17, 2014, 12:49:01 PM
I don't own a mac, I believe Chaeplin does and it's working for him. Regardless, this is what I found after some quick research.
Try this taken from Mac website. https://discussions.apple.com/thread/3941688?start=60&tstart=0
Close all windows.
Keychain Access -> click on System Roots on the left, and then click on Certifcates on the bottom left.
Check to see if any of the certificates on the right have the blue "+" symbol - this means they have custom trust settings.
There is a bug in changing the policies, so you'll have to change them via the method below. Changing them just by changing the access to "system defaults" doesn't seem to save. The method below worked for me.
Double-click on each certificate with the custom setting (blue "+"), expand the section labled "trust". Change the "Secure Sockets Layer (SSL)" setting to "no value specified". Close window - you should be prompted for the password. Double-click on the certificate again, expand trust, change the "When using this certificate" setting to "Use System Defaults". Close window, and re-enter password.
If you didn't re-enter your password upon closing the window, the setting didn't take. The blue "+" should disappear after a few seconds when it's set back to default. Once all of the certificates are changed back to default, restart Safari.
Oh my Chrome had problem. It showed 3 apple certificate.Try this taken from Mac website. https://discussions.apple.com/thread/3941688?start=60&tstart=0
Close all windows.
Keychain Access -> click on System Roots on the left, and then click on Certifcates on the bottom left.
Check to see if any of the certificates on the right have the blue "+" symbol - this means they have custom trust settings.
There is a bug in changing the policies, so you'll have to change them via the method below. Changing them just by changing the access to "system defaults" doesn't seem to save. The method below worked for me.
Double-click on each certificate with the custom setting (blue "+"), expand the section labled "trust". Change the "Secure Sockets Layer (SSL)" setting to "no value specified". Close window - you should be prompted for the password. Double-click on the certificate again, expand trust, change the "When using this certificate" setting to "Use System Defaults". Close window, and re-enter password.
If you didn't re-enter your password upon closing the window, the setting didn't take. The blue "+" should disappear after a few seconds when it's set back to default. Once all of the certificates are changed back to default, restart Safari.
I had cleared browsing data.
June 17, 2014, 12:48:12 PM
Wow. And I thought Crapple sucked less than Microshaft...
Dude...Chill out dude. Life is too short.
Fewer words than you dedicated to the reply... 
June 17, 2014, 12:43:49 PM
Wow. And I thought Crapple sucked less than Microshaft...
Dude, you clearly do have more than half a brain, but whats with you today? Buy a gram of coke? Speed? Meth?
Chill out dude. Life is too short.
June 17, 2014, 12:41:16 PM
Which pools, exchanges and other services failed to update in time for the last fork?
We should compile a list of these, and check if they've announced that they have updated yet, and contact them if not.
Those who fail to respond saying that they've updated, well, that's 3 strikes. Broadcast the blacklist far and wide in time for the next fork.
+1 Definitely something to think aboutWe should compile a list of these, and check if they've announced that they have updated yet, and contact them if not.
Those who fail to respond saying that they've updated, well, that's 3 strikes. Broadcast the blacklist far and wide in time for the next fork.
June 17, 2014, 12:39:03 PM
I don't own a mac, I believe Chaeplin does and it's working for him. Regardless, this is what I found after some quick research.
Try this taken from Mac website. https://discussions.apple.com/thread/3941688?start=60&tstart=0
Close all windows.
Keychain Access -> click on System Roots on the left, and then click on Certifcates on the bottom left.
Check to see if any of the certificates on the right have the blue "+" symbol - this means they have custom trust settings.
There is a bug in changing the policies, so you'll have to change them via the method below. Changing them just by changing the access to "system defaults" doesn't seem to save. The method below worked for me.
Double-click on each certificate with the custom setting (blue "+"), expand the section labled "trust". Change the "Secure Sockets Layer (SSL)" setting to "no value specified". Close window - you should be prompted for the password. Double-click on the certificate again, expand trust, change the "When using this certificate" setting to "Use System Defaults". Close window, and re-enter password.
If you didn't re-enter your password upon closing the window, the setting didn't take. The blue "+" should disappear after a few seconds when it's set back to default. Once all of the certificates are changed back to default, restart Safari.
Wow. And I thought Crapple sucked less than Microshaft... Try this taken from Mac website. https://discussions.apple.com/thread/3941688?start=60&tstart=0
Close all windows.
Keychain Access -> click on System Roots on the left, and then click on Certifcates on the bottom left.
Check to see if any of the certificates on the right have the blue "+" symbol - this means they have custom trust settings.
There is a bug in changing the policies, so you'll have to change them via the method below. Changing them just by changing the access to "system defaults" doesn't seem to save. The method below worked for me.
Double-click on each certificate with the custom setting (blue "+"), expand the section labled "trust". Change the "Secure Sockets Layer (SSL)" setting to "no value specified". Close window - you should be prompted for the password. Double-click on the certificate again, expand trust, change the "When using this certificate" setting to "Use System Defaults". Close window, and re-enter password.
If you didn't re-enter your password upon closing the window, the setting didn't take. The blue "+" should disappear after a few seconds when it's set back to default. Once all of the certificates are changed back to default, restart Safari.
June 17, 2014, 12:30:12 PM
It's so funny how dramatic cryptsy's graph looks, it only spans .016 to .018 and what used to be small looking variations now look huge, LOL. Been that way for some time. At least it makes a basically flat line look exciting 
The difference between 160 and 180 is a fine piece of daily profit for day traders
.True, but that's just what the chart shows, the real difference in the coin is .001 BTC, which is about $0.60. I understand if you're skilled enough to sell at the highs and buy at the lows, that this could make you pretty money, but I certainly don't have that skill. Can people really squeeze a profit out of that in practical terms?
For all I know, it's even safer than when the market is on the move, LOL
June 17, 2014, 12:23:34 PM
Which pools, exchanges and other services failed to update in time for the last fork?
We should compile a list of these, and check if they've announced that they have updated yet, and contact them if not.
Those who fail to respond saying that they've updated, well, that's 3 strikes. Broadcast the blacklist far and wide in time for the next fork.
We should compile a list of these, and check if they've announced that they have updated yet, and contact them if not.
Those who fail to respond saying that they've updated, well, that's 3 strikes. Broadcast the blacklist far and wide in time for the next fork.
June 17, 2014, 12:23:13 PM
I don't own a mac, I believe Chaeplin does and it's working for him. Regardless, this is what I found after some quick research.
Try this taken from Mac website. https://discussions.apple.com/thread/3941688?start=60&tstart=0
Close all windows.
Keychain Access -> click on System Roots on the left, and then click on Certifcates on the bottom left.
Check to see if any of the certificates on the right have the blue "+" symbol - this means they have custom trust settings.
There is a bug in changing the policies, so you'll have to change them via the method below. Changing them just by changing the access to "system defaults" doesn't seem to save. The method below worked for me.
Double-click on each certificate with the custom setting (blue "+"), expand the section labled "trust". Change the "Secure Sockets Layer (SSL)" setting to "no value specified". Close window - you should be prompted for the password. Double-click on the certificate again, expand trust, change the "When using this certificate" setting to "Use System Defaults". Close window, and re-enter password.
If you didn't re-enter your password upon closing the window, the setting didn't take. The blue "+" should disappear after a few seconds when it's set back to default. Once all of the certificates are changed back to default, restart Safari.
Try this taken from Mac website. https://discussions.apple.com/thread/3941688?start=60&tstart=0
Close all windows.
Keychain Access -> click on System Roots on the left, and then click on Certifcates on the bottom left.
Check to see if any of the certificates on the right have the blue "+" symbol - this means they have custom trust settings.
There is a bug in changing the policies, so you'll have to change them via the method below. Changing them just by changing the access to "system defaults" doesn't seem to save. The method below worked for me.
Double-click on each certificate with the custom setting (blue "+"), expand the section labled "trust". Change the "Secure Sockets Layer (SSL)" setting to "no value specified". Close window - you should be prompted for the password. Double-click on the certificate again, expand trust, change the "When using this certificate" setting to "Use System Defaults". Close window, and re-enter password.
If you didn't re-enter your password upon closing the window, the setting didn't take. The blue "+" should disappear after a few seconds when it's set back to default. Once all of the certificates are changed back to default, restart Safari.
June 17, 2014, 12:20:50 PM
I think this had been discussed before so forgive me but I think it needs to be brought up again since its ongoing.
Im unable to access Darkcointalk.org on any of the machines where I had visited the site in the past. Reseting everything that can be reset in Safari doesnt fix this. Im a experienced Mac user and Ill guarantee that if running the reset option or trashing preferences doesn't fix this, it will go unfixed on most users machines.
Surely this can be corrected on your end.
Im unable to access Darkcointalk.org on any of the machines where I had visited the site in the past. Reseting everything that can be reset in Safari doesnt fix this. Im a experienced Mac user and Ill guarantee that if running the reset option or trashing preferences doesn't fix this, it will go unfixed on most users machines.
Surely this can be corrected on your end.
Nonsense
I accessing Darkcointalk.org from my phone and 3 different machines
(incl MAC)
try again …>>
I have the same issue on safari but not chrome on mac. Despite trashing prefs, emptying cache, etc.
June 17, 2014, 12:10:03 PM
Is it time to start spamming pool operators if they have updated ? that is If they don´t any announcement on their site about it. Dont let them waste your hash on a wrong fork. 
June 17, 2014, 12:09:36 PM
I think this had been discussed before so forgive me but I think it needs to be brought up again since its ongoing.
Im unable to access Darkcointalk.org on any of the machines where I had visited the site in the past. Reseting everything that can be reset in Safari doesnt fix this. Im a experienced Mac user and Ill guarantee that if running the reset option or trashing preferences doesn't fix this, it will go unfixed on most users machines.
Surely this can be corrected on your end.
Sounds like your ISP or your Government doesn't like you visiting darkcointalk.org.Im unable to access Darkcointalk.org on any of the machines where I had visited the site in the past. Reseting everything that can be reset in Safari doesnt fix this. Im a experienced Mac user and Ill guarantee that if running the reset option or trashing preferences doesn't fix this, it will go unfixed on most users machines.
Surely this can be corrected on your end.
Or you're really, really, really stupid. Which I doubt is the case... You'd have to be so stupid that you can't even read this forum.
If you didn't dump your router's DNS cache then you're too stupid to be here.
TTL set to potato? If you've been having this problem for more than 24 hours, you should reconsider the huge number you set the cache TTL to... Dumbass. It would fix itself if you didn't break it with dumb.
June 17, 2014, 12:06:38 PM
Regarding the upcoming hard fork, would it make sense to use the Alert system? Bitcoin (and many others) has a built in alert messaging service protected by a private key in the possession of Gavin Andresen (originally Satoshi). This could very easily be used to send network wide upgrade alerts:
https://en.bitcoin.it/wiki/Alerts
+1. As far as I know Evan was thinking about implementing this indeed.https://en.bitcoin.it/wiki/Alerts
Make it a simple feature add after we get over the major hurdle, eh?
June 17, 2014, 12:04:50 PM
Very odd how DRK is very inactive on low volume going into the Fork.
It's like everybody is waiting on the sidelines to see what happens after the fork.
Not odd at all. The stupid got buttfucked in the inadvertent fork. Pain taught them. I held inaction for 2 weeks prior to that clusterfuck. I'm not so worried this time. Typical neuro-typical behavior. Go wild when you should be careful. Act careful when there's no longer a need... No understanding, clueless reactionaries... It's like everybody is waiting on the sidelines to see what happens after the fork.
June 17, 2014, 12:01:24 PM
On Mintpal...
PRICE (BTC) DRK BTC
0.01703032 1404.38987259 23.91720893
PRICE (BTC) DRK BTC
0.01703032 1404.38987259 23.91720893
June 17, 2014, 12:01:05 PM
Linux... you kidding? linux is vulnerable too.
Linux is only as vulnerable as it's operator.Microsoft only fixes problems when Microsoft is forced to admit them. There are dozens of attack vectors you can't seal because you don't know about them and never will.
Of course both are vulnerable. The matter is that on Linux you can do something about it. On Windows you only get placebo/false sense of security.
But fools will be fools. Stolen DRK will undoubtedly end up in an exchange for me to buy at some point... So go ahead and use Windows with all the aftermarket Unicorns and Fairy Dust you like... More DRK for me.
If you even ask the question "Can I run a MN on Winblows?" You're definitely very, very, very unqualified to run a MN. But go ahead and let your greed push you to do stupid things. Lack of discipline... Your loss is my gain.
If you want to make money running a masternode, don't take shortcuts. Pull your head out of your ass and LEARN. There is no shortcut.
Nailed it like a boss.
June 17, 2014, 12:01:00 PM
Hey eduffield, please update front page and titile about hard fork. This should attract more attention.
Personally, I don't read this topic everyday and I've just noticed that hardfork is coming.
THIS.Personally, I don't read this topic everyday and I've just noticed that hardfork is coming.
This thread is generally such a clusterfuck of trollshit that most people deliberately avoid it... Unbury the important news. Put it in the OP. Yesterday.
June 17, 2014, 11:55:52 AM
Linux... you kidding? linux is vulnerable too.
Linux is only as vulnerable as it's operator.Microsoft only fixes problems when Microsoft is forced to admit them. There are dozens of attack vectors you can't seal because you don't know about them and never will.
Of course both are vulnerable. The matter is that on Linux you can do something about it. On Windows you only get placebo/false sense of security.
But fools will be fools. Stolen DRK will undoubtedly end up in an exchange for me to buy at some point... So go ahead and use Windows with all the aftermarket Unicorns and Fairy Dust you like... More DRK for me.
If you even ask the question "Can I run a MN on Winblows?" You're definitely very, very, very unqualified to run a MN. But go ahead and let your greed push you to do stupid things. Lack of discipline... Your loss is my gain.
If you want to make money running a masternode, don't take shortcuts. Pull your head out of your ass and LEARN. There is no shortcut.
June 17, 2014, 11:44:13 AM
The stability of this coin is soo sexy. After stability comes rapid increase. Always. Friday will be fun.
I've never taken Viagra, but I'm sure this is what it feels like
Jump to: