Prior to this change, we setup our feed variant query to have a cached randomization seed. For a given user this seed is cached for 15 minutes. The goal of this is to provide mostly consistent sort orders on the feed articles during that 15 minute window. With this change, we allow for a feed variant to say ignore the cached seed and generate a new one for this call. I have also added explicit settings to each of the feed variants to reflect our desired intentions for those features. Relates to - forem/forem#17833 - forem/forem#17826 Closes forem/forem#17940
36 lines
780 B
JSON
36 lines
780 B
JSON
{
|
|
"max_days_since_published": 15,
|
|
"reseed_randomizer_on_each_request": false,
|
|
"order_by": "relevancy_score_and_publication_date",
|
|
"levers": {
|
|
"featured_article": { "cases": [[1, 1]], "fallback": 0.85 },
|
|
"privileged_user_reaction": {
|
|
"cases": [
|
|
[-1, 0.2],
|
|
[1, 1]
|
|
],
|
|
"fallback": 0.95,
|
|
"negative_reaction_threshold": -10,
|
|
"positive_reaction_threshold": 10
|
|
},
|
|
"matching_negative_tags_intersection_count": {
|
|
"cases": [
|
|
[0, 1],
|
|
[1, 0.5],
|
|
[2, 0.4],
|
|
[3, 0.3],
|
|
[4, 0.2]
|
|
],
|
|
"fallback": 0
|
|
},
|
|
"public_reactions": {
|
|
"cases": [
|
|
[0, 0.9988],
|
|
[1, 0.9988],
|
|
[2, 0.9988],
|
|
[3, 0.9988]
|
|
],
|
|
"fallback": 1
|
|
}
|
|
}
|
|
}
|