Forum Replies Created
January 17, 2019 at 10:11 am in reply to: Reset my password, now JSE requires 6 digit 2FA. However I never set 2FA. #8037
Will go through this with you on Discord but for anyone else:-
Click “Restore 2fa”
Enter email and 2fa backup key
Scan the QR code with either Google Authenticator or Authy (mobile apps)
Enter six digit code to log in.
Yeah that’s the same issue we are getting here. Thanks again for your help. It is very much appreciated by ourselves and all the publishers I’m sure.
Have forwarded this on to John to take a look. Where did the firstname.lastname@example.org email address come from I don’t think that is in use which is why it would bounce. I’m guessing Google play so will take a look there but not sure why that’s been used. Apologies.
Yes withdrawals to ERC20 wallets are currently only available via the web platform at https://platform.jsecoin.com
You should be able to login and make a withdrawal without disturbing the mining on your desktop app.
Yeah if any Russian speaking users could contact them that would be a big help. You have our consent to contact them on our behalf. Thank you for this.
We are still waiting for a reply here too.
Rakuten Linkshare wouldn’t terminate your account because of having mining scripts enabled surely??
I scanned through their terms and couldn’t find any mention of crypto or mining:-
I can’t see any reason why a network would terminate your account for this. Have you tried contacting a rep and asking why your account was terminated?
Could you provide some feedback just to set other users minds at ease once you’ve contacted them.
We spoke a bit about it in the Telegram group a while back and it was generally agreed that the pin should be imutable. Email back up would remove the security benefits for other users, SMS/Whatsapp backup is expensive and impossible (currently) to roll out globally.
I know it’s frustrating for anyone that’s lost it but it’s going to be a familiar number. I can’t imagine anyone would use a completely random number that they haven’t recorded somewhere safe. The network allows 3 guesses per six hour period.
We don’t have the man power currently to do individual support and recovery based on ID checks for lost pins but this might become an option in the future for anyone that has funds sitting in an account with no access.
Anonymous. Do you have Ethereum in your account that has the JSE tokens?
You need a little bit of ETH (less than 1 USD) in your account to cover network fees whenever you transfer ERC20 tokens. Another reason the transaction could be stuck in pending is because the gas fee is set too low. This could be what Metamask recommended at the time but the Ethereum network has been under quite high usage recently which has pushed prices up.
You haven’t been robbed and this isn’t something anyone in the JSE team is responsible for or has access to as we are reliant on Ethereum’s network for the transfer of ERC20 tokens.
Metamask has some support information here which might help too: https://metamask.zendesk.com/hc/en-us
Nijaz, notes on your account are:
pub fraud – stats indicate fake traffic- site doesn’t exist
– Are accounts limited in any way? Basically is an account with many sites have the same opportunity per site as an account with only 1 site?
No your sites with multiple domains would be treated exactly the same as if they were coming from a single domain or an account with a single site.
– What is the algorithm used now to decide who earned a ticket for the lottery system and are the limitations based on sites or accounts?
It’s based on unique opted in visitors and how long they stay on site. So a unique (24hr) user visits the site who is either already opted in or clicks the opt-in button. The mining starts and some client data is sent to the servers which is recorded for machine learning analysis. Lottery tickets are produced when client “quality” reaches a certain level and then distributed every x minutes. The lottery is run every 30 second block which distributes rewards to pending for 7 days before they are paid in to the clients account.
We pushed out an update on the first day which meant that anyone with desktop traffic earnt a lot more and anyone with mobile earnt a lot less. This has been rebalanced and we’ve been tweaking the algorithm every day since. There’s going to be another update today and I think we will continue to tweak, analyse data, tweak for a while yet until it’s as optimal as possible.
There’s been quite a few changes since the original update which is why there are fluctuations in the daily earnings. We are trying to balance it out so that everyone is happy (an impossible task). Hopefully we are getting closer but likely there will be further updates in the near future as we tweak things according to the data.
I can’t understand why more visitors sitting on the site for longer wouldn’t bring in more revenue. The opposite should be true more visitors + longer on site = more earnings. If it’s low volume it could just be variance or it could be a traffic quality issue if you are buying the traffic from a 3rd party or it could be to do with the above and we are changing things while you are running tests.November 26, 2018 at 3:12 pm in reply to: website earnings based on average time on site not working #7822
The first day we launched the changes there was an imbalance in the algorithm that meant that publishers with a lot of desktop traffic were earning a lot more than publishers with mobile traffic. We’ve been tweaking it pretty much every day since and publisher earnings have been a bit volatile. We are trying to balance it so that it’s fair and evenly distributed across the network. However every time we change something there are going to be some publishers that earn more and some that earn less because of the fixed distribution. We want to reward sites that have genuine traffic and engaged users more than sites where traffic bounces or comes and goes very quickly. There is added value to the mining pool for time on site and this should be rewarded too in our opinion. It’s still a work in progress and probably something that will be under constant development and continual improvement for the foreseeable future.
This isn’t currently possible in the publisher mining. You could potentially ping the subid to get earnings balance but this would need to be done server-side really to protect the API key.
Looks good to me. I’ll forward it on to Dave he loves anything to do with outdoors lifestyle.