FEATURE: Subscriptions - Button and Page Resolution #715

Closed
opened 2017-11-06 17:36:03 +01:00 by ghost · 3 comments
ghost commented 2017-11-06 17:36:03 +01:00 (Migrated from github.com)

Ideal Release Date: 12/11, morning EST.

The Issue

(1) User needs to Subscribe to channel ("subscribe")
(2)* User needs to see their Subscriptions ("subscribe_list")
(3) Publisher needs to see their subscriber count ("subscriber_count")
(4)** Publisher needs to see where their subscriber count arrived from ("subscriber_sourceCount")

*This is a second Homepage, structurally identical to current Homepage, populated by local "subscribe_list" content.
**This is an analytic. Enable a Publisher to see which pages generated what Subscribe clicks.

Expected behaviour IN ORDER OF PRIORITY

Subscribe Button on Video Page
Subscribe Button on Channel Page
Subscription Homepage View
Publisher-side Channel Data related to Subscribe commands

Ideal Release Date: 12/11, morning EST. ## The Issue (1) User needs to Subscribe to channel ("subscribe") (2)* User needs to see their Subscriptions ("subscribe_list") (3) Publisher needs to see their subscriber count ("subscriber_count") (4)** Publisher needs to see where their subscriber count arrived from ("subscriber_sourceCount") *This is a second Homepage, structurally identical to current Homepage, populated by local "subscribe_list" content. **This is an analytic. Enable a Publisher to see which pages generated what Subscribe clicks. ### Expected behaviour IN ORDER OF PRIORITY Subscribe Button on Video Page Subscribe Button on Channel Page Subscription Homepage View Publisher-side Channel Data related to Subscribe commands
liamcardenas commented 2017-11-13 23:12:48 +01:00 (Migrated from github.com)

We need to figure out how subscriptions will integrate with the daemon.

We need to figure out how subscriptions will integrate with the daemon.
ghost commented 2017-11-14 00:08:09 +01:00 (Migrated from github.com)

FWIW, I strongly believe Subscriptions belong at the app layer. This is not a fundamental aspect of LBRY, it is aesthetic and application-specific.

FWIW, I strongly believe Subscriptions belong at the app layer. This is not a fundamental aspect of LBRY, it is aesthetic and application-specific.
kauffj commented 2017-11-14 14:35:46 +01:00 (Migrated from github.com)

If subscriptions are only at the app/local level (which I think is reasonable), it will be tricky to count the number of subscribers.

If subscriptions are only at the app/local level (which I think is reasonable), it will be tricky to count the number of subscribers.
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#715
No description provided.