Idea #13: Wishlist app

This would be a fun application where you could scan or enter something into your wishlist. A certain amount of money every period could go to your bank. This app would search online marketplaces for the item at the top of your wishlist. When the amount in your "bank" exceeds the cost of the item, it will automatically buy and ship it to you. Alternative method: You could set a price you were willing to pay instead and when the price drops below it will autobuy it if there is enough in the bank.

Idea #12: Cabinets and drawers with rounded corners/edges

If I ever make a set of cabinet drawers or furniture, I'd love to make the inside corners rounded. Reasons: 1) Whenever I am cleaning anything, the corners of drawers are the hardest to keep clean. 2) Moving something out of the drawer could be as easy as moving it to the edge instead of digging at it with your nails 3) Extra support-- the corners are your weak point and can help stabilize the structure

Idea #11: Location based apps

One of the worst things about the current field of location based apps is that you have to go to them. 4square, facebook, everything is in its own sandbox. What if instead, locations could tell you which apps were up. For example, as you walk through a mall, each stores app blinks in and out as you pass it by. Any apps you have installed, such as 4square tell you if there is anything special for that location. The locations could be marked by cell triangulation, GPS, NFC, low power radio, etc. The trick is to have mobile devices pick up location instantly (no QR code fail or taking pics). I think this would be the real power of a location based service rather than advertising. Money would be made by events and some advertising. Anything annoying could be filtered out easily (location spam). Other specific ideas: - Doorbells that announce who it is - Car starting - Finding your car - Traffic signs - Tolls - Purchasing at stores - Menus and specials - Enhance reality integration

Idea #10: Smelly cell models

Make models of cells that each individual smell like something relating to its function. Idea spawned from this: http://toulousestreet.wordpress.com/2012/02/08/rough-trade/ Will definitely help memory retention as smell is more closely associated with memory

Idea #9: A better way to do online Dating

There are two things very wrong with online dating: 1) You make your own profile and people tend not to know themselves from an external point of view 2) There is a huge trust barrier to overcome between sane people. Conversation without context can feel forced and fake. The first can be solved by having your friends write your profile for you. It'd be interesting for sure, not sure on how well that would work out though. The second is why blind dates work-- both people are stuck in a strange awkward situation that engenders trust. I feel that if your friends choose who you go on dates with, it would be better for this. Its an interesting concept, though I can't imagine it gaining traction in the US (this would work great in India).

Idea #8: Better OpenID

Add a property in your DNS record that gives a url format for OpenID logins. Your OpenId login can then be someone@somewhere[.overtherainbow].biz. You can get the needed url from the DNS record for overtherainbow.biz (and use subdomains appropriately) and redirect/validate the user from there.

This idea must exist somewhere, hmm.

Idea #7: Anti-spam measures

Spam is an issue in many blogs, forums, ims, any communication. It is only an issue if it reaches a real person. Therefore, all actions and modifications to content made by untrusted persons will have to undergo some kind of review in order to not cause a spam problem. In the meantime, their content will have to wait, which is a tradeoff.

1 - Direct connection, XMPP style

Submit comes with token and user@server. That token is validated with that server for that user. Content is trusted to come from that user. No sign in required.

If users@servers are blacklisted, spam will still occur. Users may be required to register then and those registered users whitelisted. Who to trust to register? Lets go onto number 2:

2 - Ring of trust

Any user may register. However, not all are trusted. Trust can earned for user@server by asking server who vouches for user. If we trust any user that vouches for that user, we verify that with that voucher_user@voucher_server. If verified, we assign +rep trust from that user and store it locally with that user's registration. If the circle of trust is outside our scope of registered users, we go to number 3:

3 - Proof of work

User is asked to give a proof of work problem that an average user can handle. If this is solved correctly (maybe a captcha in addition or instead), the user comment is given to manual review. If a manual review is verified, that user is assigned +1 rep from the system.

Caveats

• You still need manual review. If your Proof of work is broken, manual verification can become unwieldy.
• User information must be sent with a comment. That user's server must be up at the time of connection.
• This system only works if trust from the system may be revoked (otherwise mistakes are permanent). Certain highly networked users might become too big to fail and if hacked, cause cascading registration issues (or conversely, solutions). Keeping track of a reputation as well as trust will help mitigate this, as users can be slowly trusted by the system due to reputation rather than relying solely on a brittle trust network.
• The circle of trust implementation here is very basic. The problem is that the server might not know which of its user's vouchers are registered with the site, and this information is private. This results in extraneous information. The 'who can vouch for me' information itself might be private as well. It would likely be better to send along the system name to the user when asking for vouchers. This way they can ask their vouchers who trusts that server and maintain privacy of their vouchers.
• This system does not allow for mass anonymity except through duplicate accounts.