3,016 karma · joined September 10, 2007
Reach out me to via: 954.247.1673 || '%sb@bitsorbricks.com' % request.GET['id'][0]
YC Badge: 0x91b51c173a4bDAa1A60e234fC3f705A16D228740
I had a pretty great experience and would recommend TripleByte.
There was a question about the financial risk of launching early - PG's answer was really good, but it seemed pretty clear to me: Launching early costs less time and money. So you should launch something that works, as soon as possible with the minimum number of people required to build something useful (probably 2-4 people). Beyond that, you make your "vision" meet reality, where you can do magical things like learn from users/customers, which is basically priceless.
As a fellow vegetarian, I tend to increase fruit intake & do early morning workouts or yoga when I feel like this. Give that a try @sama
Hey Tom! Guy from the article here. First off, thanks for Metabase. I'm a big fan & recommend it often.
Second, you're absolutely right. We have been capping people at $1500 purchases per month unless they were willing to provide identification & an understanding of the risks associated with our service.
> Nor would I recommend the founders continue to run it unless they've consulted a lawyer and are aware they're likely running a money transmitter business. See https://en.bitcoin.it/wiki/Casascius_physical_bitcoins#Suspe....
Casascius very simply shut down, some of our counsel thinks we have legal basis to not be a money transmitter while other legal counsel believes we may be. We're currently working through that to understand how and where we stand to adapt our offering to be within the limits of the law.
> Accepting credit cards as payment for cryptocurrency is also a risky proposition, to say the least.
Agreed. Mutual trust has been required, we're working on something better than that now :D
We've had some conversations with our legal team at Cooley & some conversations with outside counsel at Goodwin Procter. They have not been able to reach consensus on whether we fall within regulatory oversight. Until then, we're not going to be selling anymore in the United States. It comes down to whether this is art or a collectible or not. We're working on it & have stopped sales for the time being. :)
> Not to mention selling crypto with credit cards is a great way to go broke unless you own the keys like Coinbase does.
This is a fair point, there is actually trust on both sides of the relationship here - we're trusting that our customers will not chargeback & they're trusting us not to steal their keys.
> Also, why would you trust the keys they are sending you? Having someone else generate a wallet for you then sending it to you via a USB key sounds very very bad.
We originally thought so as well. When we sold a bunch we were surprised & started talking to our customers. It turns out, they don't want to go through the hassle of finding a wallet creator, disconnecting their computer from the internet, generating a wallet, writing down private keys or mnemonics & securing them.
You can think of this kind of how car dealerships don't run their own mail servers anymore or pizza places don't run their own instance of a bind DNS server. They want the convenience of not having to worry about it.
We're currently working hard on a v2 that makes it a bit more secure while maintaining usability.
> I don't get this.
We really didn't either, but the people that have trusted us with their money helped us understand this: Everyone who is working on cryptocurrency projects is suffering from the curse of knowledge [1] - most of them don't care about the end user.
There is also apparently https://screencast-o-matic.com/
I've been reading https://www.manning.com/books/grokking-deep-learning and have been liking it better than this tutorial.
The relevant part is here: https://github.com/allynalford/investor_day/blob/master/app/...
Basically, if the curation is good, I'll be there looking for improvements to my "stack".
I've futzed around with ML docs (dataquest, random articles, first 3 weeks of andrew ng course on coursera) & what I don't get about this (http://tensorflow.org/tutorials/mnist/beginners/index.md) is how to actually make a prediction / classification on something that is not "test" data. Can anyone point me in the right direction of how to "use" a model once I have it validated, like we do at the end of that tutorial?