There was a time when Sync was worth around 2BTC each. Wouldn't it be nice if that came back around!

Still running my wallet 24/7 and have been pretty much since the coin launched - hoping for some sort of revival.

This was originally about DRM vs the consumer, but I thought it deserved a little retouching for the current situation

Yes - exact same issue here in Firefox 31.

I take back my previous suggestion about taking down cloaktalk - I was looking at the un-labeled date column which has an "activity" header - it's confusing to say the least.

I have suggestion which is slightly opposite to moving everything to cloaktalk.org. I personally think that cloaktalk.org is probably doing more harm than good at the moment, and should be shut down unless the dev team regularly posts updates there. On checking out the cloaktalk forums, the latest post from the dev team in either "Project Development" or "Announcements" is more than a month old, and there is very little activity. I realize that they are busy as hell doing tons of actual development, but you'd never know it to look at that site.

Love it... trolls claiming to have "bought in at 1k" - it was around 10k right after it hit the market, and I was fortunate enough to buy a few hundred at that price; I'm pretty sure it's never been at 1k. Trolls suck.

Man... I was not around this morning when Cloak dipped down to 120k. Very bummed that I missed the buy opportunity.

If PoW is over, please update your OP to reflect that fact and remove the mining pools from it as well. Most of us don't have time to read dozens of pages for every single coin that's out there.

I have a small suggestion for the op post. There are people (not me) who don't read the thread every day, and it's impossible to tell when the mandatory wallet update came out or even if it is a different version than they have installed. Instead of just saying "mandatory update" and providing a wallet link, it should also display the wallet version and release date.

While we're boasting about awesome deals, here's my best:

date:06/04/2014 06:38:42 AM   type:Buy   rate:0.00010000   quantity:400.00000000

I have bought a lot since then, but I really wish this first buy had been for a WHOLE lot more.

If there is a flaw in POS of this and other coins, the truly responsible thing to do would be to notify the devs of the other affected coins directly before releasing anything to the public. Simply releasing details of a flaw to the public after fixing it for only your own product is exactly what Cloudflare did with the Heartbleed OpenSSL bug.

I know there are a LOT of POS coins out there (both proof-of-stake and piece-of-shit), and contacting each and every dev individually would be nearly impossible, not to mention extremely time-consuming. I unfortunately don't have a constructive suggestion for what to do here, but this is factor that should be considered.

FYI - the official word from IRC on what happened with Bittrex:

bittrex-rami  CLOAK restored
bittrex-rami  index went bad, had to rebuild

In other words, it was a bittrex internal issue, just as predicted.

Update: my $34 investment is now worth 24 effing cents - 0.7% of its purchase price. Glad it was only $34.

Man... glad I didn't invest TOO much with this coin - it's taken a 92.7% hit in value since I bought in at .00023797

For those worried about there still being a 100% POS interest rate, keep in mind that it is only 100% annually, and only for those with an open wallet. The current total coin supply is still just a little over 1040.

Hey - quick note on the math in the video to calculate the max buy:

btc = quantity * bid * 1.0025

to solve for quantity, divide both sides by bid*1.0025:

quantity = btc/(bid * 1.0025)

This works out with the numbers in the video around 7:00:

quantity = .00590745 / (.000732 * 1.0025) = 8.050161481542047

Very nice! Looks like you got PHP working on the server, too. Good stuff, and all working here!

I made some modifications to the market scripts - parsing is greatly simplified, and they will now all accept a "callback" parameter which allows them to function as JSONp. This will allow them to be hosted on any site without worrying about cross-site-scripting security.

getBittrex: http://pastebin.com/bLKjsQAH
getAGX: http://pastebin.com/kSkc6h1f
getCoinnext: http://pastebin.com/1XXQ9hai

Calls to bittrex & coinnext APIs cannot be made directly from the client due to cross-domain javascript security restrictions unless they offer JSONp functionality - I don't believe that either of these API offer JSONp. Standard AJAX calls must be made to the same domain as the page calling them.