Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supports metadata #32

Open
tzarebczan opened this issue Apr 15, 2019 · 3 comments
Open

Supports metadata #32

tzarebczan opened this issue Apr 15, 2019 · 3 comments
Labels
needs: exploration Solution unclear, needs research type: new feature New functionality that does not exist yet

Comments

@tzarebczan
Copy link

tzarebczan commented Apr 15, 2019

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(lbryio/lbry-sdk#2028)
Commenting (with/without tips)
Ratings
Community tagging
Blockchain based subscriptions

@tzarebczan tzarebczan added type: new feature New functionality that does not exist yet needs: exploration Solution unclear, needs research labels Apr 15, 2019
@osilkin98
Copy link

osilkin98 commented Apr 26, 2019

I'm going to add these to the prototype database so we can also have it as an experimental feature to play around with elsewhere in the stack.

Since we'll have to do more integration on the UI side it would be nice to see how it could work before it's ready to be on the blockchain.

@tzarebczan
Copy link
Author

I would not worry about that for now. The whole point of the comments prototype is to get something out before we know exactly what's on the blockchain side. It will fill the gaps for us.

@tzarebczan
Copy link
Author

I started writing up something for this and then lost it, so I'll be a bit briefer here. I know we'll start adding metadata and signing to supports soon, and I also think we should consider generating some type of authentication keys that users can exchange in this manner also . One example would be the creator-owned relationships - where a subscription (special support) on the blockchain allows receiver to view certain parts of the channel metadata (would need to be spec'd out) and share a content key to unlock future premium publishes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs: exploration Solution unclear, needs research type: new feature New functionality that does not exist yet
Projects
None yet
Development

No branches or pull requests

2 participants