125 karma · joined July 13, 2012
What exactly let you down so that i can continue to edit and improve this post going forward?
Kind Regards.
As i stated in another reply i am a novice writer and still looking and learning to improve, I've gone back through and fixed up those NodeJS occurrences.
Do you have any good places that i could find more about improving my writing as that would help greatly in the future!
Thanks for reading though i still hope that the core point of my article was useful and not in vein.
For me urgency in getting up to speed in actually writing a functioning application was of a higher necessity than learning about core node and as part of the learning experience it bummed me out going back to writing hello world examples not getting any 'results' made me want to give it up faster.
also a side note, usually as with most platforms, experience in the higher level results in experimentation lower levels.
I may do a more elaborate comparison of IDE's and how they've effected my workflow regarding node in the future thank you for the inspiration there :)
And yeah, looking back i am surprised that i didn't find out about npm and packages earlier on in the game. But yeah for me the learning experience was so fragmented that it was very hard to get a good grip on 'what i needed' and 'what was available' i suppose in the beginning i spent all my time trying to learn the 'core' nodejs without knowing that later i'd spend all my time in 3rd party librarys
Im not sure what modern firefox so lets see :D
Regarding the payments side of things I am using the client side stripe library. Basically what happens when you input card details and hit submit a secure async push is made to stripe's servers where the card details are stored a call back is made with a token to your browse and ONLY that token is sent to my server.
While having SSL would be nice and make the clients feel more comfortable rest assured the payments side of things is still secure
SSL WILL BE ADDED :) Probably over next weekend my next personal 'sprint'
However the past 10 hours have prooven that the m1's do have some balls :) both the site and the processing exist on the same machine and have only marginally struggled with 0 downtime from the HNEffect
Regarding the relational data that is one of the challenges I faced when building the application. I used NoSQL because I had recently had some experience with mongo and mongoose thought it would be easier then I realised I would have to begin making multiple selects and concatenating data together to bring back average ping stats for the dashboard etc which made it somewhat harder.
It may also be the server is hosted in Sydney on Amazon's ec2 so if your far from Sydney Australia that might also contribute to a page load time of about 2 - 3 seconds :) the rest is probably HN Effect
Feel free to check out lemp :)
Its a search engine, as for legality, the users who upload the videos have agreed to having the required rights to upload said content.
The site / application are not affiliated with any of these users and merely scan, index and organize content that is publically available elsewhere.