Exclude blocked content from app #565

New issue

Closed

opened 2017-09-14 21:40:20 +02:00 by lyoshenka · 8 comments

lyoshenka commented

2017-09-14 21:40:20 +02:00

(Migrated from github.com)

List of blocked outpoints is at https://api.lbry.io/file/list_blocked

liamcardenas commented

2017-11-17 17:53:30 +01:00

(Migrated from github.com)

@lyoshenka can we get some dummy data in the list?

lyoshenka commented

2017-11-17 18:52:36 +01:00

(Migrated from github.com)

You can install and run the api locally, then pass an env var to the app to tell it where to find the api (see lbryio.js line 13). Then you can make the api do whatever you want, or put whatever dummy data in the db you want. API setup instructions are in the internal apis readme.

tzarebczan commented

2018-02-07 19:22:18 +01:00

(Migrated from github.com)

Also, how would this work from a hosting perspective? Shouldn't LBRY nodes (at least ones running our official software) have to abide by this blacklist as well? What should happen on the daemon side if a file is blocked?

@lyoshenka would we need to block this separately from a search/trending perspective? Seems like trending would need to take it into account separately so it can still show the top 10 trending without blocked content. Let me know if I should open an issue. Also, how would this work from a hosting perspective? Shouldn't LBRY nodes (at least ones running our official software) have to abide by this blacklist as well? What should happen on the daemon side if a file is blocked?

finer9 commented

2018-02-08 03:30:45 +01:00

(Migrated from github.com)

As per convo with @kauffj we need to prioritize getting blocks in the app

tzarebczan commented

2018-03-28 00:29:41 +02:00

(Migrated from github.com)

@liamcardenas when you start working on this, ping @kauffj as he would like to provide input on the language used in the app when content is blocked.

kauffj commented

2018-04-06 17:23:08 +02:00

(Migrated from github.com)

Store outpoints from /file/list_blocked in redux state. This can be re-polled at a periodic interval (once an hour or once a day) rather than checked on every access.
When the user accesses the show page, check if the outpoint is on the blocklist
If it is, render a different component explaining the content is likely illegal to access (I can/will write the copy for this, just put stub copy or Lorem ipsum in). The component should link github.com/lbryio/dmca

- Store outpoints from /file/list_blocked in redux state. This can be re-polled at a periodic interval (once an hour or once a day) rather than checked on every access. - When the user accesses the show page, check if the outpoint is on the blocklist - If it is, render a different component explaining the content is likely illegal to access (I can/will write the copy for this, just put stub copy or Lorem ipsum in). The component should link github.com/lbryio/dmca

tzarebczan commented

2018-04-16 22:39:06 +02:00

(Migrated from github.com)

The goal is to release this change with the current app release (and not the redesign) this week

To be clear, if blocked content shows up on a tile on the homepage (i.e. in community section), we would still see the tile/thumbnail, but the show page (when clicking on it) would have the new blocked component. Would we want to block the thumbnail as we do for NSFW as well?

@kauffj can you work on the explanation in the meantime?

The goal is to release this change with the current app release (and not the redesign) this week To be clear, if blocked content shows up on a tile on the homepage (i.e. in community section), we would still see the tile/thumbnail, but the show page (when clicking on it) would have the new blocked component. Would we want to block the thumbnail as we do for NSFW as well? @kauffj can you work on the explanation in the meantime?

kauffj commented

2018-04-16 22:57:42 +02:00

(Migrated from github.com)

The most immediate need is to block show pages. I think we should likely make other changes, but the changes to the show page should be shipped as soon as they are releasable.