Topic: [ANN] 🔥 NEW β-faucet 🔥 (Read 372 times)

Did you read the info found if you click the "i-link"?
Or the FAQ? (The "?" link.)

Once the address has been verified, the button get's enabled and you should be able to click it.

Anyway, if the page get stuck for some reason, just reload it.
You don't have to wait for the ads to load, you can enter the address anyway. If the spinner is active however, it's trying to load something important and you have to wait.
There are still one or two little oddities that are popping up once in a while, but the code is working for me and the people that have helped me to test it out.

It's important that you have no adblocker or popup blocker running. I think a popunder-blocker is enabled by default in chrome, it needs to be disabled.You also need to have javascript enabled and allow cookies.
Internet Explorer and Edge are known to cause problems in general since they very often don't support the same functions as the rest of the browsers on the planet. For some freak reason Micropuke seems to think it's ok to force publishers to write their code specifically for them? Go figure...
Proxies are not allowed since proxy ips don't generate any revenue.

Why popunders and ads? It's simple, The faucet needs to get revenue somehow...
people watching and clicking ads are what keeps the faucet up and running. But, I have tried to cut down on ads in a big way to keep it loading faster and offer a more pleasant experience.

If it's still not working right, please send me a pm so I can dig a little deeper. Since, it's working on my end and I'm not getting ant error logs, the problem must be hiding...

All the faucets have been configured now and should be fully operational.

P.S. I've tried to optimize the faucet for mobile users as well.

https://kemafaucet.com/beta

unable to claim as the page is loading

also cannot  click claim button

Security update almost complete.
β-faucet is operational but the other faucets still have some configuration left before they go back online.
I should have everything up and running by tomorrow if all goes well.
Faucet timer is gone and the reward increases over time.
I also took the opportunity to include a loyalty bonus that increases with 1% for each consecutive day that you claim from the faucet. (Up to a maximum of +100%)
If you miss a day, it falls back to 0%.

And now the β-faucet has had another facelift.

I’ve received some critique for my faucets being “complex”...
So, this time I’ve really tried to simplify matters.
1. Enter wallet address
2. Click power-gauge to make claim. It’s round, pretty big and placed in the middle of the screen, you can’t miss it.

The longer you wait between claims, the more power = higher reward.
(You should be able to make a handful of claims with full power each day. )

If you really hate short links, just click the checkbox for “I want a smaller reward”.

β-faucet = testing new code, please report back any bugs so that I can fix them.

New faucet script launched for all Kemafaucets. 

Ok, since I'm not seeing any responses here regarding the popunder question, I'll justy go ahead and give it a try.
Popunder inserted and rewards raised!
Feedback is welcome.

P.S. At the time of writing the average reward is somewhere in the 16-17 satoshi area.
But as I’ve mentioned earlier, it can be both higher and lower depending on a range of factors.

No interest in that one?
+1 popunder = higher reward, or stay as is?

Pop quiz: What would you prefer? I add a popunder ad and raise the reward, or stay as is?

I'd have to do some testing to see exactly where we would end up rewards wise, but it should easily be able to add a couple of satoshi on average.
So, it's pain vs greed here, lol.

Lol, I didn’t even notice.
And yes, for sure, now that it’s operational it’s time to take care of things like that.

Ah, I probably didn't make myself clear with "You may want to change KemaBCH?"

I meant that the payout on FaucetHub shows as faucet KemaBCH (see screenshot in my previous post) while paying BTC, this may confuse users? Not a big deal but anyway, just mentioning... 

Awesome
And yeah, since this is the β-faucet... Successful features will definitely carry over to the regular faucets.

^ Working now! 



Image link: https://i.imgur.com/SJDea6d.png

Did a claim with and without shortlink, working and paying!

PS: You may want to change KemaBCH?

Greets!

I think I got it!
Fixed another typo, and it worked when I supplied a new address for testing.
So, (fingers crossed) it should work fine now.

Google Chrome, after clicking "Login":

*edit*= removed address, pm me if you need it

After that I'm stuck, page just loads with that error! 

Thanks, I’ll get right on it.
It’s incredible how everything is working when I test things and then go wonky for other people?

Edit. Well that was a quick fix. at least.
Try now...

P.S. Since people are so nice and helping out I decided to up the reward just a little.

just tyed to login with my normal faucethub address and got this error after login :
 Catchable fatal error: Object of class stdClass could not be converted to string in /home/kemafa5/lib/model/ip.php on line 120



regards

Had another oops *facepalm* moment, found a typo in the code dealing with clearing IP's.
Anyhoo, that too is fixed now.

Edit. I can see in the statistics that claims are registering now. 

This is actually somewhat funny, you were in the wrong page to begin with.
Use this link to go to the correct page.
The URL for the β-faucet is https://kemafaucet.com/beta

Now, it was still a good thing because it did force me to check browser support.
And, I did find problems...
Everything should be working now though.

I have Javascript and cookies enabled though.When I clicked the green boutton "Bonus" after completing the captcha and filling my address I get an error:

Sorry for being imprecise earlier.
Ps: I use Google Chrome (latest version I guess?)

Although it's a terrible inconvenience when something like this happens it is good to catch it early and fix the issue.
It works perfectly in Opera and in Chrome, both on PC, iPhone and iPad.
MS Edge, FF and MS Explorer are showing errors, some handles it gracefully others not so well.

Somewhere I must have used something that only works in Chrome?
I'm on it...

But for people using Chrome it should work as it is.

Update, it appears Cloudflare was causing issues for Firefox and MS Edge, tweaking the settings seem to have fixed it. Firefox and MS Edge appear to be fully functional now.