I do not really count that discussion as super productive because while we align on many things there are some key things I would like to discuss and share...so I invite you to to a recorded live conversation where we can hash out many ideas. Let me know when you can meet up.
You are viewing a single comment's thread from:
You and @asgarth are doing a really good job with PeakD. One could argue that having both peakd and ecency as high-quality frontends is a bit overkill at this point (not even counting condenser), but it might be worth it for the sake of decentralisation.
With this said, keep on doing what you're doing with PeakD. There's no all-in-one-solution or Eierlegende Wollmilchsau (as we'd say in Germany) in regards to ease-of-use, decentralisation, etc., and at this point, I can only speak from my experience, it's a great feeling knowing that I don't have to integrate every single aspect of Hive into my project because I can just refer to PeakD or Ecency, knowing that it's well built and easy to use.
Also, I don't know the legal consequences/requirements for storing private keys/passwords for your users' cryptocurrency wallets, but I wouldn't want that kind of pressure.
The approach we would like to take is to not create keys for custodial accounts just authorities we can use. I see them as the accounts for those who are Not creators or crypto holders... aka the commentors and people who just want to be social. The price of owning should be taking a moment to learn how to be responsible for true ownership.
Aka let them create an account have have simple password on peakd and use the site and then decide they truly value ownership enough to use the software and keep safe some keys.
There should be no legal requirements since the user wouldnt even own a Hive account at first. There are a few ways to do it, some Peakd already attempted.
Yeah. Lets do that.