Here's a few user stories for you to ponder and consider the features needed to make these possible.
Crypto Influencer Girl X
X makes informative crypto deep dive videos where she goes over crypto projects in great detail. She keeps her content updated and organizes her videos in "Collections/Playlists" on PeakD so that users can easily find the content associated with their favorite coin.
While X does decently on her reward pool rewards, the vast majority of her earnings on PeakD come from tips. She actively asks for tips at the beginning and end of each video and depending on the level of tip, the user can receive different perks.
Tips equal to or less than 10 Hive, receive an automated, "Thanks for the tip!" response.
Tips greater than 50 Hive will receive personalized DM reply.
Tips greater than 250 Hive will receive a shoutout at the end of her next video.
The Online Art Instructor Y
Y teaches art online through video lectures. He posts these lectures to PeakD and organizes them in "Collections/Playlists" based on subject matter, difficulty level, and a host of other variables. While all of this content is free, Y accepts tips for offering feedback to anyone who watches one of his online lectures, and completes the assignment assigned at the end of every lecture.
For a 10 Hive tip, Y will leave a detailed comment providing feedback on your work
For a 100 Hive tip, Y will make a quick video recording where he will critique a students work.
Y has his own whitelisted community where students can post the work they've completed for his courses. Within the community he has "Collections/Playlists" of previous students work as a showcase of what people have learned by following his educational material.
Hopefully these paint a picture of the sort of experience I've envisioned as I've chatted with you all about some of the features I'd love to see.
Very helpful. These are the stories that put a vision behind some potential ideas. Would be awesome to see some people attempting stuff like this (even if they were doing it more manually) and then we could automate the process. It's challenging to put time into something no one is doing yet just hoping that those who have this skillset or influence eventually come and use.
So to be honest, I think that at the current infrastructure support level and scale of Hive, TODAY neither of these examples would be successful. Too much friction still in buying Hive, plus a bunch of other choke points. My goal is to hopefully help to illustrate some of the many ways PeakD could fulfill on one of your defined pillars as being a partner in the success of your users. The strategy of which features implemented at what time in what order is a different problem and I'm sure you all know best what the best approach is for that in the context of everything you're working on.
That said, I do not think anyone will even attempt to do anything like this until the rails are already built and greased for them. I think whatever you macro vision is for PeakD, you will have to solidify that and go for it, then make changes and adaptations upon feedback and metrics of what's working and what's not. Just my 2 cents.