Open
Bug 1561745
Opened 5 years ago
Updated 2 years ago
Fix value for missing published_timestamp in recommendations
Categories
(Firefox :: New Tab Page, defect, P2)
Firefox
New Tab Page
Tracking
()
NEW
People
(Reporter: mmiermans, Unassigned)
References
Details
The endpoint that delivers recommendations to discovery stream has published_timestamp = -62169962400 when we don't have a publish date. Discuss with Fx client devs what the right approach is: missing key or a null value.
We currently only use the published_timestamp to determine 'trending' stories, and in practice stories are almost always trending, so fixing this bug would not have any user-facing impact.
Reporter | ||
Updated•5 years ago
|
Type: task → defect
Assignee | ||
Updated•5 years ago
|
Component: Activity Streams: Newtab → New Tab Page
Updated•5 years ago
|
Priority: P3 → P1
Updated•5 years ago
|
Assignee: mathijs → nobody
Iteration: 70.3 - Aug 5 - 18 → ---
Priority: P1 → P2
Updated•5 years ago
|
No longer blocks: pocket-newtab
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•