lbryio / lbryio/lbry-desktop

Add ability to re-download content

Open
#698 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

level: 3 priority: low type: improvement
Dominant language
JavaScript
Stars
3.5k
Forks
409
PR merge metrics
No merged PRs in 30d

Description

## The Issue
There are three main scenarios where users would want to re-download content in the LBRY app:

1) A claim was updated with a new source file - the user should be alerted to this and allow the new file to be downloaded. If the filename is the same, ask to replace or rename automatically If the content was paid for, it should not charge again (this may require https://github.com/lbryio/lbry/issues/803).

2) A download started (sd-blob downloaded) but then stalled. Currently, there's a workaround if the content is free but it takes a couple steps - you need to click "remove" which kicks you out of the claim page, so you need to navigate back. Then you can attempt to re-download. If the content was paid, this would not work since it would request a key fee again. Not sure if this is possible without https://github.com/lbryio/lbry/issues/803 right now.

3) Users already paid for content but the file is no longer available. If the blobs are available, can this be done without https://github.com/lbryio/lbry/issues/803?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the LBRY app's existing download, claim-update, and paid-content flows; no specific files or tests are named in the issue. Define acceptance criteria for replacing updated files, retrying stalled downloads, and restoring unavailable paid content without charging again, including the dependency on lbry issue 803.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, javascript, react
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.