Exclude blocked content from search results #12

New issue

Closed

opened 2017-09-14 21:40:49 +02:00 by lyoshenka · 6 comments

lyoshenka commented

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

(Migrated from github.com)

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

filipnyquist commented

2017-09-18 11:27:42 +02:00

(Migrated from github.com)

@lyoshenka , what is the output of endpoints?

lyoshenka commented

2017-09-18 15:20:56 +02:00

(Migrated from github.com)

Its a list of outpoints. An outpoint uniquely identifies a file. Its a combination of txid and nout of the publish for the file. It has the form txid:nout. For example, the outpoint for the current winning claim on one is 8e5d6945d238e8508520364d5eae7885b0db15d77d6d5cffee3f860dc13f0b45:0

Its a list of `outpoint`s. An outpoint uniquely identifies a file. Its a combination of txid and nout of the publish for the file. It has the form `txid:nout`. For example, the outpoint for the current winning claim on `one` is `8e5d6945d238e8508520364d5eae7885b0db15d77d6d5cffee3f860dc13f0b45:0`

kauffj commented

2017-09-18 18:13:45 +02:00

(Migrated from github.com)

If possible, I would like lighthouse to return the quantity of blocked URLs (and possibly the list itself).

tzarebczan commented

2018-04-06 17:22:48 +02:00

(Migrated from github.com)

@filipnyquist / @tiger5226 this has become a high priority item as, do either of you have the bandwidth to work on it?

tiger5226 commented

2018-04-08 06:18:34 +02:00

(Migrated from github.com)

I won't post the test cases but you should be able to just search the claim name and see that it no longer shows up in the results.

PR #59 adds this functionality to the sync process. To avoid quadratic logic while syncing, I just at the very end attempt to delete the blocked claims from elastic search which is async and should be very fast. I won't post the test cases but you should be able to just search the claim name and see that it no longer shows up in the results.

filipnyquist commented

2018-04-08 09:26:52 +02:00

(Migrated from github.com)

Yup, this is tested and now live on production! Closing this issue!