Supports metadata
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
The blockchain will be adding the ability to assign a value to supports. This will allow us store metadata along with supports, including channel signing. The type should be flexible to support multiple use cases.
Use case ideas:
Reposting content(https://github.com/lbryio/lbry/issues/2028)
Commenting (with/without tips)
Ratings
Community tagging
Blockchain based subscriptions
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
No file or test is named. Start by reviewing the repository's cross-language type definitions and how supports are currently represented, then compare the proposed metadata value with the reposting, commenting, ratings, tagging, and subscription use cases. Done when a flexible representation is agreed and its compatibility across supported languages is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, javascript
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100