Re: Ninety-Nine Lisp Problems: pilog

2011-07-15 Thread Alexander Burger
Hi Doug, > re: the 24jul10 comment: "The more of the higher-numbered problems... > are really typical Prolog problems! All of them involve recursive > searches in some solution space." http://picolisp.com/5000/-2-1K.html > > Then perhaps picolisp's Prolog (pilog) would be ideal? I'm always > happ

Re: The PicoLisp Ticker

2011-07-15 Thread Alexander Burger
Hi all, On Fri, Jul 15, 2011 at 03:07:26PM +0200, Alexander Burger wrote: >(prinl "Disallow:" > (cond > ((= *Host '`(chop "ticker.picolisp.com")) " /") > ((= *Host '`(chop "picolisp.com")) " /21000/") ) ) This helped! Googlebot now seemed to have stopped all traversals

re: Ninety-Nine Lisp Problems: pilog

2011-07-15 Thread Doug Snead
re: the 24jul10 comment: "The more of the higher-numbered problems... are really typical Prolog problems! All of them involve recursive searches in some solution space." http://picolisp.com/5000/-2-1K.html Then perhaps picolisp's Prolog (pilog) would be ideal? I'm always happy to see pilog ex

Re: 64-bit problem on Mac

2011-07-15 Thread Alexander Burger
Hi Jon, > Using "sed -i'' 's/@plt//' x86-64.darwin.base.s" did not delete the "@plt" Hmm, so let's give up inplace-editing with 'sed'. We can use three commands instead: Move the '*.s' file to some temporary file, and then 'sed' to remove the '@plt's: mv x86-64.darwin.base.s x86-64.darwin.b

Re: 64-bit problem on Mac

2011-07-15 Thread Jon Kleiser
Hi Alex, > Hi Jon, > >> I now re-did everything from scratch, in a new clean "ongoing test", and >> I >> think the results are now more what you had expected. The error messages >> were now just this: >> sed: 1: "x86-64.darwin.base.s": extra characters at the end of x command > > Ah, OK, this make

Re: The PicoLisp Ticker

2011-07-15 Thread Alexander Burger
Hi all, OK, I extended "robots.txt" a little now. Not only "ticker.picolisp.com" is disallowed now, but also everything below /21000/ on "picolisp.com". Let's see if that persuades Google to stop the traversal. BTW, I'm handling robots.txt in the following way: "robots.txt" is actually not a fil

Re: The PicoLisp Ticker

2011-07-15 Thread Jakob Eriksson
On Fri, Jul 15, 2011 at 10:45:28AM +0200, Alexander Burger wrote: > Hi Dexen, > > > may I suggest adding rel="nofollow" to the `Next page' link (the tag)? > > I see! Didn't know about that tag. > > Any opinions? Should we relieve the busy bot? Or should we wait to see > what happens? Will Googl

Re: The PicoLisp Ticker

2011-07-15 Thread Alexander Burger
On Fri, Jul 15, 2011 at 10:53:15AM +0200, Jakob Eriksson wrote: > Put a link back to picolisp.com on each ticker page. There are pretty > good keywords I think in the bot trap. :-) Good idea! :) However, I expect the spook to stop eventually, as I've already installed the robots.txt. -- UNSUBSCR

Re: The PicoLisp Ticker

2011-07-15 Thread dexen deVries
On Friday 15 of July 2011 10:45:28 you wrote: > Hi Dexen, > > > may I suggest adding rel="nofollow" to the `Next page' link (the > > tag)? > > I see! Didn't know about that tag. because it's non-standard. Google's proprietary extension to HTML. Normally I discourage using proprietary stuff, bu

Re: The PicoLisp Ticker

2011-07-15 Thread Edwin Eyan Moragas
On Fri, Jul 15, 2011 at 4:53 PM, Jakob Eriksson wrote: > On Fri, Jul 15, 2011 at 09:58:59AM +0200, Alexander Burger wrote: >> Hi all, >> >> let me share my funny experiences about the PicoLisp Ticker, and how it >> is handled by Mr. Google: >> >>    http://picolisp.com/5000/-2-1i.html > > Put a li

Re: The PicoLisp Ticker

2011-07-15 Thread Jakob Eriksson
On Fri, Jul 15, 2011 at 09:58:59AM +0200, Alexander Burger wrote: > Hi all, > > let me share my funny experiences about the PicoLisp Ticker, and how it > is handled by Mr. Google: > >http://picolisp.com/5000/-2-1i.html Put a link back to picolisp.com on each ticker page. There are pretty goo

Re: The PicoLisp Ticker

2011-07-15 Thread Alexander Burger
Hi Dexen, > may I suggest adding rel="nofollow" to the `Next page' link (the tag)? I see! Didn't know about that tag. Any opinions? Should we relieve the busy bot? Or should we wait to see what happens? Will Google ban the whole picolisp.com site? Cheers, - Alex -- UNSUBSCRIBE: mailto:picolis

Re: The PicoLisp Ticker

2011-07-15 Thread Edwin Eyan Moragas
On Fri, Jul 15, 2011 at 4:13 PM, Doug Snead wrote: > > I think you created a bot-trap :-) aha! that figures. i'm subscribed to google alerts with 'picolisp' and 'pico lisp' as keyword. i have gotten 4 so far from that wacky ticker of yours. but don't remove it, please! it *is* fun. > > --- On

Re: The PicoLisp Ticker

2011-07-15 Thread Alexander Burger
On Fri, Jul 15, 2011 at 01:13:27AM -0700, Doug Snead wrote: > I think you created a bot-trap :-) Yeah :) Let's see how it escapes ... -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: The PicoLisp Ticker

2011-07-15 Thread dexen deVries
On Friday 15 of July 2011 10:13:27 you wrote: > I think you created a bot-trap :-) may I suggest adding rel="nofollow" to the `Next page' link (the tag)? Cheers, -- dexen deVries [[[↓][→]]] For example, if the first thing in the file is: an XML parser will recognize that the documen

Re: The PicoLisp Ticker

2011-07-15 Thread Doug Snead
I think you created a bot-trap :-) --- On Fri, 7/15/11, Alexander Burger wrote: > From: Alexander Burger > Subject: The PicoLisp Ticker > To: picolisp@software-lab.de > Date: Friday, July 15, 2011, 12:58 AM > Hi all, > > let me share my funny experiences about the PicoLisp > Ticker, and how i

The PicoLisp Ticker

2011-07-15 Thread Alexander Burger
Hi all, let me share my funny experiences about the PicoLisp Ticker, and how it is handled by Mr. Google: http://picolisp.com/5000/-2-1i.html Cheers, - Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe