104 karma · joined May 12, 2011
The New York Times recommender system uses a hybrid approach (Content Based + Collaborative Filtering) called Collaborative Topic Modeling on top of LDA[4]. It would be interesting to try that.
[1]: https://github-recs.appspot.com/
[2]: https://medium.com/towards-data-science/recommending-github-...
[3]: https://github.com/jbochi/facts
[4]: https://open.blogs.nytimes.com/2015/08/11/building-the-next-...
Our library was just open sourced (and still in my personal account, until we add more documentation): https://github.com/jbochi/facts
Inspired by Evan's post, I wrote "How Not to Sort by Popularity" a few weeks ago: https://medium.com/@jbochi/how-not-to-sort-by-popularity-927...
1: We just repackage it. 2: The problem is that EvoStream stores the manifests and chunks locally and we needed high availability. That's why we use an external data storage. We have had up to 30 simultaneous streams, with 7 bitrates each and 2 hours of DVR.
I'll try both if I find the time :)
PS: Some of the configurations are not stable with my code. I'll try Runge-Kutta.