Should show published and updated dates when content has been edited, users should have control over handling of updates. #2377

Open
opened 2019-03-23 20:23:57 +01:00 by skhameneh · 1 comment
skhameneh commented 2019-03-23 20:23:57 +01:00 (Migrated from github.com)

The application should have more awareness and communication of when claims have been changed.

  1. Users should be aware of when an update is available.
  2. Give users control of how edits are handled for content they have already downloaded.

Downloading content implies a file may be stored statically. Some users will want edits to auto-apply. Other users may want explicit control w/ manual updates.

Two scenarios:

  1. A user has downloaded content. They may treat this as a backup and not want it to change if the original claim is edited. This user will not want auto-updates and an auto-update could incur data lass.
  2. A user has downloaded content that expects frequent updates like a game. This user will likely want auto-updates. Not having auto-updates could cause a broken or less-than-desirable experience for this user.
The application should have more awareness and communication of when claims have been changed. 1. Users should be aware of when an update is available. 2. Give users control of how edits are handled for content they have already downloaded. Downloading content implies a file may be stored statically. Some users will want edits to auto-apply. Other users may want explicit control w/ manual updates. Two scenarios: 1. A user has downloaded content. They may treat this as a backup and not want it to change if the original claim is edited. This user will not want auto-updates and an auto-update could incur data lass. 2. A user has downloaded content that expects frequent updates like a game. This user will likely want auto-updates. Not having auto-updates could cause a broken or less-than-desirable experience for this user.
tzarebczan commented 2019-03-23 20:26:33 +01:00 (Migrated from github.com)

Discussed some scenarios here too https://github.com/lbryio/lbry-desktop/issues/2328... this requires the release date attribute and probably https://github.com/lbryio/lbry-desktop/issues/1203

Discussed some scenarios here too https://github.com/lbryio/lbry-desktop/issues/2328... this requires the release date attribute and probably https://github.com/lbryio/lbry-desktop/issues/1203
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#2377
No description provided.