Have you considered contacting Internet Archive - or specifically, "Archive Team" - and coordinating with them to package up and deliver an archive of the public data that was produced on your platform ?
> We still feel that the internet deserves better and hope that we see more teams take on this challenge in the future
As someone with a headful of ideas hoping to potentially take on this challenge (:P) - any writeups or info on scaling/architecture would be much appreciated. There are some HighScalability articles on the bigger sites but every bit of info on comparison of architectures helps us newbies, heh.
Also, as others asked about - if you guys do manage to open source, that could be a starting point for those who liked Imzy's layout/model (personally as one of the ones who likes aspects of "oldschool" and novel design concepts, I'd go in a diff direction; but the engine could still help me figure out components needed and possibly other scaling/metrics/etc logic)
Thanks for giving it a shot, take care man.
I don't think Imzy's scalabilities issue is what did them in. I signed up to see what it was about, and saw a JS bug and reported it, and they not only fixed it super-quick, but also sent me a thank-you sticker. So their team, while imperfect as all teams are, was at least responsive and dedicated.
If I had to guess - and I do - their problems stemmed from their community size not growing as rapidly as it could have, and monetization.
That's the interesting thing - how do you build a community? How do you build a bunch of communities? How do you advertise, how do you tackle moderation successfully, how do you keep people invested, etc.
There's a billion write-ups on writing code, but nowhere near enough on running a meta-community.
Building a bunch of communities (aka facilitating community) is a different beast entirely, and seldom takes off very quickly at all. The best example of facilitating community is Meetup.com.
I've been working on a facilitation of community model called Horizon (http://www.horizonapp.co) which is best thought of as airbnb/couchsurfing with friends, friends of friends, and communities. So, privately, rather than publicly with strangers.
You can either facilitate existing community, or build a community. Trying to do both is a recipe for disaster imho.
If you're an engineer like me, we'll often overweight tech choices, rather than the product and user acquisition decisions that matter in a social network.
Can you explain a bit about how you tried to monetize the site? What did you try? What worked and what didn't?
It's incredibly small for the amount of media attention they received. I think shutting down is the right, and responsible move here.
Did you focus on any cohort or did you just experiment with lots of cohorts hoping one would take off? If you did focus, what if anything did you learn?
(One of the things that worries me a lot about taking venture capital is the pressure to grow quickly over growing well / sustainably, so I'm pretty curious about this....)
If they're not seeing the demand it's smarter to cut losses than to continue on without a plan to make the site sustainable.
Bit curious if there was any weighting algorithm in the voting?
If we had done better with this, we could have gone to market quicker and probably done a better job finding product/market fit.
There's of course more, but this is the biggest thing.
Why do people do this?? Please don't build for mega huge scales before you've gone to market...it's a huge waste of time and money. I guess developers have too much pride to not make the _best_ platform
People doing startups are natural optimists, bold risk-takers. And to get the money, you have to sell people on a dream of giant scale, on a big vision of what is to come. If you can't create and sell that vision, nobody gives you the money.
To then turn around and say, "Ok, what's the minimum necessary?" is really hard. You have to throw out 99% of your vision. You have to turn into a risk-averse pessimist. After talking about making the best thing, you have to go and make nearly the worst thing. Then you user-test it, discover why it sucks for your core audience, and make it suck less, in hopes that this time you've got the minimum viable product.
Making that turn is definitely a skill, something you have to learn and practice. It's not something we learn at all just building things to spec, which is the normal experience. It's the kind of product management that in theory everybody should do, but that in practice you only really are forced to do if you don't have much money.
Seems related to: "MVP" --> "the rewrite / second system"
I also have an amazing staff of developers, community minded folks, product people, executives, who are looking for work. Many of them mare open to moving (we are in Salt Lake City) and all are open to remote work. They are all very talented. Please drop me a line if you're interested.