2021-07-30 01:46:59 <siraben     > crc: no more bridge?
2021-07-30 03:50:34 <veltas      > I'm assuming no because you now need to authenticate with TLS, which you already do for libera.chat but couldn't blame him if it's too much effort
2021-07-30 03:50:58 <veltas      > Also thought I'd see you commenting on that fundamental theorem of algebra thread lol
2021-07-30 03:59:59 <siraben     > ahaha
2021-07-30 04:16:19 <siraben     > veltas: proof assistants come up from time to time
2021-07-30 04:16:28 <siraben     > I'm very interested in that area
2021-07-30 04:17:02 <f-a         > indeed I am not sure about forcing tls
2021-07-30 04:17:14 <f-a         > web & friends were meant to be simple
2021-07-30 04:18:06 <siraben     > f-a: welcome to new management
2021-07-30 04:19:05 <f-a         > thanks
2021-07-30 04:19:20 <f-a         > I serve my site with http and now some browser have a big scary red warning
2021-07-30 04:19:38 <f-a         > I can add https but I do not own/cannot control the certificate, since I am on shared hosting
2021-07-30 04:19:50 <f-a         > so I think I am providing a facade of security
2021-07-30 04:22:07 <siraben     > f-a: the thing is, many an unfortunate person have been victims of scam sites, and then there were secure scam sites with bad certs
2021-07-30 04:22:20 <siraben     > my guess is browsers had to put big scary warnings for that
2021-07-30 05:00:14 <crc         > siraben: freenode now requires accounts, which doesn't work for me. I briefly tried making an account for the bridge, but it just displays this: https://postimg.cc/tYFn37WD
2021-07-30 05:01:38 <siraben     > crc: what do you mean requires accounts?
2021-07-30 05:01:43 <siraben     > nickserv?
2021-07-30 05:02:36 <f-a         > lol really?
2021-07-30 05:03:07 <crc         > " Closing link: (~cbridge_@li288-125.members.linode.com) [You must use TLS/SSL and authenticate via SASL to connect to freenode please visit https://irc.com/login/sso in order to create an account. SASL Configuration: https://freenode.net/kb/answer/sasl"
2021-07-30 05:03:23 <siraben     > LOL
2021-07-30 05:04:36 <f-a         > I fail to see what they end goal is
2021-07-30 08:10:21 <veltas      > Both libera.chat and freenode require TLS (which requires an account as far as I can tell). Very awkward, I prefer dumb IRC but yes I know it's hideously insecure
2021-07-30 08:10:50 <veltas      > But outside of DMs IRC is inherently 'public' anyway
2021-07-30 08:11:17 <veltas      > Well privacy is one matter and then also it's susceptable to integrity issues
2021-07-30 08:58:25 <crc         > veltas: libera allows for plaintext connections
2021-07-30 09:17:07 <siraben     > but requiring one to visit a website to make an account for an IRC network is next level
2021-07-30 09:17:25 <siraben     > veltas: how come you stayed for a while on freenode?
2021-07-30 09:17:47 <siraben     > ah you were also here
2021-07-30 13:38:19 <veltas      > siraben: I joined libera.chat when I realised people in this channel had moved over, and at the time I had to join with TLS, I don't know if that's changed
2021-07-30 13:39:38 <veltas      > crc: ^
2021-07-30 13:40:12 <veltas      > My plain text connection was rejected anyway, and I was told to do TLS
2021-07-30 13:40:32 <crc         > veltas: some IP ranges apparently can only connect via TLS
2021-07-30 13:40:46 <siraben     > Why the TLS adversion?
2021-07-30 13:40:52 <siraben     > aversion*
2021-07-30 13:41:03 <crc         > I'm using TLS on my main connection, but not for the logger or bots at this point
2021-07-30 13:41:10 <veltas      > Because I grew up with IRC being something I could do over telnet
2021-07-30 13:41:18 <veltas      > I don't know
2021-07-30 13:41:29 <veltas      > And also it's more effort to set up in my client
2021-07-30 13:42:35 <siraben     > in ERC it's just M-x erc-tls
2021-07-30 13:42:46 <siraben     > I see
2021-07-30 13:44:29 <veltas      > Still working on my modified B language
2021-07-30 15:05:56 <lispmacs[work]> is there some FORTH technique similar to scheme's for-each?
2021-07-30 15:07:00 <lispmacs[work]> like, to replace `a foo b foo c foo d foo` where foo consumes the top of stack item
2021-07-30 15:08:25 <lispmacs[work]> In scheme it would be (for-each foo a b c d)
2021-07-30 15:09:03 <f-a         > some kind of `map`?
2021-07-30 15:09:21 <f-a         > a b c d would be on the stack?
2021-07-30 15:09:57 <lispmacs[work]> well, I'm open minded on that. maybe some compiling trick would do to
2021-07-30 15:10:17 <lispmacs[work]> e.g., something that looked like
2021-07-30 15:10:53 <lispmacs[work]> : myfunction for-each ['] foo { a b c d } ;
2021-07-30 15:11:08 <lispmacs[work]> where for-each parsed ahead i guess
2021-07-30 15:12:11 <lispmacs[work]> i suppose on the other hand, it wouldn't be too hard to write something that just took an execution context off the stack, and a number of items, and then consumed that many number of items off the stack
2021-07-30 15:12:41 <lispmacs[work]> doesn't quite seem like a clean approach
2021-07-30 15:13:13 <lispmacs[work]> anyway, I often am writing code like "PINA set-output PINB set-output PINC set-output, etc..."
2021-07-30 15:13:56 <lispmacs[work]> was wondering if there might be a more concise way
2021-07-30 15:14:57 <lispmacs[work]> some paradigm/technique for mapping a word over some values
2021-07-30 15:17:47 <lispmacs[work]> though, I think in FP if you say map you are meaning to transform the data, I just mean to feed them into the word
2021-07-30 15:17:51 <eris[m]1    > if theyre on the stack, you can build your own map pretty easily
2021-07-30 15:18:12 <eris[m]1    > for an arity 1 word
2021-07-30 15:18:37 <f-a         > I suspect you could also do «partial application» with ['] and friends
2021-07-30 15:19:06 <eris[m]1    > : map ( stack xt -- ) depth 0 do dup execute loop ;
2021-07-30 15:19:11 <eris[m]1    > should work
2021-07-30 15:19:22 <eris[m]1    > in interpret mode, ' word map
2021-07-30 15:19:34 <eris[m]1    > though this the full stack
2021-07-30 15:20:19 <eris[m]1    > personally, i'd define a
2021-07-30 15:20:19 <eris[m]1    > : mapn ( xt n -- ) 0 do dup execute loop drop ;
2021-07-30 15:20:32 <eris[m]1    > there is a need for a drop in the first, too
2021-07-30 15:20:56 <eris[m]1    > you could also use length prefixed arrays
2021-07-30 15:25:08 <eris[m]1    > its not terribly hard to write a map
2021-07-30 15:25:51 <eris[m]1    > ha, you could do a fun compile mode only onw
2021-07-30 15:26:48 <eris[m]1    > with R>
2021-07-30 15:27:07 <eris[m]1    > greatly impractical but this looks good
2021-07-30 15:31:23 <lispmacs[work]> mapn there looks like the easiest solution. the length prefixed array sounds good but I think I would need to do some coding to set up come compiling brackets that create the anonymous array
2021-07-30 15:32:34 <lispmacs[work]> so I could do : bar { a b c d } ['] foo map ;
2021-07-30 15:34:12 <lispmacs[work]> sounds quite doable but might take somebody with my level of inexperience an hour or two to figure out the create/does wording
2021-07-30 15:36:02 <eris[m]1    > i mean
2021-07-30 15:36:16 <eris[m]1    > dont need breakd
2021-07-30 15:36:25 <eris[m]1    > brackets*
2021-07-30 15:37:46 <eris[m]1    > you could just name the array, haha
2021-07-30 15:38:00 <eris[m]1    > or use a sentiel value
2021-07-30 15:38:58 <eris[m]1    > you know? i think i can do the brackets
2021-07-30 15:53:06 <lispmacs[work]> I don't want my code littered with more named arrayed. I don't know what a sentiel value is
2021-07-30 16:06:24 <veltas      > Sentinels are when you have a special number/address to represent something
2021-07-30 16:06:37 <veltas      > Like 0 is a sentinel in a null-terminated string
2021-07-30 16:07:47 <veltas      > And surprisingly(?) they often improve performance in code
2021-07-30 16:08:13 <veltas      > And can make special cases easier to handle (that's the main use)
2021-07-30 16:09:04 <veltas      > My favourite example of a sentinel: https://en.wikipedia.org/wiki/Sentinel_node
2021-07-30 16:09:29 <veltas      > Makes linked list logic simpler and faster
2021-07-30 22:53:03 <dave0       > maw