Support lbry.tv mode vs local SDK
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 21
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Many users won't want to setup a local SDK, fund it, etc. We can do all of the current SDK tasks via lbry.tv API calls + auth token (https://api.lbry.tv/api/v1/proxy)
Publish content endpoint (see https://github.com/lbryio/lbry-desktop/blob/58d323fd9782593e29e1382aa0813a86b05aab32/lbrytv/setup/publish.js)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the referenced lbrytv/setup/publish.js file and the lbry.tv proxy endpoint documentation. Compare the current SDK tasks with the available API calls and auth-token flow, then define the remaining scope for local-SDK-free operation. Done means the issue's current SDK functionality works through lbry.tv mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100