984 karma · joined October 9, 2010
User-Agent: *
Disallow: /21000
or User-Agent: *
Disallow: /http://code.google.com/web/controlcrawlindex/docs/robots_txt...
the robots.txt of http://picolisp.com (found at http://picolisp.com/robots.txt) allows the indexing of http://picolisp.com/21000 and all follow up pages.
why? see the spec:
The disallow directive specifies paths that must not be accessed by the designated crawlers. When no path is specified, the directive is ignored.
see here https://github.com/franzenzenhofer/robotstxt for coffeescript implementation of a robots.txt parser
in the next step they claim i missunderstood the question, the question was not really about "what to do with the beans", it was more about "how should we stick them up our noses in the best way"
>I need to add the ability to use any image you want, not just the canned ones I have. This is not some feature I just left out. It turns out that the browser/javascript system deliberately screens out access to images coming from other domains
i solved this here http://www.barbafan.de/farbzauber/w but yeah, u need some server side code that takes an url and returns the image data as a base64 string, i havent found another workaround yet and i doubt that there is one.
well G watches your searches anyway, even tunes the search results to your search history, as its cookie dependend, not log in dependend. see http://www.google.com/support/accounts/bin/answer.py?answer=...
i wonder which other tools could be implemented that simple...
i kinda miss dead tree magazines with actual working code ... maybe we should start a github magazine?
unimportant at google: google translate api
important at google: $3 for $10 worth of drinks, pastries and treats at Floyd’s Coffee Shop
said that: i use google docs but i just love my dropbox (after i got rid of the growl spam the installed on my system)
they just took it from there...