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

Properly handle blacklisted claims. #7665

Merged
merged 2 commits into from
Aug 9, 2022

Conversation

Ruk33
Copy link
Collaborator

@Ruk33 Ruk33 commented Aug 5, 2022

Fixes

Issue Number: #7663

What is the current behavior?

Blacklisted claims are not being handled properly.

What is the new behavior?

Blacklisted claims (those with errors.censor) will now be
marked as blacklisted properly.

Other information

PR Checklist

Toggle...

What kind of change does this PR introduce?

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

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 added a line describing my change to CHANGELOG.md
  • 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

Copy link
Member

@jessopb jessopb left a comment

Choose a reason for hiding this comment

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

This looks pretty good. Couple comments.

Also, please research selectBanStateForUri in extras/lbryinc and see if it needs to be updated.

<Card
title={uri}
subtitle={__(
'In response to a complaint we received under the US Digital Millennium Copyright Act, we have blocked access to this content from our applications.'
Copy link
Member

Choose a reason for hiding this comment

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

Just need a way to differentiate between actual US DMCA and other reasons. Possibly if blocking channel name includes "DMCA"? This should not be the message for every blocking channel.
Examples of channels here
https://github.com/lbryio/hub/blob/master/docs/blocking.md#defaults

Copy link
Member

Choose a reason for hiding this comment

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

We hvae a few cases:

  1. it literally says DMCA in the channel name -> show DMCA text, but say "hub" did it - not "we" did it.
  2. the channel that blocks it has a description -> some way to show channel and description
  3. the channel that blocks it has no description. -> some way to show channel and generic text

I think this may need some way to display the channel that blocked (reposted) it, to resolve the channel that blocked it (possibly a claim preview component?) and display the description of the channel that blacked it.

@jessopb jessopb merged commit 6b1069f into master Aug 9, 2022
@jessopb jessopb deleted the 7663-support-hub-operated-dmcablocking branch August 9, 2022 15:19
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.

2 participants