I think it's funny people don't believe it's him.   

He was a respected member here for a long time.  It's a hero level account that hasn't been used since he started at GAW.  Now he's using it after he obviously left!

He's giving you guys the real info, without implicating himself... I guess some folks just have to be spoon fed?

http://www.troll.me/images/ancient-aliens-guy/there-is-no-spoon.jpg

You mean like a picture of me and your Mom?   

Holding for my reply to that one.  

Definitely miaviator though.  RESPECT.

Per lolwuts' demand:  Another feature request. 

The dashboard needs Algorithm buttons, for miners who mine more than a single algo on the multiports.

The process to view how you're different algo's are mining at any given time currently involves viewing the statistics page (or the irc) to find out which coin is currently being mined (then back to the dash to select that coin).  Well, that or clicking the dashboard button until it shows all the algos you're mining.  Either way, it's pretty inefficient. 

Even being able to select the Algorithm header from the coin selection list would be awesome!

All good dude.  We're looking into it now.   

Right, so this is the best version of cgminer for modded gridseeds.  However, P2Pool mining is broken for this branch of cgminer-gc3355:
https://github.com/jmordica/cgminer-gc3355

To fix it you need this older branch (that doesn't support freqs above 1150):
https://github.com/girnyau/cgminer-gc3355/

Then you'll build the old branch, but first:

1) From the new branch, copy the driver-gridseed.c, and driver-gridseed.h into the old branch.

2) In the old branch, open miner.h and add the following code beneath line 1048:

extern char *opt_gridseed_freq;

3) In the old branch open cgminer.c and add the following code beneath line 178:

char *opt_gridseed_freq = NULL;

AND the following code block at line 1053:

static char *set_gridseed_freq(const char *arg)
{
        opt_set_charp(arg, &opt_gridseed_freq);

        return NULL;
}

After that, while in the directory for the old branch run:
./configure --enable-scrypt --enable-gridseed
make

And then you should be all set with high frequency support for P2Pool on your modded gridseed!

Thought I would share my validation results for the new client (badass work btw Tranz!).  

The following was performed on Ubuntu 12.04 64 bit.  QT and daemon source compiled without issue.

Confirmed that the new client appears to generate stake blocks correctly. (Had older coins available that were stakeworthy.)
Status: 4363 confirmations
Credit: 0.039441 CAP
Net amount: +0.039441 CAP
Transaction ID: a40bbf7671c8ff14f8ab0d9fd94b2503e4caebd0de7c2a8669bc0a41726a32d4

Confirmed solo mining to the wallet is also functional (verified internal CPU, and RPC/GPU mining).
Status: 3897 confirmations
Date: 30 May 2014 17:50
Source: Generated
Credit: 10.00 CAP
Net amount: +10.00 CAP
Transaction ID: a5a018de920af7a4096c35d19585ed55f8dc55602c7fd700c23ceb6d94072d92

Confirmed that the beta wallet is backwards compatible with the original wallet (ftm).
Confirmed coins could be sent/received.
Confirmed wallet.dat could be opened from both clients (not simultaneously), performed multiple times with no issues.  
Confirmed all coins mined on the new wallet were available from the old wallet and vice-versa.
Confirmed stability, ran 72+ hours.  No memory leaks, no thread locking.

Also performed some cursory validation on the new coin control features, and new functionality in the debug console.  And no issues to report!

It's all looking REALLY REALLY good!  Incredible functionality for a "beta".  

Would be better if someone associated with Neocoin could maybe update the "Official" thread for their coin. 

Saw this update on one of the pools I use (neo.cryptcoins.net):

5/23/14- Neocoin client updated to version: v2.2.1-neocoin.

Probably means folks should update their wallets!

It's definitely possible.  From what I read the other day it's it just a Rasberry Pi with a custom image? 

I'll see if I can find a copy of it to run on my rpi. 

That's definitely strange.  Rigs are still getting hired.  Which rig was it that had that issue?

And is there an issue with hiring rigs in IE? 

Which ISP's are those?  I've never seen an ISP that didn't give you an IP address. 

The captcha has always been there, but it only shows up after a bad password attempt. 

(Keeps folks from brute force cracking your login.)

Yeah, I mentioned to miaviator that the notice might not be completely accurate.  I had thought that one week leases were only supported for the new dynamic hourly plans.

If you go to the rig management interface, and click the "Dynamic" button, you can assign a max hourly value of up to 168 hours.  

Sorry for the confusion, I know that if the standard plans don't support it now, they will support at least 168 hours in the next update.  

Oh yeah.  Definitely still on the roadmap. 

Just a question of how long I can handle miaviators' anti-doge tirades before I put everything else on hold to knock it out! 

Not sure if everyone noticed yet, but providers have the option to accept one or the other now (LTC OR DOGE).

I can't imagine Auto-Exchange will be very difficult to implement, but it's still at least another week or two out (maybe even three).

We're spread pretty thin right now with all of the other: updates, issues, threats, tickets, scams, and fires. 

LOL.  Yes, and more than just a little bit.  (Somebody was trying to figure out the current maximum lease time in hours.)

We're up to somewhere between 550-600 hours without miaviator blowing his fuse!  

Long term leases will be available VERY soon.  

In regard to the pools not being changed back over.  Technically, we only see that issue when a rig goes offline and the lease is "auto-cancelled".  It's definitely something to do with the miner being offline when the call is made to change the pools back. 

We usually see the issue with the customer pools being overwritten by provider pools on rigs that have CGWatcher running in the background.

I'm definitely working on fixing those issues currently.  

Whenever you post a reply, the customer is notified via email with a link to your reply.  From there they can reply to you and you will in turn be notified.  (Vicious cycle).

I wasn't sure whether cluttering up the main feedback view with a lot of replies was a good idea or not.  A lot of times you get a ton of completely unrelated information that you have to look through just to view the actual feedback (i.e. this forum).

Also, this feature is still in active development, so keep the "feedback" coming.    

Yeah, I've been watching that rig for the last week.  Not sure that it's tricking LRP.  TBH I think he's exploiting an existing issue. 

At times I've seen LRP start reporting an unreal hashrate after it's been running solid for a couple of weeks.

It would be super useful if someone who rented the rig posted what speed it was actually running.

Either way, we're going to resolve the problem shortly.   

Rented the Miner02 for 48 hours on LeaseRig.net.

I wish I could say that I had problems, as the provider extended my lease more than once...  But I cannot...   

The hash rate was definitely above the advertised speed for the duration of the rental period, and from what I could determine; there was never a single issue.  Everything worked great!

This is a reliable provider!  Highly recommended!