Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jeffasinger
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
35 ms
·
361.
▲
by
jeffasinger
14y ago
Also, most people aren't doing only one thing while they're at work.
362.
▲
by
jeffasinger
14y ago
I'd think that it would be advantageous for most of them to not keep spreadsheets.
363.
▲
by
jeffasinger
14y ago
As soon as your bitcoin node receives the signed transaction (should be seconds), approve the transaction, but listen for other spends of those same coins. After a few seconds, the cost of double spending those coins would be basically the
364.
▲
by
jeffasinger
14y ago
People want point to point mass transit. I'd love to use Mass Transit for my daily commute. But at 1 hour for taking the bus vs 10 minutes to drive, it just doesn't make sense.
365.
▲
by
jeffasinger
14y ago
This is why when people ask me how they should learn X web technology, I usually tell them to pick something they want to use, and make it. It's a ton more motivating.
366.
▲
by
jeffasinger
14y ago
Yep, there's no API really, just creating a file in a specific format, and uploading it to the bank after logging in. Balanced is definitely easier. The security conscious part of me also likes that there's human, offline intervention befor
367.
▲
by
jeffasinger
14y ago
The banking feature is called ACH Origination. We use a small local bank, Canandaigua National Bank, most banks should be able to do it. Writing the software to do it took me about a day.
368.
▲
by
jeffasinger
14y ago
Why not just batch all your payouts daily and do ACH with your bank for payouts? Costs us $17/mo and takes 5min no matter how many payouts we need per day by uploading a file to our bank.
369.
▲
by
jeffasinger
14y ago
The reason that I asked that is I feel that most applications end up needing something at that layer eventually anyways, but not knowing exactly what level of traffic results in too much load is a good reason to do this.
370.
▲
by
jeffasinger
14y ago
Why you would do this, instead of putting your node server behind a more battle tested proxy, like Varnish or HAProxy, and limiting the number of simultaneous connections.