When generating an invitation token (at the following URL: https://invite.maidsafe.net/update_ip.html?...) The distinction between current IP and registered IP isn’t made clear to the user, which caused some confusion for me. It’s probably worth sticking something similar to this underneath the “Set IP” button:
Please click on the Set IP button to update your registered IP address, your invitation token will only work if your registered IP matches your current IP.
In addition, browsing to any URL on the invite.maidsafe.net domain which requires you to be authenticated (while you currently aren’t authenticated) provides the user with a useless “Please Wait” message which never updates, it’s probably worth adding some sort of check on page load:
if (authNeeded && !authorised) { redirect('login'); }
@Shankar That’s perfect - and looks much better from a design perspective. Thanks for getting that done so fast - I had already figured it out obviously, but it helps other users to adopt the platform.
Hi this might not be the best place to raise my query, but here goes.
Working through the authentication process have his a road block at the last? step
receive a message Invitation already claimed. Suggests that I may already have performed the authentication
already - but don’t believe so. Quite possible the invitation has been used in a failed (mismatched IPS)
attempt.
Now I don’t see my way forward - and given failed attempts what my final login codes might be.
