You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.
This is a discussion issue for long term when it becomes relevant.
App edition: Business/enterprise
Each potential business client for our app/service is different, they might be very impressed by the fact that its blockchain based cloud storage, but they might know little to nothing about the underlying platforms apart from what we inform them on our website.
In the back-end of our service a Storj account is made for each customer, this to avoid centralization and reduce the risk of losing everyone's data if our central account were to get compromised. The easiest way to implement this in a decentralized manner is use their simple-authentication details (email + password) of their Goobox account and mirror the details to create a Storj account. The issue here however is that when registering a account via the app ( which uses Libstorj), the email will be sent to the users's email address. As we don't have access to the client's email account this poses a number of issues including:
induces confusion, users are using Goobox yet they get a account confirmation email from the Storj bridge, this induces doubt as they might not know what exactly Storj is and why they are getting the email, this again induces confusion which turns people off.
Risk, the Storj bridge confirmation email might end up in spam, they might delete it because its not from us. All of this would prevent them from confirming their Storj account.
Ease of use, having to confirm their account twice (one time from us and once from the bridge) is just not user friendly at all.
This is a discussion issue for long term when it becomes relevant.
App edition: Business/enterprise
Each potential business client for our app/service is different, they might be very impressed by the fact that its blockchain based cloud storage, but they might know little to nothing about the underlying platforms apart from what we inform them on our website.
In the back-end of our service a Storj account is made for each customer, this to avoid centralization and reduce the risk of losing everyone's data if our central account were to get compromised. The easiest way to implement this in a decentralized manner is use their simple-authentication details (email + password) of their Goobox account and mirror the details to create a Storj account. The issue here however is that when registering a account via the app ( which uses Libstorj), the email will be sent to the users's email address. As we don't have access to the client's email account this poses a number of issues including:
induces confusion, users are using Goobox yet they get a account confirmation email from the Storj bridge, this induces doubt as they might not know what exactly Storj is and why they are getting the email, this again induces confusion which turns people off.
Risk, the Storj bridge confirmation email might end up in spam, they might delete it because its not from us. All of this would prevent them from confirming their Storj account.
Ease of use, having to confirm their account twice (one time from us and once from the bridge) is just not user friendly at all.
As a alternative method that was suggested is using a API call: https://web.archive.org/web/20170801003621if_/https://storj.github.io/bridge/#!/users/get_activations_token to activate the account for the user. I am not sure but i think this will require some ECDSA keypair magic.
https://github.com/Storj/bridge/blob/master/doc/auth.md#ecdsa-signatures
The text was updated successfully, but these errors were encountered: