lbryio / lbryio/lbry-sdk

Feature requests for improved transparency for seeders

Open
#3,391 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
7.2k
Forks
493
PR merge metrics
No merged PRs in 30d

Description

I am most interested in lbry as a peer to peer content distribution system, similar to BitTorrent, but with an index of all available content. As such, I miss the level of transparency about how one participates to the P2P network that can be found in all BitTorrent client. I would like to be able to easily know what file I am seeding, how much of it I have already seeded, and how much bandwidth is currently being used in the process of seeding each file. These information could be made available through the SDK's API.

It would also improve the transparency if, similarly to BitTorrent clients, file being seeded were stored "as is" instead of as a list of nameless blobs somewhere in a user's directory, so that without even having to go through the SDK the user can see what file is downloaded and could delete that file if they don't want it seeded anymore.

Other features that could be added, that are not usually part of BitTorrent client, is the ability to see and choose what the policy is for deciding what content is seeded, and what content is not.

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 separating the requested SDK API visibility, user-visible file storage, and seeding-policy controls into independently scoped features. The issue does not name files, tests, or entry points; completion would require agreed requirements and project-specific implementation locations for each part.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.