I've identified myself as a dev many times in this thread. This is why we don't update the thread every day.

¯\_(ツ)_/¯

I am an assistant dev - I only work on the website.  

https://github.com/wlemahieu/raiblocks.net/commits/master <--- Website (Faucet)
https://github.com/clemahieu/raiblocks/commits/master <--- Coin / Network
http://tinyurl.com/hnwzfus

Website updates are going very well. Real life has caused the delays, not any development problems.

Thanks for your patience crypto-mob. The faucet will drip soon.

Thanks for the discussion and enthusiasm about RaiBlocks everyone. We're nearly finished with faucet maintenance and website updates. The delay is because we're ensuring everything is stable before we open the floodgates again. Thanks for your patience and stay tuned.

Select the hash with left click.
Then use ctrl+c or command+c to copy it.

When it happens again, please click 'Report' and email the error log to clemahieu at raiblocks . net

We are working on the delayed distributions from before.

I just do the web-dev. Clemahieu created RaiBlocks.


We're working on the distribution intervals and distributions are delayed at the moment. You can keep solving and you'll get distribution eventually for all your solves.

What is your account? How many claims does it say you did? How many did you actually do?

No ReCaptcha solves can be missed though if you receive a green 'Success' message, so it may have been a visual error.

We count your total ReCaptcha success and pay everyone their fair share every 2-4 hours. So you do not receive krai/mrai immediately after solves, you have to wait 2-4hrs.

There is more information in the 'How it works' section of the form. (https://www.evernote.com/l/AAJAWXAm_4BGEocwIcSj0hYurRF6Oj7zyd8)

Let me know if you have any other questions!

Distributions were delayed but should be all caught up in a few hours.

Correct

I'm working on making it readily available to each user. It's stored on our end.

I see 3 different distributions to that address.

Fri, 15 Apr 2016 02:00:00 GMT     -     Fri, 15 Apr 2016 04:00:00 GMT
Total Count: 59, Mrai Owed: 360
Receipt Hash: 92BB249D9D40E19657D68763DAD66F85EA8B7B0A7B05E7BEF959BD5269991D56

Mon, 18 Apr 2016 04:00:00 GMT     -     Mon, 18 Apr 2016 06:00:00 GMT
Total Count: 497, Mrai Owed: 1547
Receipt Hash: 7CA1B6B0490ABF306F8C478D4B727AFFAE201CFD10C5FFEAE44F96307C544E9C

Mon, 18 Apr 2016 06:00:00 GMT     -     Mon, 18 Apr 2016 08:00:00 GMT
Total Count: 203, Mrai Owed: 621
Receipt Hash: 9F67F2F01651D38AFDAA25AAF12C5065DCFB869972284391E9A9631F2A90D47C


Does that help?

What is your address?

An increased delay would mean that any single user could effectively solve multiple captchas over multiple VPNs across multiple accounts within any time-frame you could ever recommend. Let's say you wanted a 30 minute delay... Perfect! As an exploiter, I'd just get 10 accounts and then hop between VPN networks claiming from the faucet using my many accounts... I can now get easily 10 claims or more "per delay" if I have more accounts since they're easy to create. You think you'd be limiting people with a delay, but you're actually enabling people to cheat with a delay past 8-10 seconds.

We're pretty sure no human could really ever solve ReCaptchas faster than 6-seconds per solve given the fluctuating difficulty provided by Google. Right now, the people who put in the most hard-work / time get the reward. That seems fair but if you have any other ideas let us know.

There are more people now which is why it may feel like less. I'll be making stats available on the website shortly!

It's likely in these rare cases that the RPC server is getting overloaded and can't validate your account, causing your ReCaptcha solve to fail. I'll mention this to clemahieu.

It might appear broken but actually that success message is intended to appear under the immediately-available refreshed form after you successfully complete the ReCaptcha. If you submit before the 6-second timer, you'll receive a "Try Again" warning from the server.

Yesterday, we started caching the "available supply" number. When people visit the faucet, there were 2 RPCs being called just to obtain the "available supply". Imagine 100 users, that's 200 RPC calls just to grab 1 number which we can easily cache. So now there are 0 RPC calls when visiting the faucet page. You'll see the available supply update after distributions when it matters most. This also is a better way to spend RPC / web resources.