IRC Log - 2025-04-05 - ##forth

Channel: ##forth
Total messages: 76
Time range: 09:21:02 - 22:43:21
Most active: cleobuline (36), veltas (19), mforth (14)
09:21:02 ##forth <veltas> crc: I think it would be useful, although possibly more in #retro, to be able to get responses in the main channel
09:21:24 ##forth <veltas> Specifically when we're demonstrating something, teaching, or learning
09:22:59 ##forth <veltas> Yeah IRC bots are hard to do right
09:33:00 ##forth <veltas> I guess the 'right' networking Forth interface probably isn't IRC anyway
09:33:30 ##forth <veltas> We need to create the 'BLOCK' protocol, something very Forth oriented, for networking between Forths
10:17:38 ##forth <KipIngram> I've thought at times about gluing ipfs into the block protocol.
10:17:57 ##forth <KipIngram> On a 64-bit system you certainly have enough clock #'s.
10:18:05 ##forth <KipIngram> s/clock/block/
11:12:06 ##forth <cleobuline> mforth: : test 0 4 DO I . -1 +LOOP ;
11:12:09 ##forth <cleobuline> forth: test
11:12:22 ##forth <cleobuline> mforth: test
11:12:22 ##forth <mforth> 4
11:12:23 ##forth <mforth> 3
11:12:29 ##forth <cleobuline> perfect
12:45:23 ##forth <veltas> KipIngram: I think instead I wouldn't bother mapping, it over-complicates it
12:45:33 ##forth <veltas> If that's what you meant, not sure
12:46:55 ##forth <veltas> I would probably do something like: 192.168.000.001 800 600 DOWNLOAD to download 192.168.0.1 block 800 to block 600
12:47:21 ##forth <veltas> And DNS example.com would get the IP address for example.com
12:47:36 ##forth <veltas> Maybe DOWNLOAD4 for IPV4, or DOWNLOAD6 for IPV6
12:48:27 ##forth <veltas> Just have it ABORT" on failures, e.g. BLOCK NOT FOUND or ACCESS DENIED
12:50:51 ##forth <veltas> Maybe DOWNLOADS for multiple blocks
12:51:22 ##forth <veltas> There should probably be a standard block for the 'root' of the blocksite
12:54:44 ##forth <veltas> Like DNS veltas.co.uk 1 1000 BLOCKSITE and I'd have that save it in block 1000 and LIST it
12:55:27 ##forth <veltas> And block 1 should contain the 'root' info, like a sitemap/index/motd with some useful blocksite numbers to explore
13:21:39 ##forth <veltas> I guess can send stuff, up to the specific blocksite what UPLOAD will mean, and on what block
13:22:04 ##forth <veltas> And provide sandboxed Forth words on both sides called COFFEE
13:24:04 ##forth <veltas> And we can get lost writing COFFEE-FORTH frameworks
13:27:01 ##forth <cleobuline> mforth: LOAD "test.fth"
13:27:37 ##forth <cleobuline> mforth: 123456789123457 FPRIME? .
13:27:38 ##forth <mforth> 1
13:32:37 ##forth <cleobuline> fast enougth
13:40:34 ##forth <cleobuline> mforth: 0 1000 RAND .
13:40:34 ##forth <mforth> 333
14:01:39 ##forth <cleobuline> voil 'ai fini https://github.com/cleobuline/forth-bot-irc-final
14:04:15 ##forth <cleobuline> it seem to not have bugs for now
14:06:37 ##forth <cleobuline> mforth: : BACK-LOOP 0 10 DO I -1 +LOOP .S ;
14:06:48 ##forth <cleobuline> mforth: BACK-LOOP
14:06:48 ##forth <mforth> <10> 10 9 8 7 6 5 4 3 2 1
17:16:35 ##forth <cleobuline> forth: 10000 DELAY ." test" CR
17:16:51 ##forth <cleobuline> mforth: 10000 DELAY ." test" CR
17:18:51 ##forth <cleobuline> mforth: 10000 DELAY ." test" CR
17:19:01 ##forth <mforth> test
17:28:15 ##forth <cleobuline> mforth: 3600 CONSTANT HOUR
19:00:11 ##forth <cleobuline> mforth: LOAD 'test.fth"
19:00:11 ##forth <mforth> Error: Error: LOAD: Cannot open file ''test.fth'
19:00:21 ##forth <cleobuline> mforth: LOAD "test.fth"
19:00:56 ##forth <cleobuline> mforth: LOAD "test.fth"
19:01:08 ##forth <cleobuline> mforth: CREDIT
19:01:08 ##forth <mforth> Bring to you by Cleobuline https://github.com/cleobuline/forth-bot-irc-final Site https://labynet.fr
20:07:01 ##forth <cleobuline> mforth: " un monstre affreux avec des tentacules des grandes dents et des gros yeux " IMAGE
20:07:15 ##forth <mforth> https://i.ibb.co/35CMzzFj/mforth-image-6-QJR8l.png
20:14:13 ##forth <cleobuline> mforth: LOAD "test.fth"
20:14:23 ##forth <cleobuline> mforth: HELLO
20:14:23 ##forth <mforth> Hello cleobuline How are uou ?
21:47:40 ##forth <cleobuline> c'est calme
22:02:08 ##forth <cleobuline> mforth: 200 fact
22:02:08 ##forth <mforth> Unknown word: fact
22:02:15 ##forth <veltas> Trop calme
22:02:22 ##forth <cleobuline> mforth: LOAD "test.fth
22:02:31 ##forth <cleobuline> mforth: LOAD "test.fth"
22:02:41 ##forth <cleobuline> mforth: WORDS
22:02:41 ##forth <mforth> USERNAME .S . + - * / MOD DUP DROP SWAP OVER ROT >R R> R@ = < > AND OR NOT XOR & | ^ ~ << >> CR EMIT VARIABLE @ ! +! DO LOOP I WORDS LOAD CREATE ALLOT ." CLOCK BEGIN WHILE REPEAT AGAIN SQRT UNLOOP +LOOP PICK CLEAR-STACK PRINT NUM-TO-BIN PRIME? FORGET STRING " 2DROP IMAGE TEMP-IMAGE CLEAR-STRINGS DELAY EXIT DOUBLE FACT POW FIBONACCI COUNTDOWN TUCK SUM_SQUARE CUBE SUM_CUBES RECUNACCI CAT :D PGCD
22:03:00 ##forth <cleobuline> mforth: 200 FACT
22:03:26 ##forth <cleobuline> mforth: .
22:03:26 ##forth <mforth> 788657867364790503552363213932185062295135977687173263294742533244359449963403342920304284011984623904177212138919638830257642790242637105061926624952829931113462857270763317237396988943922445621451664240254033291864131227428294853277524242407573903240321257405579568660226031904170324062351700858796178922222789623703897374720000000000000000000000000000000000000000000000000
22:14:19 ##forth <cleobuline> mforth: 300 FACT .
22:14:19 ##forth <mforth> 3060575122164406360353704612972686293885888041735769994167767412594765331767168674655152914224775733499391478887017263688642639077590031542268429279069745598412254769302719546040080122157762521768542559653569035067887252643218962642993652045764488303889097539434896254360532259807765212708224376394491201286786753683057122936819436499564604981664502277165001851765464693401122260347297240663332585835
22:20:09 ##forth <crc> cleobuline: I don't mind having bots in the channel, but would prefer if you did testing in a different channel. Random code & output tests make it harder to find and follow actual discussions.
22:20:48 ##forth <cleobuline> yes :)
22:21:23 ##forth * crc suggest using #retro-testing or #retro-interactive for this; I test some things in my bots on those channels
22:23:10 ##forth <cleobuline> i just want o know if it can handle 300 ! gracefully crc :)
22:24:17 ##forth <cleobuline> to see the limits
22:27:44 ##forth <cleobuline> i works ten hours to adjust loop constraint crc so i am proud of ir now it works gracefully
22:35:03 ##forth <crc> A few years back I wrote a server for sharing & updating blocks using a gopher-compatible protocol, and a block editor using it
22:36:02 ##forth <crc> I'll eventually be updating & expanding this for konilo compatible blocks
22:43:21 ##forth <cleobuline> :)
Generated from IRC logs • Back to Top