Open Sourced: Newscombinator Front End
github.com
github.com
a live snapshot http://i.imgur.com/0KbPjcx.png
another snapshot: http://i.imgur.com/CBYRvV3.png
server load peaking @2.00 seems to be stable
another snapshot: http://i.imgur.com/LcgXdFy.png
still everything running stable.
It would also be good to be able to collapse/expand by clicking on the headline count.
I'm not sure how I feel about the continuous scroll. Often I like that, but here I am unsure, but it may be because of my particular use case: I use LinkVisitor to mark all links as visited, so that next time I know which I've already read or decided to ignore. Having a fixed number of headlines makes it easier for me to recognize that it is time to hit cmd-fn-f2. If others get a lot of value from the continuous scroll, don't worry about it, mine is likely quite the edge case.
Its kind of a funny thing here with that Ellen Pao case. I didn't see similar stories for quite a while on the very top and exactly now there is one. Shouldn't be an excuse, rather something I literally just learned about my app. And if everything is collapsed at the very beginning, it also looks kind of odd (for me at least).
Thanks for the great feedback. Considering its an angular app, it shouldn't be that hard to have a switch to choose between endless scroll / normal pagination. But its a long way to go. I'll put it on the list :).
I think a little icon that indicates the source next to the title (on the left) would be really useful to quickly scan what media ranks where and maybe only select the top stuff from your most trusted source etc.
The icon is a great idea, now the problem: What happens if a link was on 8 sites (2 x reddit, 4 x ycombinator, datatau, makernews). What would you expect next to the title?
The backend is Solr in combination with a custom scraper in java and a lamp stack. The REST interface is wrapped around a php for better auth handling - and mainly because I'm a big fan of the Zend Framework and Pimcore [1] - one of the best CMS I've come across in my life (I'm not working for them).
Although I cannot give you access to the full source of the scraper/backend (at the moment), why not get in touch and/or follow on twitter/mailinglist. I'm going to send out updates what problems I was struggling on and how I solved it from time to time.
{
"error": {
"msg": "undefined field: \"log\"",
"code": 400
}
}
Otherwise, great work! Looks very nice!It should just open a new tab with the same request as sent to the REST interface anyways in the background...
Like that one http://goo.gl/eLiUT1
So, all the information is preprocessed at index time and solr is basically a text-blob spread across multiple fields, yes.
First off: I don't choose a language because its 2014, 1999 or 1985. Or because its hip, cool or just "in". I choose a language for me, because it can help me achieve what I want to do in a reasonable amount of time. If the outcome is great, even the language is shit, its still great outcome. If the outcome is aweful, no matter how great the language is, the outcome is still not good. And I think the outcome is okay in this case and the framework is in my opinion pretty cool (considering I started JS first on IE5.5), so I cannot be blamed for being happy with a framework like this :).
And, based on my opinion, I choose angular, because I have learned it first and to love it last year. Great community and good documentation imho. I think its the wrong move to change the unterlying API with the new verison. If that really happens, then I maybe switch, learn something new, better - maybe. React is awesome, plain Javascript too imho.
Thoughts?