| /* | |
| * Omegle Command Prompt Chat Client | |
| * ================================= | |
| * Version 1.0 by adammw111 | |
| * Requires Node.JS | |
| */ | |
| var net = require('net'); | |
| var OMEGLE_HOST = 'cardassia.omegle.com'; | |
| var OMEGLE_PORT = 1365; |
At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)
Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.
| // Hash map class template | |
| template <typename K, typename V, typename F = KeyHash<K>> | |
| class HashMap { | |
| public: | |
| HashMap() { | |
| // construct zero initialized hash table of size | |
| table = new HashNode<K, V> *[TABLE_SIZE](); | |
| } | |
| ~HashMap() { |
This is an example of how to use the Google Drive file picker and Google Drive API to retrieve files from Google Drive using pure JavaScript. At the time of writing (14th July 2013), Google have good examples for using these two APIs separately, but no documentation on using them together.
Note that this is just sample code, designed to be concise to demonstrate the API. In a production environment, you should include more error handling.
See a demo at http://stuff.dan.cx/js/filepicker/google/
People
 :bowtie: |
😄 :smile: |
😆 :laughing: |
|---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
https://devcenter.heroku.com/articles/custom-domains http://thenomadicfreelancer.blogspot.com/2012/08/pointing-godaddy-domain-to-your-heroku.html
For each custom subdomain use domains:add in the Terminal.
| (function(window, document, version, callback) { | |
| var j, d; | |
| var loaded = false; | |
| if (!(j = window.jQuery) || version > j.fn.jquery || callback(j, loaded)) { | |
| var script = document.createElement("script"); | |
| script.type = "text/javascript"; | |
| script.src = "/media/jquery.js"; | |
| script.onload = script.onreadystatechange = function() { | |
| if (!loaded && (!(d = this.readyState) || d == "loaded" || d == "complete")) { | |
| callback((j = window.jQuery).noConflict(1), loaded = true); |
I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!
\
Note: There is a lot of information here, but if I have provided a link, it is probably something you should click on and read. OAuth is a complex enough subject on it's own, and hacking these two services together only adds to it.
Even so, I have found Firebase's API to be simpler than almost any other OAuth solution I have explored. When all is said and done, the important bits of code related to authentication is actually less than 10 lines. If you have ever tried to implement your own OAuth flow before, you know how amazing that is.
In the end, it may be worth using Firebase for authentication, even if that's the ONLY thing you use it for.
