Idea Week. Post ideas you don't plan on implementing.
Having trouble thinking of an idea for a YC application? Thursday looming near? You can take a few of mine.
Each day this week, starting today, I'll post an idea that I'd like to see implemented, but don't have time to work on myself.
Please join me in this empirical study of the value of ideas and post your own!
109 comments
[ 5.1 ms ] story [ 152 ms ] threadIf you like the idea, check out sites like prstats.com or mychances.net (very poorly implemented, but good ideas IMO). Also, let me know and I'd be happy to share our early research with you.
Disney's virtual queuing system, called Fastpass, does not create different classes of users. The only people that get special privileges are those that are doing something like Make a Wish or winners of a contest and these extremely limited superpasses don't impact overall wait times. The advantage given to Disney guests is that on each day a park will be open one hour early and up to three hours late. This isn't that much of a benefit during peak times because the park that was open early will have more guests than the other parks and you have to get up an hour early for optimal touring. The late hours aren't that much of an advantage because everyone wants to stay late in the park.
A naive perspective on Disney's Fastpass is that it doesn't actually impact total waiting time because the standby lines will take twice as long. This is incorrect because Fastpass lets the Disney engineers redistribute traffic however they want, which measurably reduced wait times for the most popular rides right after the implementation of Fastpass. Wait times are still higher than they've ever been though, because park attendance keeps going up. Disney is a profit machine.
For more information about waiting in line at Disneyworld, I strongly recommend Industrial Engineer Bob Sehlinger's The Unofficial Guide to Walt Disney World, whatever the latest edition is. He also mapped out a mathematically near-optimal plan for riding every single ride at the Magic Kingdom in one day. I really want to try doing that one day.
Slate has a good (though somewhat old) explanation of both Universal and Disney's systems (http://www.slate.com/id/2067672/sidebar/2067676/). If its numbers are still more or less right, using Fastpass reduces your wait time to about 15 minutes when you come back to the ride during the window you've been assigned.
Perhaps it would be better to just ask people for ideas that they are willing to share -- without any implication/suggestion as to whether they plan to implement it?
Disclaimer: I haven't given it a thorough evaluation yet
I would start a new reddit, scraping unofficially at first until the bird can fly on its own, and then dropping it.
If anyone thinks this problem is even solvable, and wants to work to come up with a good solution, send me an email at keshavs@berkeley.edu - I would actually love to implement something like this.
We are developing an app that solves a narrow but significant pain point for ecommerce merchants, As we deploy the app to our beta testers, they will all want to add new features. The dilemma we will face is this: which feature should we pick? The answer - and your opportunity - lies in coming up with an algorithm that picks the right feature based on analyzing three factors: (1) the pervasiveness of the pain across the user base, (2) the magnitude of the pain, and (3) our own resource limitations.
Once you apply your algorithm successfully to our app, you should be able to extend it to other apps. If you succeed, this could be boon to the beta community all over the world, and a major success for you.
Correlation is not causation, though, and the nature of correlating a number of factors dictate you would get many false alarms. However, like a metal detector, the clues for new things to look at would be worth the false alarms. The idea of all this would be to give researchers new targets and areas of research, all free and open.
Thoughts? Impediments?
Another idea to go along with this that I've thought cool would be to create a wikipedia like system where people logically state their info and arguments in a machine understandable format. The machine would then crunch everything and tell people what the contradictions and possible truths were in the overall system of thought, or particular sub systems.
Combining these two systems could make a very powerful research tool.
Impediments? People lie about their habits. People do not accurately remember things throughout the day. How to deal with missed days? If people miss days for different reasons, how do you deal with those gaps. You have to assume that the days they miss would be different enough from days they don't miss to invalidate the data of people who miss days.
So it's all about how many confirmed positives you have and whether you have reliable data on them. It works very well for credit card fraud because there is a sufficiently large number of actual fraud cases, you have reliable data about them and false alarms do not cause major disruption.
I agree with your concern about the reliability and completeness of data. I still think it's an interesting idea if there was a way to extract the data from a reliable source instead of working with what people claim to be the case.
To your example, when I get a new drug I look up all the side effects (so I would look up thalidomide). Then I have a child and it turns out that my child has birth defects. I would look that up to see who else has that out there has experienced having a child with the same birth defects. As search continues, it would eventually pop up that people who look up side effects of thalidomide also look up birth defects. Then someone could do a serious study on it sooner than later.
As in all cases using data, the major impediment is anonimity and scale of data collection.
And creating a trusted distributed computing system on facebook, where clients would compete to have users give their programs highest priority. On a simple analysis, while this would not be a very dependable system, it seems cheaper than Amazon's service at $1 an hour per core. Plus, this could be made more complex by integrating a contract system - clients can promise a certain payout based on the results of their program, kind of like the lottery.
I use Thunderbird and I've thought about digging around in the source to see if this is possible. It's not something I've found time to do though.
http://www.jgc.org/blog/2007/06/measuring-my-inbox-depth.htm...
John.
Mutt doesn't have a fancy UI but it is fast. It has no problem handling the 150k+ in my inbox (mostly unread). I know some people that swear by pine and for all the same reasons. YMMV.
Most of your UI problems are a lack of interoperability.
Workflow is like this: user creates shader using node editor (think Maya's Hypershade, but Ajaxified...), then sets permissions for the shader. Any user with permission to use the shader can see it from the plugin for his app of choice on his machine and use it. The user sets the renderer that he wants to use, the shader is compiled on the server and sent down the pipe to the user. That way, source code is kept in the hands of the people who created it. Scene renders.
I would love to build something like this, but it requires a lot more CS knowledge than I have. So if you think it's cool, roll with it and invite me to the private beta.
One of their advantages is that plugins are (of course) run on their servers, and thus even low powered desktops could have their filters be applied instantly.
The aim is to record articles where you submitted a comment and to be able to track follow-ups.
The plugin has to detect HTTP POST. It could ask the user if he wants to save the page or have an automated process that removes logins and other unrelated actions.
you'd want a hosts file for emails? interesting.
this idea might make women look bad, but i have no problem with that if it also makes some of us rich.
I had this idea because friends and I sometimes talk on IM about a topic and the chat log turns out to make quite interesting reading.
Create an engine that reads and understands the conversation and turns into a regular article or blog post; notating both authors! Also, create a link to the full IMversation.
Call it www.IMversations.com, if available.
Gosh, I would love to get a shot at YC! Hearing ideas like this is inspiring!
If you like my thoughts & are interested in hearing more ... get in touch :)
Find a way to give that majority of smokers, those who don't like what they do (but do it anyway), the ability to purchase high-quality cigarettes whose 'profits' go to cancer research and as-effective-as-possible anti-smoking campaigns.
1. Smokers don't switch brands easily, its more than just choice or taste, bodies get used to a certain cigarette. I wouldn't' just buy your cigarettes because they contribute to a good cause. All cigs are not the same. If I wanted to contribute to cancer I have other ways of doing it.
2. Most smokers actually don't believe that they will get cancer from smoking. 'It can't happen to me' syndrome.
3.The population of smokers is getting younger. An ever larger chunk comes from teenagers and folks in their early 20's who do not want to spend more for cigarettes, additionally, what they smoke is also a function of what their friends smoke.
4. Cigarettes are getting increasingly expensive because of higher government taxes in most nations among other reasons.
5. No tobacco corporation publicly admits that tobacco causes cancer. No one will sell you tobacco to make these cigs,
6. Finally, the assumption that a majority of smokers don't like smoking is wrong. Most smokers enjoy smoking. Ask a smoker about his/her after dinner smoke and that should convince you.
"[they] purportedly donate a portion of their revenues to Native American charities." http://en.wikipedia.org/wiki/Natural_American_Spirit
That isn't too far off.
Either way, with taxes, lots of money goes to government mandated campaigns against smoking, tort damages, and miscellaneous government pork. You can't really control that.
Thanks for the interesting link. I like their idea a little, but I see donating some portion of revenues to Native American charities as a far cry from hitting the nail directly on the head with a "real" mission-driven non-profit.
http://disastr.org
Lots of room for mapping apps, GIS, route finding, and an enormous capability to handle traffic spikes.
Slashing the risk of financial transactions in the developing world through a free-market inclusive biometric digital ID standard:
http://guptaoptions.com/4.SIAB-ISA.php
Just too big for a start up - they really need BigCo involvement to get going.
For the software developers who won't change to the new installer, you should at least provide a feature that notifies the user when an update is available and downloads it in the background.
http://www.tipjoy.com/our2cents/2007/10/real_liveblogging_li... "Real live-blogging, live comments, and a comment API"
Live blogging is an interesting aspect of the blogosphere. Bloggers post in real-time, often while attending an event, chiming in live with their thoughts and views. This is a great way for bloggers to communicate with their readers, but it's currently not well supported in blogging tools.
Live bloggers should be able to update their posts in some manner similar to a chat client, or collaborative editing software. The system would take the blogger's new content and appended to the post on the readers screen without a page refresh. It would be entertaining to watch something so live, along with a different take on the process of posting to a blog. Readers could see sentences edited and thoughts refined.
Ideas come from writing them down, and this would be a live crystallization of thought.
The stream could be synchronized to an event, and then later could be played back to get the same experience.
Similarly, comment sections could be live. This is nothing new, with group chat rooms updating messages to the whole group. But it would improve the user experience of a comment thread, with new comments appearing on the site live. For sites with comment modding, the votes could also be live -- watch trolling comments nose dive and disappear.
Regarding comments - comment systems should have open APIs. For example, if a blog post makes it to the front page of reddit, digg, and Hacker News, there will be 4 disparate comment threads, one at each of the news sites, and one at the original blog. Rather than forking the conversation, recommendation sites augment it: grab from and push to a comment feed. Comments on Hacker News should be visible on the original blog, and comments there should appear on Hacker News. (Except YouTube comments; no one needs to see those.)
I already mentioned a few of these points to the Disqus folks. They certainly have a good system on their hands, and any real competitor would have to do everything they do, and maybe add a few of the ideas here.
One start would be to create an opensource wordpress plugin + a client side browser bit of js code to support it. That way each user could support their own comment systems for each place they comment. The bit that currently alludes me is the discovery bit. How do others know you have commented on a particular site?
One way could be to publish say RSS feeds that link to sites you have commented on allowing others to discover what others have said. That or some sort of microformat that marks up some page that people read. This would not be real-time though. Commercial sites have an advantage here as they have a centralised place people can look.
Maybe the solution is to offer a commercial discovery site that acts as a registry of comments. So for example:
- user John writing using open source firefox plugin you make some comments on a third party site say hackernews
- plugin sends comments back to your open source wordpress blog, adds comments to blog then generates new RSS feed of comment detailing comments + discovery information (blog, url etc).
- wordpress pings a commercial site "CommentsRUs.com" that pulls the RSS file, parses it and either creates a new entry for a particular site, adds comment.
- user Jane who has subscribed to CommentsRUs.com, HackerNews site is notified by twitter that John has responded to a HackerNews article she has also commented on
- user Jane makes another comment and CommentsRUs.com either notifies user John or makes an entry on his homepage http://commentsrus.com/person/john/hackernews/ so he can follow the thread.
Of course this is no substitute for the original site because the annoying thing is the meta data is not captured. Then again if they did have some mechanism to capture the metadata ( http://goonmail.customer.netspace.net.au/hackerid ) you can do lots of useful things.