christianfuerst / hiveonboard Goto Github PK

• Better visualization
• Pull data from https://hivedapps.com (talking to therealwolf who is running this site)

Maybe this will show up later but the account @podnews signed up with a VIP link from my @brianoflondon account. I can see the signup on the VIP page but its not showing in the main page.

There's a typo Socail Networkingon the URL: https://hiveonboard.com/what-is-hive The file https://hiveonboard.com/images/more_than_cryptocurrency_banner.png -> https://github.com/christianfuerst/hiveonboard/blob/master/public/images/more_than_cryptocurrency_banner.png

I didn't see source assets for this image so I wanted to let you know about the typo.

The referral dashboard pulls the Profile Name instead of hive username, the correct would be utopiaeducators

• Need concensus on json metadata when creating an account.

Could be implemented this way:
Refered person uses a referer link like https://hiveonboard.com?ref=roomservice and account name could be used for metadata creating the account.

https://peakd.com/hive/@stellabelle/re-hiveonboard-qa3eg3

Currently @hiveonboard account works as fallback but IF all account tickets of the fallback account are drained as well, we got a problem :(

https://peakd.com/hive/@cardboard/re-roomservice-qa2zmt

Use fallback creator if remote instance is not available

• Improve flow after user requests sms code
• Add loading indicator after successful verification

Mobile phone number +86 1821728xxxx

FYI both

• inleo.io/signup
• join.d.buzz

return an Error authorizing user to firebase" when attempting to register

And hiveonboard.com/create-account is currently out of account creation tickets ... + there is no way to contact other than this github repo.

UI reports account creation success even if the remote creator-api instance reports failure. This also results in consumption of the ticket. Basically, hiveonboard treats an account creation failure as a success and everything proceeds accordingly. Users do not notice anything wrong until they try to use the account which does not exist.

After investigation I believe this error was caused by a logic error here:

A PR is forthcoming.

Still on my todo list.

https://hiveonboard.com/create-account is down ?

Since no delegation to new accounts are provided yet.

You should already know why a private key should be generated by the users themselves on the client-side. Transmitting a private key through the wire is risky (even with SSL). When it could be generated client-side easily with hive-js, it's being stupid.

It doesn't really have a real purpose.

In this case we made sure, the user has already secured his keys and there is lesser risk that we waste an account creation ticket.

The following errors are on the https://hiveonboard.com/create-account page after submitting SMS code: