This looks really good and could see us using this, but the image upload front-end is essential for our needs.

Do you have an ETA on when you are going to be releasing the image upload front-end function?

This is definitely on our short list and SnapEditor won't go to production without the image uploader. I'm going to guesstimate we'll have some sort of support in about a month along with some other got-to-have features.

We want to get this right and part of that is coming up with a great and simple server API to handle the uploads across all platforms/languages/frameworks.

TheSunny

I just submitted something that I need doing - looking forward to seeing what you guys are capable of doing.

EDIT: One feature I would like to see is for you to have an automatic email confirmation of a submission, including the original submission body itself as a record of what was requested.

Possibly the most impressive thing is the disclosure they are hosting 30,000 sites.

At the lowest monthly plan cost of $29/mo/site thats a $10MM+ annual revenue business created in just 2 years.

Good job!

But some plans can have an unlimited number of sites, I think.

It takes time for a startup to develop and refine the message and brand that it wants to communicate.

While that unique brand and vision is unclear and unrefined, the closet substitute likely to be "right" is the average of what everyone else is doing.

Have you thought to tap out the Japanese Expat market as an advertising/marketing opportunity?

That might include Japanese people living abroad, students, workers living in the middle east for 12 months, etc

The service could very easily appeal to people living abroad and wanting a reminder of home every month.

I might try it, but wouldn't they have friends who send them items? It's very common even inside Japan that relatives send food items to each other, and I the Japanese expats who I knew in Finland were also getting items sent to them by their parents.

I agree with mendable, I feel like your service is very convenient, much more so than having friends send you things.

Nice idea.

What is the product you are working on?

You talked about about the numbers, but some general idea of the app would be interesting if we are going to follow along with your progress.

This could work really well to harness the power of learning from the community if you reveal your product.

I'm sure lots of folks, especially here, would jump in and help you improve your registration rate if we had visibility.

This Wired article[1] states that the first co-founder owned 40% of the company and the second co-founder owned 10% of the company at the time of acquisition.

This might suggest they started out with an 80/20 split.

Why? How did that split come about?

[1] http://www.wired.com/epicenter/2012/04/facebook-buys-instagr...

Kevin Systrom went all in at an earlier point. Discussed in more detail by the two of them here: http://ecorner.stanford.edu/authorMaterialInfo.html?mid=2745 (video)

Nice idea of drag-dropping onto face icons.

You defo need to change the name ASAP to avoid any trademark infringement issues though.

Congrats on the launch!

I'm curious about the previous project - lifegrams.com - I was talking to my OH about a similar idea just a few hours ago.

Would be interested to see a lessons-learned for the previous project. Was it successful, if not as successful as hoped, why not, how much traction, what could have been done differently, etc.

Would be happy to chat some time about that experience! Feel free to shoot us an email. gregarious at getchute dot com

Storing 50TB on Amazon S3 (US-EAST) Premium costs ~ $6,264

Storing 50TB on Amazon S3 (US-EAST) Reduced Redundancy costs ~ $4,160

Storing 50TB on Nimbus: $3,000

Is Nimbus's fault tolerance closer to the Premium S3 or the Reduced Redundancy S3?

(for completeness, Nimbus's transfer out is $0.06 per GB vs Amazon's $0.12 per GB).

They say[^1] that they can tolerate destruction of any 2 nodes without data loss. I don't know how many nodes Amazon S3 premium can tolerate.

[^1]: https://nimbus.io/architecture/

Amazon doesn't talk about their numbers either. The only thing they do say is that RRS (reduced redundancy storage) 'stores objects on multiple devices across multiple facilities, providing 400 times the durability of a typical disk drive, but does not replicate objects as many times as standard Amazon S3 storage, and thus is even more cost effective.'

This is at the main page: http://aws.amazon.com/s3/ (search for RRS)

Amazon says that S3 provides eleven nines (99.999999999%) durability of files. So if you have 100 billion objects in S3, you should expect to lose on average 1 per year. Or, if you have 10,000 files, you should expect to lose 1 per 10 million years. In addition they say it can tolerate the simultaneous failure of two datacenters. Nimbus, with 3 copies total, appears much less redundant... but nobody knows how Amazon calculated their eleven nines claim.