4 ms·
Okay, I understand if the form is sending my email address to check if I am an existing customer. I can understand if it wants to check if the username I want i
by DjangoReinhardt 13y ago
Okay, I understand if the form is sending my email address to check if I am an existing customer. I can understand if it wants to check if the username I want is available. Both of these are valid actions and usually helpful for new customers.
However, I can assure you that the email is intentional. Here's the text of the email:
> We noticed that you started signing up for Rackspace Cloud, but you didn’t finish. Your cloud is ready for you, and it says it’s getting lonely.
Apart from the cheesiness of the text and the language, one thing stands out clearly: The process that handles your form submissions knew that I didn't finish signing up.
> Don’t let your cloud be lonely and sad – finish signing up for Rackspace Cloud and start using it to spin up a website, an app, or any awesome new project.
> You can finish your sign-up HERE.
[ed. I have removed the link associated with `HERE`]
Again, ignoring the cheesiness of the text, this sentence clearly indicates that the email is triggered when someone (like me) DOESN'T finish signing up. While I appreciate your proactive attempts to acquire potential customers, this definitely veers into creepy...
> If you have any questions about signing up or our products, give us a call or shoot us an email. We're here to help!
One question: How do I ensure that my email is NOT added to any of your newsletters that I MOST DEFINITELY - NOW OR EVER - DID NOT SIGN UP FOR?
(Apologies for the all caps. I am a little unnerved by this. I never expected RackSpace to do this sort of a thing.)
- kordless 13y agoNo apologies necessary - it's your data. You have a right to say how it makes you feel. I opened a ticket on it for you: https://github.com/rackerlabs/devsite/issues/99 https://github.com/rackerlabs/devsite/issues/99. The dev code (which is on Github) doesn't actually implement the signup flow, so keep in mind there won't be a resulting commit for it. However, we will update you there on what we find out!
- DjangoReinhardt 13y agoThanks for raising the issue. Will follow it on GitHub as well. Also, thank you for understanding and accommodating my outburst, as well as acting on it speedily. I sincerely hope (and would like to believe) that this was a one-off phenomenon and the resulting mess was completely accidental and unintended. I would also like to request you to not judge me if I reserve my opinions until I am assured otherwise. I assure you I am not holding a grudge; I am just being cautious, that's all.
- kordless 13y agoI hear you, and agree with prudency when dealing with trust issues. Tell me what you think about this: http://www.stackgeek.com/blog/kordless/post/a-code-of-trust http://www.stackgeek.com/blog/kordless/post/a-code-of-trust. It's an important topic!
- jnoller 13y agoJust like kordless said: I concur, this is not good. I'd be just as annoyed as you, so please accept my personal apology. Kord has already filed a tracker issue for this, and I am emailing this straight to the internal teams that control signup. Again: I'm sorry
- DjangoReinhardt 13y agoI just replied to kordless' post. Thank you for the apology - it does mean a lot, given the circumstances. I saw the issue on GitHub and I am following it. As I mentioned in the other post, I sincerely hope (and would like to believe) that this wasn't intentional. Please understand that, as a consumer and a newbie developer, I will (kinda) hold you guys to high standards. A large part of my learning process involves 'watching' you guys make stuff, which I eventually try to emulate. Therefore, when something like this happens, it is quite unnerving. I hope you understand that, I am not holding a grudge; but merely being cautious.