I think this is worth clarifying.
As I understand it, due to the slots arrangement, it wouldn't be possible to delegate RC's to accounts without them confirming this was OK for a slot to be used?
Think I need to read a few more times :)
You are viewing a single comment's thread from:
That's exactly it.
Right. Sounds like it's best to get the RC's delegated from the off then with the new account creation, likely as you say in the post with button.
Will be interesting to see how it's worded by the dapps, I don't think we want 'agree to resource credit allocation' - 'allow to power your account'? :)
As a dapp owner myself, I would probably just tell them "want more rc ? click here" and everything would be done under the hood. Even better I could just delegate a lot to each users knowing some will use more rc than others and overrall the use will be okay.
Fair enough. I'm just not sure resource allocation or RC's are what new users need to hear/read. So the terms to say, 'let us kick-start your account with the ability to post, comment, vote' etc, would make more sense.
I've recently on-boarded a technical new user, and they are still blown away by the terms we pass around like everyone should know what they mean.
I tried to look for your proposal on peakd but couldn't see it? Would like to support, cheers.
Oh I think the actual flow for an account getting created would be
create account -> delegate rc to it -> if everything goes well user never feels restricted by rc.
And yeah complexity is a big problem, Before steempress with @fredrikaa we were thinking of building an onboarding tool that basically explains everything to you step by step and then creates an account for you and help you make your first introduceyourself post.
Thanks ! You can find links to vote here: https://hivedao.com/proposal/97 and on peakd I can't give you a direct link, but I am near the 12m mark