Hacker News Reader

david2016

I would recommend that rather than copying "arXiv-Vanity", your team should focus on improving and contributing to "Engrafo" since there are many errors in the HTML conversion. And, leave everything at "arXiv-Vanity" since there is no point of having 2 different places doing the same exact thing.

View on HN

We plan to do both. We want to give back to Engrafo where it makes sense, but we also have a unique opportunity given our other semantic features along with the paper metadata from our corpus to build upon this experience. This release is an MVP reading experience, but in the future we plan to add a number of things like: user highlighting, direct linking to authors and citations, and collaborative commenting.

+1 to what @undefined said.

If all goes well, we hope to act as a front-facing host for the Engrafo engine. That'll enable the ArXiv Vanity team to focus their efforts on improving the conversion process (which is what they'd like to focus on) while we can handle the logistics of serving this up to users (as quickly as possible).

I'm really excited about the opportunity to collaborate and support the ArXiv Vanity / Engrafo team!

Reply on news.ycombinator.com