lbryio / lbryio/lbry-desktop

Allow delete of LBRY/local content on DMCA page

Open
#1,763 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: ux help wanted level: 1 type: improvement
Dominant language
JavaScript
Stars
3.5k
Forks
409
PR merge metrics
No merged PRs in 30d

Description

## The Issue
Similar to https://github.com/lbryio/lbry-desktop/issues/1719 but for downloaders. We should have the delete option available to users who have downloaded DMCA/copyright content and wish to delete it from LBRY/local drive.

The page should show the local path and a delete button if the file exists in file_list.

### Suggested Solutions
Tell us your suggested solutions if you have any.

## System Configuration

- LBRY Daemon version:
- LBRY App version:
- LBRY Installation ID:
- Operating system:

## Anything Else

## Screenshots

### Acceptance Criteria
1.
2.
3.

### Definition of Done
- [ ] Tested against acceptance criteria
- [ ] Tested against the assumptions of the user story
- [ ] The project builds without errors
- [ ] Unit tests are written and passing
- [ ] Tests on devices/browsers listed in the issue have passed
- [ ] QA performed & issues resolved
- [ ] Refactoring completed
- [ ] Any configuration or build changes documented
- [ ] Documentation updated
- [ ] Peer Code Review performed

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 at the DMCA page and compare its intended behavior with issue 1719, then trace how downloaded entries are represented in file_list. Confirm how the local path is exposed and how existing project tests cover file actions. Done means existing local content shows its path and a delete option, while the project still builds and tests pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, javascript, react
Domain
desktop, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.