hrm, it could be the period in your user name, my site fakes an email and password since you wont be using them as a hive authed user here. It just makes it your [email protected] to fill in the db but its never going to need or use an actual email for hive authed users - we dont need/use those on hive apps.
Ill check that my site is not tripping on you having a period in your user name, which in turn makes an invalid email address and it may be denying you entry via my validation rules, but its a stretch. I cant imagine you havent had issues lots of places though with a period in your username, most places require alpahnumeric only to avoid punctuation in critical account ids or addresses, since periods are used so heavily for other reasons in http/tcpip and programming syntax - and they tend to blow shit up and are best avoided.
Nice, Im looking into my code to see why that would fail validations, one of my libraries does email validating against lengthy lists of what are called "RFC"s which are the rules for internet standards published by internet governance committees out there in the world. Maybe the format breaks some kind of rule. I can code to fix it and allow it, since my email addresses merely exist to plug a hole for now in case they ever become relevant for non-chain accounts to login with or we decided to use them for things like notifications if the user wants to volunteer an address for such things.
@coininstant you found a bug on my side, confirmed. I just fixed my code to allow user names with the following patterns.
Now allows letters, digits, underscores, hyphens, and periods.
Previously period was not allowed in a user name using pretty default typical username validation libraries. I overrode them to allow it as noted above.
Should work fine for you now, on future attempts with your period-name
You should never ever see that page in the way I have it commented out right now, this tells me you didnt get any of the hivesigner auth stuff in your return back from their site to mine via the call back redirect. I'm feeling hivesigner issue here, as per my other replies interlaced with your latest replies here.
I could see the hivesigner stuff in the url, however the console log in the browser was missing that. Tried with another account, was routed to the same place. Will try again later.
I just tried it again with a fresh account using chrome here on PC and no issues at all.
When hivesigner send you back to my site with an "OK good guy here" token, I consume it in a script and then push you to the profile settings dashboard logged in. So you will only see that long token url flash up for a moment on the way back before redirecting to a logged in page.
Unable to reproduce, feel like that denied login and safari and then chrome got your auth and link caches mixed up, but im not sure, thats just my gut at the moment, a clean browser cache and clean hivesigner account and it should be fine.
hrm, it could be the period in your user name, my site fakes an email and password since you wont be using them as a hive authed user here. It just makes it your [email protected] to fill in the db but its never going to need or use an actual email for hive authed users - we dont need/use those on hive apps.
Ill check that my site is not tripping on you having a period in your user name, which in turn makes an invalid email address and it may be denying you entry via my validation rules, but its a stretch. I cant imagine you havent had issues lots of places though with a period in your username, most places require alpahnumeric only to avoid punctuation in critical account ids or addresses, since periods are used so heavily for other reasons in http/tcpip and programming syntax - and they tend to blow shit up and are best avoided.
I'll test it out now with an account without a period to check.
That will be interesting and its a notable uncommonality but it should have worked anyway
OK I guess it was indeed the dot since I was able to log in with my account. Good catch!
Nice, Im looking into my code to see why that would fail validations, one of my libraries does email validating against lengthy lists of what are called "RFC"s which are the rules for internet standards published by internet governance committees out there in the world. Maybe the format breaks some kind of rule. I can code to fix it and allow it, since my email addresses merely exist to plug a hole for now in case they ever become relevant for non-chain accounts to login with or we decided to use them for things like notifications if the user wants to volunteer an address for such things.
@coininstant you found a bug on my side, confirmed. I just fixed my code to allow user names with the following patterns.
Now allows letters, digits, underscores, hyphens, and periods.
Previously period was not allowed in a user name using pretty default typical username validation libraries. I overrode them to allow it as noted above.
Should work fine for you now, on future attempts with your period-name
You should never ever see that page in the way I have it commented out right now, this tells me you didnt get any of the hivesigner auth stuff in your return back from their site to mine via the call back redirect. I'm feeling hivesigner issue here, as per my other replies interlaced with your latest replies here.
I could see the hivesigner stuff in the url, however the console log in the browser was missing that. Tried with another account, was routed to the same place. Will try again later.
I just tried it again with a fresh account using chrome here on PC and no issues at all.
When hivesigner send you back to my site with an "OK good guy here" token, I consume it in a script and then push you to the profile settings dashboard logged in. So you will only see that long token url flash up for a moment on the way back before redirecting to a logged in page.
Unable to reproduce, feel like that denied login and safari and then chrome got your auth and link caches mixed up, but im not sure, thats just my gut at the moment, a clean browser cache and clean hivesigner account and it should be fine.