jimengland@gmail.com
I had the opportunity to attend the Web 2.0 Expo earlier this week. While at the event, I was inspired to build out a prototype for a problem I saw with the Twitter stream.
The problem is that hash tags are fleeting; Twitter focuses on live results, and we lose track of tweets over time. This was especially true during the Lean Startup Intensive. #leanstartup was great when it was live on Monday, with the results consisting of live tweets of each presenter. However, if we search for the hash tag now, we get a mess of content not specifically tied to that event.
The concept is to "save a moment in time" in Twitter for a particular hash tag while also adding additional media content (SlideShare, blog posts) related to that subject.
I would appreciate any feedback on this prototype. Is there value in a product like this?
The closest model for server usage in my opinion would be Pownce or Facebook. The product will be storing user submitted web content including photos, audio, and URLs.
I found an article that tries to estimate Facebook's server costs. These numbers seemed somewhat high to me, however: http://fishtrain.com/2007/11/07/facebook-valuation/
Are there any online resources for estimating server capacity and cost? Any educated guesses for the startup to use?
Thank you!