Hacker Newsnew | past | comments | ask | show | jobs | submit | Aleran's commentslogin

$70 was the camera owner's revenue after Kitsplit had taken their cut. The rental fee was higher than $70.


The nice thing about Kochiku is that it is a free open source project whereas CircleCI is a paid hosted solution. If you have hardware available to use as workers on then Kochiku is free to use. There is a real cost to the time required to setup and maintain Kochiku but, at scale, within a larger company, this route can make sense.

I am sure CircleCI takes security very seriously but it also nice (and a requirement for certain companies) that with a self hosted CI server, that your source code does not leave the company.


I looked at Buffet but I was turned away by the lack of documentation for it. There is a short readme but that's it.


This is revolutionary because it is the first time that merchants have been ever been given the option to pay a flat fee per month in lieu of paying a percentage fee on each transaction. While that may not seem like a big deal you, merchants really love the simplicity of it.

A business that processes 60K a year is below the size that is targeted by this pricing structure. They are better off continuing to pay 2.75% per transaction.


It's a differently packaged variable rate fee IMO.


Actually the merchant is only liable for the loss if they did not follow all of the rules and regulations for processing the credit card.

From wikipedia (http://en.wikipedia.org/wiki/Credit_card_fraud#Merchants): "The liability for the fraud is determined by the details of the transaction. If the merchant retrieved all the necessary pieces of information and followed all of the rules and regulations the financial institution would bear the liability for the fraud. If the merchant did not get all of the necessary information they would be required to return the funds to the financial institution. This is all determined through the credit card processory."

From what I have seen, it is very common for the merchant to be liable for losses on a card not present transaction (e.g. online retail) but the credit card company stomaches the losses for a card present transaction.

I suspect that online merchants could reduce their liability by implementing things like Verified by Visa but choose not to because it causes them to lose too many legitimate sales.


Same for me. "Your password was leaked, but it has not (yet) been cracked. Fingers crossed."

Damnit, LinkedIn.


Square users only keep the device into their phones when they are taking a payment. When it is not needed they will carry it in their pocket, backpack, purse, or even put it on their keychains.

Even if someone were to keep the device in their phone all the time I do not think it would wear out their headphone jack. It is no different than keeping headphones plugged in all the time.


I'm an engineer at Square. I'm sure most of the company is on here as well.


The reason the projection for Q1 was only 40M is because it wasn't until March that Square reached the 1M/day milestone (http://techcrunch.com/2011/03/02/square-now-processing-1-mil...).

So in January and February they were doing less than 1M per day.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: