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

Removed comment tips #1063

Merged
merged 1 commit into from
Dec 18, 2020
Merged

Removed comment tips #1063

merged 1 commit into from
Dec 18, 2020

Conversation

clay53
Copy link
Contributor

@clay53 clay53 commented Dec 13, 2020

PR Checklist

Please check all that apply to this PR using "x":

  • I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
  • I have checked that this PR does not introduce a breaking change
  • This PR introduces breaking changes and I have provided a detailed explanation below

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting)
  • Refactoring (no functional changes)
  • Documentation changes
  • Other - Please describe:

Fixes

Issue Number: #1042

What is the current behavior?

Comments requires a 1 LBC top to be paid

What is the new behavior?

Commenting does not require any tip to be paid

Other information

Not sure if warning that comment will be posted should be removed entirely or not. Will remove if asked.

@kekkyojin
Copy link
Collaborator

This PR removes or refactor a lot of methods which would need to be added again if in the future LBRY decides to require users to pay for commenting. Wouldn't it be better to just change the price in code to 0 and ensure strings are able to adapt to a free-to-comment context?

@clay53
Copy link
Contributor Author

clay53 commented Dec 14, 2020

This PR removes or refactor a lot of methods which would need to be added again if in the future LBRY decides to require users to pay for commenting. Wouldn't it be better to just change the price in code to 0 and ensure strings are able to adapt to a free-to-comment context?

If there are no thoughts about adding back paying for comments (and I'm not sure why there would be), removing the functionality entirely is more efficient. If someone from the core team wants me to do what you suggested, I'll change it.

@akinwale
Copy link
Contributor

We were planning to eventually remove tip to comment functionality completely, so this PR is pretty useful.

Copy link
Contributor

@akinwale akinwale left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this.

@lbry-bot lbry-bot assigned akinwale and unassigned akinwale Dec 18, 2020
@akinwale akinwale merged commit e6b8387 into lbryio:master Dec 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants