541 karma · joined December 11, 2009
[ my public key: https://keybase.io/nathanhammond; my proof: https://keybase.io/nathanhammond/sigs/R8aq_5n728eDFXos9Ffd28y_lV_ltZ9Wa-YxB0FxIpU ]
Our current online banking platforms are hosted third-party solutions. We're building it in-house from scratch to be an API-driven JS MVC (Ember) application for cross-platform (including web) deployment.
This is where you come in: we're looking for a few developers who want to be a part of building something right the first time. The team building this is currently just me and two other people. We'll be building everything forward of API consumption (UI dev, testing, & deployment across any imaginable platform). We'll be working with Swagger, HTML/Handlebars, CSS/Compass/SCSS, JS, Ember, PhoneGap, Chef, Selenium, Mixpanel, Optimizely, and/or whatever other tools are right for the job (little is set in stone, we're in the prototype phase of the project).
If you're interested, get in touch! nathan.hammond@ally.com
Actually, that would be a rather scary end-game for Twitter: completely losing control of their delivery platform.
# Increase File Descriptor limits.
export FILEMAX=`sysctl -n fs.file-max`
sudo mv /etc/security/limits.conf /etc/security/limits.conf.bak
sudo touch /etc/security/limits.conf
sudo chmod 666 /etc/security/limits.conf
echo "root soft nofile $FILEMAX" >> /etc/security/limits.conf
echo "root hard nofile $FILEMAX" >> /etc/security/limits.conf
echo "* soft nofile $FILEMAX" >> /etc/security/limits.conf
echo "* hard nofile $FILEMAX" >> /etc/security/limits.conf
sudo chmod 644 /etc/security/limits.conf
touch /home/ubuntu/.bash_profile
echo "ulimit -n $FILEMAX" >> /home/ubuntu/.bash_profile
# Increase Ephemeral Ports.
sudo chmod 666 /etc/sysctl.conf
echo "net.ipv4.ip_local_port_range = 1024 65535" >> /etc/sysctl.conf
sudo chmod 644 /etc/sysctl.conf git clone legislature/generalstatutes
s/marijuana/sugar/g
git commit -am "Turn sugar into a controlled substance."
git request-pull
Legislators
If interested, # git branch bill_12345
git pull nathanhammond/generalstatutes
// Continue editing the "Sugar as a controlled substance" bill.
Spin off to committee (read/write to committee members)
git clone legislature/generalstatutes
git checkout bill_12345
// Continue editing the "Sugar as a controlled substance" bill.
git commit -am "Committee updates."
Take a vote for leaving committee.
If successful, # git request-pull
General legislature takes a vote.
If successful, # git merge bill_12345 master --signoff (Legislators that voted for it.)
Benefits:- Encourages broader participation in democracy.
- Cryptographically signed. We'll know if you voted for or wrote it.
- Tracks history of all changes (at least at the commit level). If something comes out of committee very different from how it went in you can easily find every change.
- Makes it easier for newspeople to identify how the law is changing.
- An interface like GitHub over top of the repository could hide all of the complexity, allow for line-by-line comments, and general comments.
- Registering to the interface with your voter ID could allow for representatives to identify or poll constituents.
Problems:
- Requires behavioral change for legislators who I would not necessarily classify as "early adopters."
- Still possible to "launder" the creator by having somebody else make the changes for you.
- In place modification of the law. To this point when something is repealed it typically looks something like this: http://www.ncleg.net/EnactedLegislation/Statutes/HTML/BySect...
Developer response: http://www.boardgamegeek.com/article/8518401#8518401
Both of those are from the discussion about the full situation on BoardGameGeek: http://www.boardgamegeek.com/thread/766059/aborted-pandemic-...
Micro - $105.80/yr (reserved instance)
Bandwidth - $0.00/mo (light transfer usage)
S3 - $0.20/mo (combining storage and transfer)
CloudFront - $0.20/mo (combining requests and transfer)
After a quick glance around I found that it was going to be impossible to beat that price, most especially for the services gained by using AWS (CloudFront, S3, CLI interface + tools, ability to spin up an instance behind the scenes and swap over to it once properly configured...)
The moral of this story is to make sure that you price out the cost of using any platform for your particular usage profile.
Conversation in that thread implies May or June of this year (2011).
There is a lot of interesting discussion in the thread, and Brendan Eich shows up to throw up his two cents in as well.
Also, here is my blog post discussing an attack scenario: http://www.nathanhammond.com/social-engineering-issue-with-j...
The interface for changing your Steam Forums password is not currently available.
The lobby is actually a full-on chat room (a la old school blizzard.net) and the game itself is all custom code (no libraries for the canvas stuff).
A full list of everything we used is on our entry page: http://nodeknockout.com/teams/wrench-labs
(And updates are coming as soon as judging is over!)
The best use case I can come up with is using node, socket.io, and knockout to quickly build a shared-state application (so long as there is a way to reconcile communication latency, which is why a declarative library like knockout is a good thing). I'm trying to come up with a good problem to solve with that tech stack for this year's Node Knockout.
In short, I agree, Node lends itself nicely to a particular subset of problems, but a lot of the places where it is presumed to shine (speed/real-time/code reuse) others are moving in to follow its lead.
Our most amusing result was watching a t1.micro beat the pants off a cc.4xlarge.
2. I'm in the process of setting up a self-assembling system that will need to be environment aware (public, staging, dev). If I redirect everything to a single A record I actually have to perform logic on my end. A failed request will instead mean to simply move to the next in the list. (Or that is how I am scheming for it to work anyway, not being built yet I don't know how it will turn out.)
Typo-squatting is addressed by both the ACPA (http://en.wikipedia.org/wiki/Anticybersquatting_Consumer_Pro...) and the UDRP (http://en.wikipedia.org/wiki/Uniform_Domain-Name_Dispute-Res...).
And worse, you're held responsible for the content of that page.
The conclusion of my post was that one should not use name.com for DNS at all, and, if you have any ethical concerns with their aggressive monetization strategy (which I do) to not use them as a registrar, either.
The problem I have is that it wasn't immediately apparent that I was serving ads on my domain because they weren't respecting the way in which DNS is supposed to work--basically typo-squatting me.
Just as I don't give GoDaddy business any longer due to their poor corporate ethics, I can't recommend name.com as a registrar because I must take into account the way in which they run the rest of their business. I will be ceasing my relationship with name.com as soon as reasonably possible.