1,633 karma · joined September 10, 2010
http://disattention.com/contact/
twitter.com/bobdiaes
A cross-browser effort that implements a few key features from OptimizeGoogle, would be a very good idea. I'd be up for that.
http://en.wikipedia.org/wiki/May_you_live_in_interesting_tim...
My rule of thumb is I need to stay about a month at each location, so that I don't feel rushed and it's worth the time to setup a temporary base.
A week-long vacation, trying to cram everything in the shortest amount of time, is not real "traveling" for me.
It's a security feature against low-tech threats.
There is another SRP implementation in JS+PHP: http://www.denksoft.com/wordpress/web-development/secure-aja...
We definitely need more SRP implementations, glad to see more people working on it.
What I really want though is something that will let me continue to use the Delicious extension for Firefox.
The permanent nature of ads built into a map can be a good thing. The advertiser gets lifetime product placement and doesn't have to worry about the developer removing it. However, details are irrelevant if the map is only going to be played by a dozen people.
Advertisers will want metrics.The best place to get data will be directly from the game servers. You could make a small utility that gathers traffic/gameplay/map data and sends it back to you. Then you give server owners a piece of the action in exchange for sending you data and running more maps with ads.
If you go down that road, you might as well find a few hackers to make mods that dynamically place ads in the game. I'm guessing some games might already provide native functionality that could help with this.
By the way, Google is already doing web-based game ads: http://www.google.com/ads/games/index.html
I like that I can hook it up to my Github projects. Here's the how-to: http://leetcode.net/blog/2009/01/integrating-git-svn-with-ma...
I'm always amazed at what can be found on wikipedia.
Everyone submits ideas, some voting and discussion takes place, then people work on what they want to work on.
Splitting equity and revenue is a much more complicated issue. In my experience it's easy to figure this out for small teams, provided the members are reasonable and can appreciate each other's work.
There was a software startup that was trying to do exactly this but I can't remember what it's called. Quirky is also doing this, albeit for tangible products, and they have an interesting approach.
Ideas?