-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
what if i setup a ripple-client of my own site? #35
Comments
@filod You are correct that by the current implementation either you have to have people get email activations from the Ripple Trade blobvault, no matter what client they are using, or run your own blobvault. I cannot comment on what the RL policy will be in the future, but it's my understanding that eventually they want Ripple Names to migrate from the blobvault to live in the ledger itself (!!!) |
Pending that developers actually want to use our email verification service, we're planning to make changes to the email branding. So I can understand what you need, what do you want to use the ripple-blobvault for? |
any news on the re-branding email subject? |
The emails are now generically branded. Your workaround is coming! We are actually removing the need to verify emails in order to generate Ripple names. We are working on that right now. |
Thanks! |
No, you cannot change the email message. But, when we remove the requirement to verify an email address in order to create a user in the blobvault, you can send your own verification emails (or not). If you need more details, feel free to email me! |
Hi, any updates on this subject? I really need to change the verification emails.... |
You can fork the blobvault, the only implication is you will be using your own namespace instead of ripple names - ripple federation has done this: https://client.ripplefederation.org/#/register though not ideal, another thing you could do is provide a proxy email for the user, such that the ripple emails get sent there rather than your user. |
Hi! Thanks for your answer! |
Hello, |
The best you can do at the moment, since the user does not care about the On Thu, Dec 11, 2014 at 12:07 AM, linhtinh11 [email protected]
|
I'm running my own blobvault and works like a charm. If you don't need to interact with ripple names it's a very good solution. |
https://github.com/ripple/ripple-blobvault/blob/master/lib/email.js#L18
According to this line shows above, when user register on 'mysite.com' (which i setup a ripple-client of my own), he will receive an email comes from 'ripple trade', that will confuse people who nerver knows ripple.
I have tried to fork
ripple-blobvault
of my own . but in this way, people will not have a 'ripple name', and they can not login 'mysite.com' with their 'ripple name' either.Any suggestions? Should the 'email activation process' be removed from 'register process' ?
The text was updated successfully, but these errors were encountered: