If you only spent 4 hours trying to acquire a completely new currency that is not backed by any major authority yet still usable all over the internet, you might want to spend some more time :) And yes, getting a hold of them is still a challenge. If you want to buy in bulk, you can wire money to many of the exchanges for standard wire rates.
You should look into bitcoin (at least know about it and how it can help you as a merchant). Any payment company that deals with credit cards is not just a payment company but a fraud detection service; at least that is what it should be selling themselves as. Fighting CC fraud (and bank transfer fraud) is a challenge as the system was not designed for the digital space.
That is the point. You don't need to be making two versions. This has nothing to do with npm even. Just write your code using the commonjs require syntax. When you want client side scripts use one of the many different bundlers which can resolve the requires and turn it into whatever loader style you want (flat time, AMD, custom, etc). This provides much more flexibility and keeps the code free of boilerplate which serves no purpose.
You are looking at the problem wrong. Instead of putting these hacks into your code you should use some sort of bundler (component/browserify/script/etc..) to prepare your code for the client. That way you leave it up to the user to determine how they want to package the stuff versus making assumptions about it.
It seems to me that the on state of the button should have the outline around the blue area (of the default button) also be blue instead of gray. Keeping the border gray when the slider goes to "on" gives the button the wrong appearance. The blue area doesn't look like it has been uncovered but instead looks like a tab sticking out of the side.
I am not sure it is correct to call a private undocumented API an "API". Just because you can access it over http or whatnot doesn't mean that it is an API for you to use.
The same would hold true for any website I make that has an internal API it uses to serve up pages. Sure, you can make a service that mimics the correct calls and gets the data, but don't be surprised when I change my routes around and your stuff stops working.
I was going by the actual definition of a bank. Things like swipe facilitate transactions but are not banks. Facilitating a transaction does not make it a bank.
There are already thin client wallets. These connect to "blockchain servers" and grab the relevant transactions for your accounts from those. You still maintain control of your address(es) and thus your funds. No need to download the whole blockchain. That is really only needed for those that _want_ to or those that run services. The point is that you _can_ be a full participant in the network if you want.
I don't think regulation helped any of the banks with high profile credit card hacks recently. Don't confuse regulation with security. Regulation is not necessarily in place to provide security for the end user, only barriers to entry. Once you do start to grow obviously the correct precautions should be taken.
Stop worrying about the financial and regulatory know how and just try out your idea. You might find it goes nowhere and you will have wasted your time thinking about "regulations". No one is going to shut down your website making 10$ a month and if you do start to grow then you will be able to pay the right people to deal with the right problems.
I have started to think about it. You just have to consider things like what happens when the lenders want their coins back and users have valid short orders out. Think about the incentive here. The lender is giving his coins to people who he knows are betting the price will drop. This means that when the price does start to drop the lender could want to sell the coins to prevent further loss. However, the other user (the one who got the lent coins) may not be ready to return then.
There was a service that allowed shorting (Bitcoinica). But all that seemed to come to a very abrupt and painful end. While it was running it did serve a valuable purpose.
It isn't just an idealogical itch against central banks. Controlling someone's money is a very powerful way to control them. Bitcoin is about empowering digital transactions without a controlling third party in the middle. Having ways to move money to anyone anywhere instantly is not something to shrug away lightly. Sure, maybe you have no use for them, but I can assure you that there are plenty of people, businesses, and entire sectors that benefit from their properties.
Barring outside factors (hacking, breach of trust, etc) the price of bitcoin is naturally bullish given the current ways to trade them. Since there is no large scale operation providing a way to short bitcoins, there is no one "investing" in their price decline. This simply means that anyone buying in using USD now needs to cash out at a higher price to make a profit (on most exchanges) and anyone who has coins would not want to make the market tank since that just devalues what they have.
I realize the above is a simplification and there are many other factors (and there could be malicious participants), but overall this will continue to push the price up.
I don't know anything about amazon payments, but anything that is dealing with the US banking system via ACH or the credit card system is exposed to chargebacks.
If you are a merchant, please read this before thinking about using Dwolla (or any service for that matter). Feel free to contact me about what I wrote and my personal experiences with it.
This is not meant to be trolling; I genuinely want people to be aware of what they are getting into and understand the risks so they can avoid the problems I (and others) have already faced.
Anyone that is thinking about using Dwolla needs to read about this incident and understand what happened. Dwolla was completely unable to understand or handle the fraud. In addition, they are in total denial that the only reason anyone cares about them is because MtGox (a bitcoin exchange) uses them and brings lots of volume to their platform.
I run Bitfloor and was hit with similar fraud as Tradehill (on a much much smaller scale) and Dwolla was just as ignorant and dismissive of it. Fundamentally, they went into a business that they did not understand. I know this to be true because early on (even before any Tradehill incident) we emailed them to ask about ACH chargebacks and how they handle them. They claimed there were no chargebacks and this was everything I needed to know about their lack of understanding.
It is not a benefit if that money isn't actually there. They provide no guarantee that the funds are yours to use since they can be hit with chargebacks and will just take the money from you. This is just as bad as paypal.
It personally happened to me. I had a Dwolla merchant account for a while and then it was hit with fraud. Dwolla took all the funds out of my account and provided no real way for me to try and get them back. They WILL NOT work with you to recover your funds, they will just take them to cover their ass. They have no incentive to recover them since they just pass the fraud and costs onto you.
Honestly, as long as they are still passing the chargebacks on to merchants then none of these "procedures" matter. Because Dwolla keeps the user information secret you have to trust them to do all the resolution and such. In the meantime, you are still out of funds and have no recourse.