Confirm
964
edits
Changes
→Engineering
https://wiki.mozilla.org/Firefox/Activity_Stream/Mobile_Sprint_Planning
== Cross Team Projects ==
==== Page MetaData Parsing ====
Problem: embedly proxy server has limitations in performance, client-side intelligence in display heuristics, and has a high cost.
Questions and Goals:
* How do we land and prioritize the work to use Local page meta data parsing?
* What dependencies and risks are there?
** Performance could hang the main thread for ~100ms per page till we get Loci/worker queue
** Quality of the parsing results and image identification could be lower than embedly
** Advanced storage of page indices is needed to improve scoring, de-duplication, and intelligence of displayed content.
==== Rank/Scoring heuristics for content relevance ====
Problem: current query of places.db has limitations in flexibility and inclusion of other signals.
Solution: How can we build system that could help us learn programmatically what types of content is more engaging for users measured by click-through-rate (CTR)?
Questions and Goals:
* How do we land a scoring system
* How can we maintain low latency of computation?
==== Signals ====
Problem: the heuristics for ranking page value, frecency or scoring, could improve by adding more signals from user activity
Solution: Let's experiment with a basic set of new signals that are already available (e.g. share events, etc...) and add them to a scoring system to test how we can improve relevance to users measured by CTR.
==== Performance ====
Problem: If we parse pages locally, we need to preserve performance which could be impacted if we parse many pages.
Solution: Loci, a worker queue that could parse pages without blocking the main thread. Advanced storage to store page meta data for fast queries by score.
=Team - RACI =
