Show users eligible content creators to be co rewarded #2114

Closed
opened 2018-11-20 01:17:45 +01:00 by tiger5226 · 4 comments
tiger5226 commented 2018-11-20 01:17:45 +01:00 (Migrated from github.com)

This is to support the epic for co-rewarding creators from users collecting rewards. [this] will provide the capability of rewarding content creators automatically. This issue is for determining how this feature will be presented to the user. One idea was showing an icon next to channels or claims that are allowed. We want the user to get the emotional reward of helping someone else out, with the ask to share that within their community/tribe.

  • How will this be presented?
  • Will @lbryio/appsquad need addition requirements from @lbryio/api to support?
  • Can this be shared will mobile team or do they need their own issue?
This is to support the [epic](https://github.com/lbryio/lbry-desktop/issues/2113) for co-rewarding creators from users collecting rewards. [this] will provide the capability of rewarding content creators automatically. This issue is for determining how this feature will be presented to the user. One idea was showing an icon next to channels or claims that are allowed. We want the user to get the emotional reward of helping someone else out, with the ask to share that within their community/tribe. - [ ] How will this be presented? - [ ] Will @lbryio/appsquad need addition requirements from @lbryio/api to support? - [ ] Can this be shared will mobile team or do they need their own issue?
neb-b commented 2018-11-21 21:16:24 +01:00 (Migrated from github.com)

I think it could be cool if the reward info contains data about who it helped and or how much was sent to them too. We could display that in the rewards table/on the success snackbar.

If possible, include that data when calling reward/list and in the success response when claiming a reward.

This can all be shared with the mobile app since all of the rewards code lives in https://github.com/lbryio/lbryinc

I think it could be cool if the reward info contains data about who it helped and or how much was sent to them too. We could display that in the rewards table/on the success snackbar. If possible, include that data when calling `reward/list` and in the success response when claiming a reward. This can all be shared with the mobile app since all of the rewards code lives in https://github.com/lbryio/lbryinc
tiger5226 commented 2018-11-22 01:19:22 +01:00 (Migrated from github.com)

@seanyesmunt The idea is that all youtube sync partners will be eligible for the co-reward. What I mean was, how are we presenting letting the user know that if they watch a video for a reward, the content creator they choose gets the co reward. Or, are you saying the user should not know and it should just be a notice after the fact?

I can certainly put who and how much was given for the co-reward as an output of the /reward/list API.

@seanyesmunt The idea is that all youtube sync partners will be eligible for the co-reward. What I mean was, how are we presenting letting the user know that if they watch a video for a reward, the content creator they choose gets the co reward. Or, are you saying the user should not know and it should just be a notice after the fact? I can certainly put who and how much was given for the co-reward as an output of the `/reward/list` API.
neb-b commented 2018-11-23 22:06:05 +01:00 (Migrated from github.com)

I'm not sure how (if?) we would display it to users before they claim a reward. I think if we present it somewhere before a user claims a reward, it will just be a general message (possibly part of the first run process) and not dependent on internal apis.

I'm not sure how (if?) we would display it to users before they claim a reward. I think if we present it somewhere before a user claims a reward, it will just be a general message (possibly part of the first run process) and not dependent on internal apis.
tzarebczan commented 2021-10-08 22:58:43 +02:00 (Migrated from github.com)

Don't think we'll be taking this on.

Don't think we'll be taking this on.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-desktop#2114
No description provided.