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

Support for re-posting content to channel #2028

Closed
10 tasks
tzarebczan opened this issue Apr 15, 2019 · 3 comments
Closed
10 tasks

Support for re-posting content to channel #2028

tzarebczan opened this issue Apr 15, 2019 · 3 comments
Labels
consider soon Discuss this issue at the next planning meeting, then remove this label Tom's Wishlist type: new feature New functionality that does not exist yet

Comments

@tzarebczan
Copy link
Contributor

The Issue

Implement an API where users can re-post a claim to their own channel. Optimally, this would be done via support metadata (to own address). This will require new types/protobufs to be created (lbryio/types#32). Using supports alleviates the need to create a new claim (and claim namespace) to be created.

Considerations:
Reposts would return with channel claims, have a special identifier.
Does it make sense to re-post anonymously?
What fields do we allow to be set with a repost?

System Configuration

  • LBRY Daemon version:
  • LBRY App version:
  • LBRY Installation ID:
  • Operating system:

Anything Else

Screenshots

Internal Use

Acceptance Criteria

Definition of Done

  • Tested against acceptance criteria
  • Tested against the assumptions of user story
  • The project builds without errors
  • Unit tests are written and passing
  • Tests on devices/browsers listed in the issue have passed
  • QA performed & issues resolved
  • Refactoring completed
  • Any configuration or build changes documented
  • Documentation updated
  • Peer Code Review performed
@tzarebczan tzarebczan added type: new feature New functionality that does not exist yet blockchain-dependent labels Apr 15, 2019
@kauffj kauffj added the consider soon Discuss this issue at the next planning meeting, then remove this label label Jun 7, 2019
@kauffj
Copy link
Member

kauffj commented Jun 7, 2019

I think this issue should be strongly considered as a next feature addition. It would simultaneously be a useful feature AND advance censorship resistance, as we can use the re-posting feature to allow wallet servers to know about which content is reported as a DMCA (or other) violation in a decentralized way.

@lyoshenka
Copy link
Member

#2110 is taking the first step toward making reposting happen

@tzarebczan
Copy link
Contributor Author

Closing this since the basic API is complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
consider soon Discuss this issue at the next planning meeting, then remove this label Tom's Wishlist type: new feature New functionality that does not exist yet
Projects
None yet
Development

No branches or pull requests

3 participants