lbryio / lbryio/lbry-sdk

Could you dev option "private" or "secret"?

Open
#3,735 1 comment 0 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

When I can not use odysee, and change to LBRY destop. Now it can not use "unlisted" option.

Could you dev option "private" or "secret"? In some case, video needs to save, but not ready to publish. I could consider to check copyright or something more in sensitivity. This helps me use it more convenient... like just change its option simply.

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

The issue body is the only starting point provided and names no files, tests, or entry points. First trace how the SDK represents publication visibility and how the desktop client sends that option, then clarify the intended semantics of “private,” “secret,” and “unlisted.” Done should include an agreed visibility behavior and coverage for the selected option.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.