Strip @ prefix subquery #170

Merged
tiger5226 merged 1 commit from strip_prefex into master 2019-11-20 22:14:05 +01:00
tiger5226 commented 2019-09-22 07:56:58 +02:00 (Migrated from github.com)

Signed-off-by: Mark Beamer Jr markbeamerjr@gmail.com

Signed-off-by: Mark Beamer Jr <markbeamerjr@gmail.com>
tzarebczan commented 2019-10-28 15:32:01 +01:00 (Migrated from github.com)

@tiger5226 / @nikooo777 what's the status of this?

@tiger5226 / @nikooo777 what's the status of this?
nikooo777 commented 2019-10-31 21:28:37 +01:00 (Migrated from github.com)

not sure what this does, but as soon as i have the new server deployed correctly i'll test this against my benchmark

not sure what this does, but as soon as i have the new server deployed correctly i'll test this against my benchmark
tiger5226 commented 2019-11-01 03:43:52 +01:00 (Migrated from github.com)

addresses https://github.com/lbryio/lighthouse/issues/167

So many of these tweaks over the past 6 months are for specific cases identified by @tzarebczan where the basic queries did not gather the results correctly. It found many of them but they were not in the top 10 as expected for different reasons. Many of these cases are related to higher profile creators being flagged.

I think it is better to look at KPIs than to look at specific cases. I would prefer to judge changes against the benchmark than for particular results. The weights have a lot of give and take in them that are hard to gauge across all possible searches.

addresses https://github.com/lbryio/lighthouse/issues/167 So many of these tweaks over the past 6 months are for specific cases identified by @tzarebczan where the basic queries did not gather the results correctly. It found many of them but they were not in the top 10 as expected for different reasons. Many of these cases are related to higher profile creators being flagged. I think it is better to look at KPIs than to look at specific cases. I would prefer to judge changes against the benchmark than for particular results. The weights have a lot of give and take in them that are hard to gauge across all possible searches.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lighthouse.js#170
No description provided.