Where do you send the notifications from irssi?
I run irssi in tmux on EC2 with a Colloquy push script (http://static.ssji.net/colloquy_push.pl.txt). Spent time trying to get it right, but Colloquy is flaky at best.
960 karma · joined October 9, 2009
I run irssi in tmux on EC2 with a Colloquy push script (http://static.ssji.net/colloquy_push.pl.txt). Spent time trying to get it right, but Colloquy is flaky at best.
------------------
Hey Jon,
Thanks for the comments.
We do our best to listen to our customers. The primary reason that we haven't built Bitcoin support is that we haven't seen requests for Bitcoin as a payout method.
We use GitHub to track feature requests, so I created a GitHub issue (https://github.com/balanced/balanced-api/issues/204) for Bitcoin. I'd love to get feedback.
I also submitted the GitHub issue to HN (http://news.ycombinator.com/item?id=4833049) to drive more attention and increase feedback.
Matin Co-founder/CEO, Balanced
https://github.com/balanced/balanced-api/issues
We use GitHub to track feature requests like international support: https://github.com/balanced/balanced-api/issues/23
There's three main things marketplaces have expressed that they like about Balanced: 1. Compliance. This includes PCI and the ability to underwrite merchants through the API 2. Payouts. Depositing money in a merchant's bank account the next business day and having full control over when you issue the deposit. With this launch, we made it easier for marketplaces to use us just for payouts—something we saw existing customers doing 3. Taxes. We handle the tax reporting for the merchants
There's no one else that provides any of the three above.
In the end, I think we (Balanced) should have done a better job here, and we'll work hard to do so in the future.
There are compliance ramifications of permitting money laundering, but collusion isn't always money laundering. Here's a few different scenarios:
1. Legitimate money laundering where someone is trying to obfuscate the origin of the money for some illicit reason. The ramifications of permitting or not having strong enough systems to prevent money laundering results in being shutdown. That's a bigger incentive than financial loss
2. Fraud where someone is trying to get cash off of someone else's card. This is the number one form of fraud on a marketplace and, by far, the hardest to catch. This is where the incentive is financial due to chargebacks
3. Cash advance where a marketplace has set their fees low (sometimes even lower than the fees Balanced charges) and someone is incentivized to get money off their card or simply get miles/points. Venmo and a lot of similar services experienced would get targeted by this form of collusion when they didn't charge any fees. This should be prevented due to card network (Amex, Visa, MC, Discover) policies, but they generally won't result in a chargeback
You want to comment on the API docs using the API itself? The goal is to let you fork the specs and issue a pull request on GitHub.
> Tooo many times I googled for an answer that the API docs neglect and found the answer instead on StackOverflow.
Are you referring to the API docs for Balanced or API docs in general?
Give it a shot with some test creds (see below). You can go live directly from the site: https://balancedpayments.com
# create a test marketplace
curl -X POST https://api.balancedpayments.com/v1/api_keys
# retrieve and store the secret for subsequent commands
curl -X POST https://api.balancedpayments.com/v1/marketplaces -u $SECRET:
new business comes in through referrals and press by our marketplaces, so we haven't focused on press.
if you want to sign up as a marketplace: https://www.poundpay.com/developers/application
pg says it much better: "Investors all compete with one another for deals, but they aren't one another's main competitor. Our main competitor is employers. And so far that competitor is crushing us. Only a tiny fraction of people who could start a startup do. Nearly all customers choose the competing product, a job." [http://www.paulgraham.com/future.html]
Here's to hoping more college grads join an early stage start-up or start their own company instead of joining Google or Facebook
DDoS attacks make the most sense for the attacker when they are an extortion attempt. The economics works in favor of the attacker. It costs the site dearly to be down, and they set a price that makes sense based on your site. Unfortunately, you may not hear about a lot of these attacks, and the attacker is never found or can't be arrested.
unixy.net sells DDoS insurance. You never know if the insurance policy was worth the monthly payments until an attack happens.
Note: I've never used unixy.net and can't speak to their effectiveness, but I don't like how they grossly oversimplify a complex problem
Here's a bit.ly link :-( http://bit.ly/9iQWn8
HN must have stripped out the ' from the link when I submitted it