2026-06-29 01:13:21 <xentrac     > I think Chuck never released OKAD because he didn't want to
2026-06-29 07:40:44 <xentrac     > oh my GOD cleobul__ cleobuline what is WRONG!?
2026-06-29 07:41:22 <xentrac     > you've timed out more than 30 times in the last HOUR
2026-06-29 07:43:13 <iv4nshm4k0v > M-m?  I've counted only 24 times over three hours?
2026-06-29 07:46:30 <xentrac     > 05:35 -!- cleobul__ [~cleobulin@2a01:e0a:eb5:3900:d9f3:b094:f877:bacd] has quit [Ping timeout: 276 seconds]
2026-06-29 07:46:33 <xentrac     > 05:35 -!- cleobul__ [~cleobulin@2a01:e0a:eb5:3900:7564:2651:8fcf:ded6] has joined ##forth
2026-06-29 07:46:36 <xentrac     > 05:38 -!- cleobuline [~cleobulin@2a01:e0a:eb5:3900:c87f:6f27:a04d:c6a9] has quit [Ping timeout: 252 seconds]
2026-06-29 07:46:39 <xentrac     > 05:39 -!- cleobuli_ [~cleobulin@2a01:e0a:eb5:3900:4989:ff2f:b3a2:cda] has quit [Ping timeout: 252 seconds]
2026-06-29 07:48:40 <xentrac     > I guess half of those are signing back on.  so it's only more than 15 times.  you are correct; I was wrong.  I appreciate the correction
2026-06-29 14:00:10 <cleobul__   > xentrac:  i don't know
2026-06-29 14:01:17 <cleobul__   > may be it's the sleep of the computer
2026-06-29 14:02:52 <cleobul__   > may be the client programmed with the feet
2026-06-29 14:15:37 <cleobul__   > forthBot:  LOAD ini.fth
2026-06-29 14:15:37 <forthBot    > File ini.fth with MOON  loaded
2026-06-29 14:15:46 <cleobul__   > forthBot:  MOON
2026-06-29 14:15:46 <forthBot    > Phase de la lune pour Mon June 29 2026
2026-06-29 14:15:47 <forthBot    > 🌕 Pleine lune Admirez-la sur les toits de Paris ! Illumination 99%
2026-06-29 14:16:20 <cleobul__   > forthBot:  CREDIT
2026-06-29 14:16:20 <forthBot    > Brought to you by Cleobuline updated with hashtable with the help of Grok  https://github.com/cleobuline/forth-bot-gmp-irc-threaded-multi-users/tree/main Site https://labynet.fr
2026-06-29 14:53:07 <Stalevar    > cleobul__, by the way is your bot running in a vm or something? Because in forth you can easily overwrite entire process memory and get to run whatever including any shell commands?
2026-06-29 14:53:33 <Stalevar    > even if you removed words like system (not sure if it's even present in ANS )
2026-06-29 14:56:33 <Stalevar    > cleobul__, also how do you regard somebody pentesting your bot to try and take over the server it runs on as proof of concept?
2026-06-29 15:16:11 <cleobul__   > Stalevar:   there is not instruction to write u$in the bot memot`ry
2026-06-29 15:17:04 <cleobul__   > Stalevar:    12345 123 ! is illegal
2026-06-29 15:17:36 <cleobul__   > my bot write only in variable created
2026-06-29 15:18:24 <cleobul__   > Stalevar:  forthBot does not have acces to the main memory
2026-06-29 15:21:12 <cleobul__   > Stalevar:  it's not a real forth , juste a home made interpreter
2026-06-29 15:24:39 <Stalevar    > cleobul__, it's still a mistake to let bot write arbitrary stuff into IRC socket, you should implement this part (IRC connection and messages) in main program?
2026-06-29 15:25:03 <Stalevar    > or it's just insufficient understanding of IRC protocol?
2026-06-29 15:25:23 <Stalevar    > You must filter attempts to send 0x0a and 0x0d bytes
2026-06-29 15:25:45 <cleobul__   > i will look up that
2026-06-29 15:26:13 <Stalevar    > Though one needs to look in IRC spec to see what bytes values can be within message and which work as terminators
2026-06-29 15:27:05 <Stalevar    > forthBot: 10 emit 20 emit 10 emit cr
2026-06-29 15:27:05 <forthBot    > Error: Unknown word: emit
2026-06-29 15:27:22 <Stalevar    > forthBot: 10 EMIT 20 EMIT 10 EMIT CR
2026-06-29 15:27:52 <Stalevar    > forthBot: 13 EMIT 70 EMIT 13 EMIT CR
2026-06-29 15:28:16 <Stalevar    > forthBot: 11 EMIT 70 EMIT 11 EMIT CR
2026-06-29 15:28:16 <forthBot    > F
2026-06-29 15:28:37 <Stalevar    > forthBot: 12 EMIT 70 EMIT 12 EMIT CR
2026-06-29 15:28:38 <forthBot    > F
2026-06-29 15:28:55 <cleobul__   > yes and ?
2026-06-29 15:28:56 <Stalevar    > So bytes 12 and 11 are OK even though they work as linebreaks
2026-06-29 15:29:44 <Stalevar    > forthBot: 10 EMIT ."NICK forthBot" 10 EMIT CR
2026-06-29 15:29:45 <forthBot    > Error: Unknown word: ."NICK
2026-06-29 15:29:50 <Stalevar    > forthBot: 10 EMIT ." NICK forthBot" 10 EMIT CR
2026-06-29 15:29:50 <forthBot    > NICK forthBot
2026-06-29 15:30:09 <Stalevar    > Hm, you might have fixed it
2026-06-29 15:30:16 <Stalevar    > forthBot: 13 EMIT ." NICK forthBot" 13 EMIT CR
2026-06-29 15:30:16 <forthBot    > NICK forthBot
2026-06-29 15:30:17 <forthBot    > Error: EMIT: Stack underflow
2026-06-29 15:30:35 <cleobul__   > forthBot: 10 EMIT ." /NICK forthBot2" 10 EMIT CR
2026-06-29 15:30:36 <forthBot    > /NICK forthBot2
2026-06-29 15:30:54 <Stalevar    > cleobul__, / is escape for human IRC client
2026-06-29 15:31:04 <cleobul__   > ok
2026-06-29 15:31:07 <Stalevar    > In raw TCP socket you send NICK without /
2026-06-29 15:32:18 <Stalevar    > forthBot: 13 EMIT ." test1 " 13 EMIT ." test2 " 13 EMIT CR
2026-06-29 15:32:18 <forthBot    > test1
2026-06-29 15:32:19 <forthBot    > Error: EMIT: Stack underflow
2026-06-29 15:32:35 <cleobul__   > forthBot: 12 EMIT ." NICK forthBot2" 12 EMIT CR
2026-06-29 15:32:35 <forthBot    > NICK forthBot2
2026-06-29 15:32:36 <forthBot    > 
2026-06-29 17:32:18 <forthBot    > Environment for Stalevar inactive, freeing...
2026-06-29 17:32:35 <forthBot    > Environment for cleobul__ inactive, freeing...
2026-06-29 21:14:33 <oak         > Is there a word that's like TUCK but puts the duplicated value back one further? Kind of like a.. -ROTDUP?
2026-06-29 21:14:47 <oak         > 1 2 3 -- 3 1 2 3
2026-06-29 21:20:18 <lofty       > I've seen the word "N BURY" to put the top of the stack N entries deep (kind of the inverse of "PICK"), and so this would be like "DUP 3 BURY" or such
2026-06-29 21:43:42 <crc         > 
ACTION uses a `reorder` word (non-standard) for things like that

2026-06-29 21:47:17 <crc         > #1 #2 #3 'abc 'cabc reorder
2026-06-29 22:54:59 <veltas      > : -ROTDUP DUP >R -ROT R> ;
2026-06-29 22:55:34 <veltas      > But really I would be avoiding this kind of stack operation, too complicated
2026-06-29 22:55:41 <veltas      > Simplify or if not possible then use vars
2026-06-29 23:19:18 <xentrac     > of course my advice, especially for beginners, is "use vars and then try to simplify" :-)