718 karma · joined February 6, 2008
But this has a different primary use-case, more on transient context sharing, and caring about accuracy in the short term. And not about publishing per se.
Is this because you would rather verify things are what I say they are (no content stored elsewhere) and use this service, or to run your own, or just learn?
Right now, code quality isn't in a state to open-source, but I'm thinking about it.
Ended up being really useful whenever I wanted others to see what I had experienced on personalized websites (e.g. ranked feeds that would look different on different accounts, or change if reloaded e.g. https://ctxt.io/2/AAAAiPRWFg), interview feedback, or even paywalled content if I just wanted to share a little snippet for fair-use and keep the HTML styles, https://ctxt.io/2/AAAAACI6FQ. Scroll to the bottom of the page for these examples.
The main technical difficulty here was in trying to get all the CSS styles to be as accurate as possible, and the browser extension solves many of these, including proxying requests whenever necessary to bypass some restrictions. The browser extension doesn't request any permissions, and won't inject any content scripts on your page, so as someone who cares about security, is what I wouldn't mind installing personally.
One cool thing I've discovered after building it is that it's super useful for web developers to modify the DOM of pages and redo mockups and then use Context to re-share them with others for them to also modify: e.g. https://ctxt.io/2/AAAA0KGcFA
Everything is free for now (don't worry about the $ signs), mainly interested in feedback. Thanks in advance!
Feel free to ask us questions anytime at codesprint@quora.com
Questions will also be posted at http://quora.com/CodesprintQuora so you don't have to sign up for an account to read them.
This sprint is designed to seriously test your programming prowess on a wide range of tasks ranging from algorithms and product design to machine learning and data analysis. This comes from our intention to hire only the very best engineers, product engineers and data analysts. Come and participate, and learn about any or all the challenges we face in developing these systems: - Quora Feed Optimizer - Quora Trend Analyzer - Quora Typeahead Search - Quora Browser Extensions - Quora Nearby Redux - Quora Answer Classifier Redux and more!
That statement can't quite get any harsher I would think :)
It's true that we don't have that many requirements at that low-level right now, but we certainly do have some work done lower than the web-stack -- we even got an ex-Ksplice engineer joining us to help with that.
But maybe I could also have included some of the deficiencies too, to make it a little more balanced--I agree with you it does seem too rosy with what I had mentioned, but overall the experience has been really positive. I've tried to keep things as real as possible, no-holds barred, instead of being filled with corporate imagery. So you can see the messy desks, cardboard boxes, boring food, lack of 6-core Xeons with 12GB RAMs :)
Thanks for the compliment!
You can actually seem when a question was asked on Quora, if you click on the last activity timestamp on the question. It's just not that easily accessible because we want to emphasize the fact that each Quora question page is something that will last over time and not be transient. The page should mean the same when the question was first asked and when others visit any amount of time later.