[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[miningpros]

Margin / Leverage Trading is interesting for Whales , thats what Bitfinex is different then just an exchange , thats why the next step is interesting

[Enzwell]

Margin / Leverage Trading is interesting for Whales , thats what Bitfinex is different then just an exchange , thats why the next step is interesting

More wall street folk, who actually understand market trends and psychology, taking advantage of the crypto-geeks?

[Lauda]

I hope you Dark holders are selling your coins before the Darkdrop/swich to Cloakcoin..

Stop spreading FUD. Nobody in their right mind here cares about other coins.

[roede94105]

                         spammy spam spam

Stop the spam already. And that's not how it works. Too many variables.

[tuneman1980]

DarkCoin is currently the top daily performing coin on: http://cryptocoinstats.com/

[Minotaur26]

                          !!! INTERESTING NEWS !!!!

Darkcoin , remember that after LTC was introduced margin trading on Bitfinex it exploded on June 24 2013.
It was introduced beginning of June 2013 , so couple of weeks thereafter Margin trading was introduced.
Darkcoin was also introduced to Bitfinex couple of weeks ago......... , could be any day now   

It's not news. It's pure speculation based on how LTC responded around a similar time period. All we need is people interpreting this as news and then July will come and further disappointment because it didn't come to fruition.

you have a point there. But do you know of any other coin that got paired against USD? Bitfinex is more than an exchange, and not it's core business.

Margin Trade, has not being introduced to Darkcoin yet, and yes it will be a big deal as it will open new financial instruments and will bring new capital into the coin.  I am not expecting Bitfinex to add margin trading until we go past the hard forks and show some stability in these events, but once they do it should definitely  give the coin a boost. No other coin besides BTC and LTC is even close to this, Darkcoin is already there it could happen soon but I dont think it will be before RC4.

[LastUpdateDate]

does dark gone?

[Minotaur26]

does dark gone?

Could you elaborate on your question.  Darkcoin is very much active and here.


EDIT: Just read your post history, I guess you are a fan of cryptic haiku like questions.  Here is a haiku for you:

lend me your charts,
dark as ebony,
for a pillow on my journey.

[Enzwell]

It's always cool when people get their spelling and sentence structure correct.
(Because that actually means that they have something of a clue about being programmed by the corporate industrial complex.)
Which certainly happens far too seldom around here.
(Giving some leeway to the foreigners.)

[xcapator]

Is anyone else having trouble accessing darkcointalk.org?

nope, site is up and running smoothly, try to clear your cache

[Facenose]

Is anyone else having trouble accessing darkcointalk.org?

Ongoing mystery problem. Try Firefox.

[naxin]

Is anyone else having trouble accessing darkcointalk.org?

Ongoing mystery problem. Try Firefox.

I disagree. There are few mystery problems with computers, there are however, lots of mystery problems with users. The problem is people are not actually listening.

I'm looking at the DNS records and while the TTL is *way* longer than recommended, it still would have expired days ago at this point. Other than that, there is nothing ambiguous about them, no poorly setup load balancing type thing, just a basic setup pointing to one server at a very reliable provider.

Clear your browser cache, flush your DNS (windows = [open cmd prompt] ipconfig /flushdns) and it should work.

If it still doesn't, open a cmd prompt and type: ping darkcointalk.org

Code:

nathan@nathan-desktop:~$ ping darkcointalk.org
PING darkcointalk.org (85.159.209.13) 56(84) bytes of data.
64 bytes from darkcointalk.org (85.159.209.13): icmp_seq=1 ttl=45 time=116 ms
64 bytes from darkcointalk.org (85.159.209.13): icmp_seq=2 ttl=45 time=111 ms
64 bytes from darkcointalk.org (85.159.209.13): icmp_seq=3 ttl=45 time=110 ms
64 bytes from darkcointalk.org (85.159.209.13): icmp_seq=4 ttl=45 time=111 ms

If you see something besides 85.159.209.13, you have a problem.

[GhostPlayer]

Is anyone else having trouble accessing darkcointalk.org?

Ongoing mystery problem. Try Firefox.

I disagree. There are few mystery problems with computers, there are however, lots of mystery problems with users. The problem is people are not actually listening.

I'm looking at the DNS records and while the TTL is *way* longer than recommended, it still would have expired days ago at this point. Other than that, there is nothing ambiguous about them, no poorly setup load balancing type thing, just a basic setup pointing to one server at a very reliable provider.

Clear your browser cache, flush your DNS (windows = [open cmd prompt] ipconfig /flushdns) and it should work.

If it still doesn't, open a cmd prompt and type: ping darkcointalk.org

Code:

nathan@nathan-desktop:~$ ping darkcointalk.org
PING darkcointalk.org (85.159.209.13) 56(84) bytes of data.
64 bytes from darkcointalk.org (85.159.209.13): icmp_seq=1 ttl=45 time=116 ms
64 bytes from darkcointalk.org (85.159.209.13): icmp_seq=2 ttl=45 time=111 ms
64 bytes from darkcointalk.org (85.159.209.13): icmp_seq=3 ttl=45 time=110 ms
64 bytes from darkcointalk.org (85.159.209.13): icmp_seq=4 ttl=45 time=111 ms

If you see something besides 85.159.209.13, you have a problem.

Or just drop 85.159.209.13 onto your browser and just use that for a few days, should revert back to normal using the DNS URL.

[GhostPlayer]

 Wow... did we just actually have an intelligent comment, instead of trolling?

 cool!

EDIT: Damn.. just as I wrote this, the post was gone. What gives?

[thelonecrouton]

I disagree. There are few mystery problems with computers, there are however, lots of mystery problems with users.

Speaking as a sysadmin with currently only one user to put up with (ahem) I can confirm this.  

[Facenose]

Is anyone else having trouble accessing darkcointalk.org?

Ongoing mystery problem. Try Firefox.

I disagree. There are few mystery problems with computers, there are however, lots of mystery problems with users. The problem is people are not actually listening.

I was just trying to jeer you guys into finding the problem, and thanks!

- I had tried flushing cache, and just tried clearing DNS on my Lion and Mountain Lion machines using Apples directions to no avail.

sudo killall -HUP mDNSResponder

I'll try using the IP for a few days.

[Facenose]

http://85.159.209.13 or https://85.159.209.13 not working either. Am I typing it right? Pings good.

[sterlingcapital]

Is anyone else having trouble accessing darkcointalk.org?

Ongoing mystery problem. Try Firefox.

I disagree. There are few mystery problems with computers, there are however, lots of mystery problems with users. The problem is people are not actually listening.

I was just trying to jeer you guys into finding the problem, and thanks!

- I had tried flushing cache, and just tried clearing DNS on my Lion and Mountain Lion machines using Apples directions to no avail.

sudo killall -HUP mDNSResponder

I'll try using the IP for a few days.

tried entering 85.159.209.13 into safari and it says ssl got rejected, works in chrome on the same mac

[Facenose]

tried entering 85.159.209.13 into safari and it says ssl got rejected, works in chrome on the same mac

It was coming up with a selection of SSL certificates on my 10.9 machine, and in that case removing both of them from the keychain fixed the whole problem. Removing all similar looking certificates on my older machines does nothing.

- BTW Heres how to flush DNS on 10.9 give it a shot:

dscacheutil -flushcache;sudo killall -HUP mDNSResponder

[turk-fx]

Is anyone else having trouble accessing darkcointalk.org?

Ongoing mystery problem. Try Firefox.

I disagree. There are few mystery problems with computers, there are however, lots of mystery problems with users. The problem is people are not actually listening.

I was just trying to jeer you guys into finding the problem, and thanks!

- I had tried flushing cache, and just tried clearing DNS on my Lion and Mountain Lion machines using Apples directions to no avail.

sudo killall -HUP mDNSResponder

I'll try using the IP for a few days.

tried entering 85.159.209.13 into safari and it says ssl got rejected, works in chrome on the same mac

It gives SSL expired error, but able to fallback to HTTP. Probably safari does not fall back to HTTP from HTTPS.