I'm Ivo, a passionate, experienced, and self-motivated full-stack web developer looking for my next opportunity! I care deeply about test-driven-development, and processes that improve software quality.
Location: Seattle
Remote: Yes
Willing to relocate: No; currently in Seattle
Technologies: Ruby / Rails, SQL, JavaScript, React / Redux, MongoDB, AWS, and more. Test driven dev. Git, Linux, Windows, macOS.
Résumé/CV: https://www.ivopavlov.com/#resume
Email: pavlov.ivo [at] gmail.com
I really enjoy these puzzles, but I'm also stuck at the login page. Even poking around, and ignoring that the subdomain isn't working, I don't see anything else. Have any suggestions?
Everything you need to figure it out is on the login page.
Consider how hackernews works, there is the login page but that is not the only means to authenticating. You don't after all have to type your user/pass out for every page request.
Thanks for the tip! I'll be attacking this again tonight, I think I have an idea now that you mention auth. By the way, some subdomains are public (not sure if part of the game), like source.0x0539.com, oxidized etc.
Awesome work, thanks for the fun!
Edit: Just got past login, what an awesome puzzle. That being said, I hate that it looks like I have a run an executable from your site. Seems dangerous, so now I have to spend the time getting a VM setup.
You don't have to run the executable. You can, but the problem is absolutely doable without running it (static reversing).
As for the subdomains, you can safely ignore them. There are a number of them most are not primarily mine. I just give some friends free hosting(or point subdomains to their boxes)
And yea there are random subdomains that are not part of it. Most of the subdomains are not even mine (I give free hosting to friends). The only subdomain that was part of it was clcs.0x0539.net but thats no longer the case.
Thanks so much for all of the clarification; it's really helpful to know I don't have to execute the app in question. I'll keep going down the rabbit hole, hopefully others find this site and enjoy it.
Hello Andrew, I wanted to follow-up with a like to source code for any changes you want to introduce! I'm seriously very interested in changes you might introduce, so please do anything you would like with the source code here: https://github.com/nint22/3DTutorial :-)
Hi Andrew, I'm Jeremy - the author of the book. So yes, I immediately agree with everything you say, and would even like to ask you to clarify more on some of the technique divergence. Optimisations (such as acos vs. normalization) was done on purpose to make the math and code crystal clear to the reader. I've really been frustrated with great books that explain one equation but then implement its optimized form without any clear transition or derivation. I'm also aware that my texture system is very different than the standard approach; this was done for my own sake since I felt more comfortable with the Barycentric system, though (correct me if I'm wrong) that is rarely used in comercial applications. I'm always looking to make things better for the reader, so do tell me what other professionals think!
As for coding style - PLEASE do comment on it! I'm pretty anal about formatting and standards, and wrote this tutorial over a few months so things might of broke down over time. I'll be posting the book's code on Github tonight and allow several users to modify some code as requested by users here and on Reddit.
Hey, I'm Jeremy, the author. Yep, no excuse, my writing skills are far from great. Re-reading my text over and over again to catch mistakes is clearly still not effective enough - which is why I love reading people's feedback, so thanks! :-)
Hey, I'm Jeremy - the author of the book in question. I'm happy to say I completely agree, and proudly own two of the book in question! My book's goal was to be a simple read with little overhead in allowing readers to start writing code and see results immediately. Though C is incredibly powerful (goes without saying), many students have a very hard time understanding that C is a language, not a library, and thus has a hard time "outputting" real-time interactive graphics. HTML5 / Canvas, on the other hand, are ready to go without any sort of installation!
Regardless, in my next update I'll be making this point explicitly clear to readers :-) I am not trying to become any sort of tome in the library of great computer-graphics books.
