You are viewing a single comment's thread from:
RE: Login To Busy Demands Extensive Access For "@busy.app" - This Needs Clarification
SteemConnect is the trusted way to connect apps to Steem via Steemit.com access. It means the guys at Busy.org never need to have access to your key directly, like the way OpenID works. It looks they've updated to show you exactly what the posting key can do so there has been no effective change, only a UI change.
That's what logging in is so if you don't want to log in you can just not log in and continue using Busy.org without being logged in.
But I agree that there should be an option to choose between permissions. That is for SteemConnect to implement however, not Busy.org
I love busy.org and SteemConnect, my hyper paranoia will never allow me to click that continue button though. Ironically, I have always known this was the access I was granting when using the SteemConnect, but the raw brutal transparency just hit a little too hard.
Let it hit hard and look into the jaws of reality!
That is a great explanation for this whole thing. Maybe they should add that sentence to the login process. Perhaps plus something, like "this is necessary so that Busy.org has access to the Steem blockchain for your account"... or something like that.
How do I post articles and comments on Busy without being logged in?
You can't! But you can use Busy.org for viewing without logging in, that's the only point I make. Otherwise you have to accept it.
I should also say that using your posting key is more secure than you're master key (called the active key), so really at every level they seem to be following best practice here. If your posting key is compromised you can always regenerate it with your master key.
I believe you that, but I strongly doubt that inexperienced or new users are aware of that. The login process simply demands too much pre-existing knowledge about the system and without it, the whole login process looks like a scam.
I can see how you or anyone could come to that conclusion, I don't debate that it should be clearer, I'm just trying to make it clear to you, here 🙂 The ticket has been accepted so looks like they will do something about it.
Yes of course, thanks for the clarification. You actually did help me with that.