Supports metadata #32

New issue

Open

opened 2019-04-15 17:49:02 +02:00 by tzarebczan · 3 comments

tzarebczan commented

2019-04-15 17:49:02 +02:00

(Migrated from github.com)

Use case ideas:
Reposting content(https://github.com/lbryio/lbry/issues/2028)
Commenting (with/without tips)
Ratings
Community tagging
Blockchain based subscriptions

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

osilkin98 commented

2019-04-26 13:15:07 +02:00

(Migrated from github.com)

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.

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 commented

2019-04-26 14:56:39 +02:00

(Migrated from github.com)

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 commented

2020-02-04 23:23:35 +01:00

(Migrated from github.com)

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.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/types#32

No description provided.