Unhandled Perception
From the mind of a developer.

Tuesday, February 26, 2008

IDEA: Video cliff notes of famous movies

This is a very simple idea. Take a movie and reduce it down to a 5min movie cliff note where the plot and the best movie points (key lines, jokes or action scenes) are brought out.

This will let you watch any movie in 5min and be able to hold a conversation with someone about it.

Would be interesting to see if someone could do it.

Labels:

Saturday, January 05, 2008

IDEA: Playlist processor

Create a website that accepts uploads of a music playlist and provides:
  • A list of songs I like. Basically just a very friendly listing of the songs contained within my playlist
  • An analysis of the type of music I like to listen to (kinda of like what WTF Music Info does)
  • Suggestions of music that may appeal to me
How to be profitable:
  • Use an affiliate link to songs and music I may like
  • Advertising to key music websites
What it needs to be successful:
  • Access to a very large song database (like CDDB) for comparing and extracting information from a song list

Labels: ,

Saturday, October 20, 2007

IDEA: Online service to distribute your development assets after your death

What I have been thinking about is all the websites, software and other internet assets that would be lost due to its owner death. How do you preserve assets that others, in your family, may not know what to do with when you die.

If you look at Veign's stuff. Veign has 8 online application, 5 full blown websites that support a specific community, 7 freeware applications and many code samples in my dev library. What would happen to this stuff if something happened to me. I would want the stuff passed along to someone else who I thought would keep the stuff alive, for free, as I intended.

I thought there was a need for a web service where keys (passwords), files (source code) and instructions where kept in a highly secure, encrypted state with a list of other users who would get parts or all of the information upon something happening to me. Basically, withing my account I have my assets and my recipient's. I can divide my assets up against my recipient's who would be notified upon my death (email, snail mail).

The service would be marketed as a way to preserve the assets of the internet and keeping the original developers intent alive even after their death.

The "I will try and contact you and if you don't respond then you are dead approach" that some current services employ would not work since I would be asking people to entrust very sensitive information to the website service and prematurely releasing this information could be devastating for the owner.

I think a two-key process would work better where both keys have to be 'turned' to mark you as dead. Then you can give out these keys to people within your family or, for a simple charge, put the keys within the service who you turn the keys upon proof of death (actual person verifies).

leave your thoughts...

Labels:

Friday, October 19, 2007

IDEA: Social Shopping website

Create a website that attempts to simulate or bring to the internet the same experience that women have when going shopping together. Allow them, through a website, to shop together, compare products, discuss products and see what each other is looking to buy.

I see shopping online as a very solitaire experience when it doesn't need to be. Create a Social Shopping website where you create a group of other users that you shop with. If nobody is online you shop as your normally do now. If someone in your group is online you get to shop with them (if you want) and have a more social shopping experience.

thoughts?

Labels:

Wednesday, October 10, 2007

IDEA: A website to help me remeber who you are

This idea I really haven't had the time to flesh out properly but the gist of the idea is a website geared towards mobile devices that lets you capture the images of people you meet so you can recall them later on. With more and more mobile devices supporting a web browser it would be nice to be able call up a website that helps jog my memory on who somebody is and how I know them. Would also be nice to know its someone's birthday, what their spouses name is or any other information that helps me get into a conversation with someone.

The way I see it working is I meet someone, capture their image into my mobile device, image is automatically pushed into my account in the website. Later on I login and update the person's information and 'tag' this person for easy retrieval later on. To retrieve the information I can capture the image again, and with the use of facial recognition software on the server, recall a persons profile.

There are so many time I meet someone and I either can't remember their name or can't remember how I know them or details of this person.

Like all other ideas posted here I am just throwing this out there. Good or bad idea it doesn't matter, as I am just purging my mind of things that I think would be cool to have developed.

Names for it:
  • FaceBase.com (as in a Face Database)
  • RememberYou.com
  • RemindMe.com
Your thoughts on this? Leave a comment

Labels:

Thursday, August 30, 2007

IDEA: Search engine query repository and bookmarking service

Overview
Create a bookmarking system where the user no longer bookmarks a single website but instead is bookmarking a highly perfected (over time in the system) search engine query. What this does is prevent the annoying 'page not found' you get when you recall a bookmark. Instead you are always presented with the best possible websites for your topic.

The system would allow for, and encourage, tweaking queries for even better results. This allows your bookmarked queries to become better through the community using the site.

A community member would be able to request a query update where the original query creator would have the option of appending the change or branching the query into a related branch query. Related branch queries are a mechanism to see what other queries had be spawned from your original, perfected query.

Features
  • Easily store and recall search queries in all major browsers
  • With your account you can make a query public or private
  • Public queries can be searched, viewed and modified by other users
  • Modified queries requests are sent to you so you can chose to update your query with a better, advanced query
  • Queries can be branched, or spawned, from an existing query. All query branches can be followed to see how a query has developed over time
  • Complete user account management
  • IE and Firefox toolbars to easily 'capture' queries
  • Queries could attempt to tweak themselves by the user providing a target webpage. The system would then try and create the best possible query that brings the webpage, and like results, into the top spots in the designated search engine.
  • Browser toolbar could have a Query Suggestion button where the system reads the page and attempts to create a query based on the pages content and the system knowledge of advanced query creation.
Imagine how many pages will be indexed in 5 or 10 years and as pages indexed increase it would make sense that bookmarked pages would increase also. By bookmarking a query you greatly reduce your bookmarks since a single query, on a topic, can replace large groups of page bookmarks.

Obviously a lot needs to be worked out but this is the basis for the website. First on block is a big thing and so far nobody else is doing this. I think this is a great idea and I just don't have the time to implement so I thought I would release the idea and see what happens.

Discussion going on now at DonationCoder about this idea

Email me if you develop it and donations accepted :-)

Labels:

Monday, December 18, 2006

Digg Feature request

Digg should allow developers and content managers the option to not have their pages listed on Digg or other social sites. We all know that a front page listing on Digg could bring down a server and I'm sure there are people who really don't want certain content from being Dugg. This could work for all social sites.

A simple META tag would work.

Search engines use a meta tag like this for excluding them:
meta name="robots" content="noindex, nofollow"

So, how about something like this for social sites:
meta name="social" content="nolisting"

What do you think?

Submit this to Digg and lets see what others have to say

Labels: