312 karma · joined April 5, 2007
The tornado and cyclone APIs are closer to what I am thinking about as a web developer. Virtually never do I make an object and then think about how I'd like to adapt it to return an HTML view or programmatically add it under a parent object.
And then the next thing I would want is a fast way to throw up an ad for the app in question, just to see how many clicks it gets.
That one is more scrolly, and searches for a bit more than just 'app' ideas.
The guy I know with a printer has used it primarily for making toys and gifts, but he also needs the occasional custom camera mount, e.g. for sticking 2 tiny cameras on a model plane.
Squid can do what varnish does, but it's 2x slower by my measurements, and it has a gigantic config file. (Squid can do things that varnish can't, so you may have to use it anyway.)
I forget who I learned this trick from :(
I'd love to try your calendar version!
My data is worth tons to me, nothing at all to greplin, and a little bit to advertisers. How about I give greplin access to as much of it as possible, for some convenience that doesn't depend at all on network effects or even computing resources beyond what I have at home (or in my pocket)? At least when google does this kind of stuff they have other reasons not to leak or sell my data.
Good luck to greplin, though! Their success will mainly validate the PIM search space, which will help semweb enthusiasts like me.
Also you casually mix in "default state", so you need to decide if you're going to include all the possible modes of the more flexible stores out there or if you want this to be a silly attack on default configs.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/271706
I'm not sure where it came from originally.
I used to think that window tabbing and grouping was too complex a UI problem for window managers to support. The implementations I'd seen required lots of keys and buttons to control the window groups, so it wasn't worth their time to implement something hardly anyone would use. But I was wrong, of course! There should be chrome-style tab grouping everywhere.
Before I'm going to do anything, you need to tell me about the requests you're going to make (frequency, user-agent, robots, etc like other people have pointed out). Then I want to know about your own server's reliability. There are no clues at all that you'll be around even for a week. One way to improve this would be to offer an optional RSS feed that has a post every day that my site is up. That way I would know your server hasn't stopped completely, but you aren't blasting me with emails. Or just decorate your page in a way that makes me think you have some reason to keep your own system running.
I am using a free competitor (http://www.aboutmyip.com/AboutMyXApp/Watchdog.do) which sends me periodic uptime reports. I don't remember their setup UI being any more difficult than yours. Maybe it was, but I certainly don't remember! That's the nature of this app-- people almost never interact with it. Clearly on aboutmyip, they have several other things going on that could pay the bills.
dbpedia's RDF is somewhat easier to work with, but freebase results contain more sources than just WP, you can edit the data with a nice gui on freebase.com, and freebase spends a lot of effort tracking topics between updates. With dbpedia, I think you just get a snapshot of WP, even if that means your URIs from last week are dead.
dbpedia is open source, the freebase extractor is not.
The #2 use case example from dbpedia (use it to put WP data on your pages) is a big focus of freebase.com, and they have a bunch of tools to make that easy.
I bet there are lots of others too. This doesn't sound like something you'd ever want to write yourself (unless the widget IS your project).
(I don't know if their version is any good)
Then, don't be afraid of ambiguity. In many cases, you can Branch Both Ways. 12/10/2008 could refer to two dates, so put the item on both, showing clearly why it's there. "Lunch with Bill" could refer to a few people in my address book, so just link all of them. If your software manages to get some additional data, sort the choices so the likely one is on top.
I'd suspect that problems with implementing gmaps wouldn't affect me. My issues are more like "can I code and deploy from linux?" and "do I get access to the camera, network, speaker, etc?"
I want to be writing blog entries like this one: http://blog.danielwinter.de/archives/13