You’re probably all running storage nodes, but we recently launched this new sign up flow to replace our waitlist. After letting us know if you meet the requirements, you provide your email and receive an auth token soon after (same day or a few days after).
Has anyone used the form? We would appreciate feedback on it!
I have test it und it works with Linux Mint 19.2 and Chrome Version 78.0.3904.70 (Offizieller Build) (64-Bit) with enabled Adblock. For me there is a small issue. Somtimes it’s difficult to set the checkmarks because the range for making it in the square is to small.
whole registration works, but it’s difficult to set the checkmarks because the range for making it in the square is to small
Linux Mint 18.3, Firefox 70 + uBlock Origin, Chromium 77 + uBlock Origin
FYI, if you use the same email address to request multiple auth tokens, you will get the same one the next time, only if you have not yet claimed/used the last one to sign a node identity before. Once you have claimed a token, you can again use the same email address to request a new one for another node (which of course should be running on its own IP and location).
I used the form 3 or 4 days ago and still haven’t received the auth token. Just filled out the form again with the same email address to see whether it speeds it up.
What you are seeing here is an unfortunate result of our automatization to send auth tokens to our SNOs who request them. Our certificate authority only extracts the email address you share with us in the form in order to put it in a queue to generate the auth tokens automatically, so we can send you the invite email message with the new auth token right away without having to wait for bulk sends like we had before, when we send emails periodically in batches. We are NOT using this to track you.
Please state what ad-blocker software you are using that produced these results you showed in the screenshot. Our Martech team will contact them and any other such sites that are mis-identifying our form as tracker to ask them to correct this so that it no longer gets misidentified as tracker.
Please could you send us the email address you used to request the auth token in a support request on support.storj.io so we can find out why you did not receive a new auth token.