Day changed to 2024-09-02
[21:21] whaack: first for September!
[22:47] dorion: hey whaack, how goes ?
Day changed to 2024-09-03
[20:06] jfw: dorion: protip from the cookbook: 2 Tbsp pure cocoa powder added to a sweet-enough-already fruit based smoothie. excelente.
[21:16] dorion: jfw, ok. paulette just got some beans I can grind up.
[21:25] jfw: you just grind them straight, no fermentation or anything? I tried doing that once and they just got all moldy, never learned a proper process.
[21:26] jfw: (tried leaving them to ferment, I mean, as I'd read that's what's done)
[21:26] jfw: I recall she did something more involved for us once.
[21:46] jfw: ugh, apparently ye olde ChillingEffects changed their name to LumenDatabase and is the place to go if you wish not to find any database, but only teases of vague tidbits of information followed by bot-administered proof of stupidity should you try to click any further.
[21:47] jfw: makes sense then that it's the designated compost heap where google forwards their dmca takedown notices for public transparency & accountability and such.
[21:51] jfw: for such lulz as can be had though, the first page search results for 'rfk' cite a link taken down because 'The reported URLs are sharing a copy of my clients copyrighted material (photographs, videos) without permission' with original URL onlyfans.com and allegedly infringing URLs including the likes of 'leaknudes.com' along with... amazon s3, wordpress, and the new york times.
Day changed to 2024-09-04
[16:29] whaack: dorion: all is swell, recently bought some land here. It's ~2 hectareas of trees on a hill 15m drive from the beach, paid about $1.50 per square meter.
[16:29] whaack: how is it in Panama?
[17:35] jfw: whaack: you gonna build some treehouses now?
[17:35] jfw: does it come with utilities, any water resources?
[17:37] whaack: nope, no electricity nor water, but there is a big project being built and there's only 1 lot that separates me from that project, so getting water/electricity within 1-3 years looks promising
[17:38] whaack: jfw: how's the jaw?
[17:39] jfw: about as usual; pretty well recovered from the tooth extractions so far, just keep having to brush the stuck food out of the sockets.
[17:40] jfw: otherwise, been on the lookout for higher level expertise in treatment options
[17:42] jfw: speaking of utilities just out of reach, it looks like the ISP connection is moving forward, at least with another 'inspection' tomorrow
[18:34] jfw: (incidentally, I finally learned that a hectare is simply a square hectameter, ie 1/100 square km.)
Day changed to 2024-09-05
[19:38] jfw: http://jfxpt.com/2024/jwrd-logs-for-Sep-2024/#12430 - things are looking good here, it seems while we were waiting the provider has already got their fiber trunk to the building, or at least got the rights and the physical rope to pull it through what turns out to be a pre-existing buried duct network owned by the state (ASEP) for the neighborhood.
[19:38] sourcerer: 2024-09-04 17:42:37 (#jwrd) jfw: speaking of utilities just out of reach, it looks like the ISP connection is moving forward, at least with another 'inspection' tomorrow
[19:42] jfw: normally these guys use their own ducts but there's been a specific policy for cable burial in obarrio in the works since 2011 if I heard right.
[19:49] jfw: at least it beats the situation the other side of the train tracks, so to speak.
[19:49] sourcerer: 2024-08-19 16:55:17 (#jwrd) jfw: home network is back. the optical fiber was a lie, it's some "hybrid fiber-coax" HFCS abortion but we'll see if it holds up better than the last guys' coax.
[19:50] jfw: no trouble noticed so far from that connection though.
[19:52] jfw: who knew that being near "the center" wasn't enough, it matters which specific block you're on. real estate stuff!
Day changed to 2024-09-20
[17:11] jfw: wb cruciform
Day changed to 2024-09-26
[01:23] jfw: http://jfxpt.com/2024/jwrd-logs-for-Sep-2024/#12432 - after some excavation, not quite street but sidewalk at least, further confusing communications and another 5 days delay... the signal is finally live!
[01:23] sourcerer: 2024-09-05 19:38:39 (#jwrd) jfw: http://jfxpt.com/2024/jwrd-logs-for-Sep-2024/#12430 - things are looking good here, it seems while we were waiting the provider has already got their fiber trunk to the building, or at least got the rights and the physical rope to pull it through what turns out to be a pre-existing buried duct network owned by the state (ASEP) for the neighborhood.
[01:27] jfw: and none of the prevalent "must use our special router" bullshit either. they placed a managed switch of some nameless chinese variety to convert the fiber to copper ethernet, but it doesn't appear too uppity, I just set the public IP on my side as conveyed on the delivery document and it works. the switch even appears to have a proper serial port management interface.
[01:39] jfw: less pleasing news from the frontiers of modern-PC-architecture hell: a new AMD Ryzen build with Asus board boots to BIOS setup, and isn't locked to Secure Boot, and has a menu option to enable CSM (compatiblity support module i.e. the traditional BIOS boot path largely bypassing the UEFI nonsense), but it's grayed out, can't be set. First plausible suggestion is that some integrated GPUs no
[01:39] jfw: longer provide the VGA BIOS and so the config utility refuses to allow it unless you add a discrete graphics card.
[01:43] jfw: the boot order allows selecting "Legacy HDD" or "UEFI HDD", but even selecting Legacy, it still fails to boot the drive; no errors or anything, just reboots back into configuration.
Day changed to 2024-09-27
[17:38] jfw: the PCIe graphics card did the trick, after a rather long delay of nothing but black screens and cryptically blinking power LED. in fact, I hit it with an old enough card that once it finally woke up and put out a signal, the BIOS informed me that my card didn't support UEFI and so it had enabled the compatibility module all by itself.
[17:39] jfw: then there was further hell on the software side but that's another story, albeit related.
[19:43] dorion: http://jfxpt.com/2024/jwrd-logs-for-Sep-2024/#12446 -- ha ! win.
[19:43] sourcerer: 2024-09-27 17:38:42 (#jwrd) jfw: the PCIe graphics card did the trick, after a rather long delay of nothing but black screens and cryptically blinking power LED. in fact, I hit it with an old enough card that once it finally woke up and put out a signal, the BIOS informed me that my card didn't support UEFI and so it had enabled the compatibility module all by itself.
Day changed to 2024-09-30
[01:45] jfw: Greenspun's Tenth Rule of Programming holds that "Any sufficiently complicated C or Fortran program contains an ad-hoc, informally-specified bug-ridden slow implementation of half of Common Lisp." Case in point, GCC: here I was, belaboring under the notion that it was written in C. Come to find out, it includes [https://gcc.gnu.org/onlinedocs/gccint/Type-Information.html][a meta-compiler of sorts
[01:45] jfw: for its own code] in order to garbage collect itself between passes.
[02:10] jfw: it's been there for a while, too.
[08:36] lru: not just C or Fortran, but I've seen one python project do the same, with a small lisp interpreter written independentyly and specifically in python
[08:37] lru: maybe I should learn lisp before I accidently write it in c++
[15:22] jfw: I'm not sure there's any way around it though, from where we are today. perhaps in the 80s it had a chance to become the definitive system, but the vendors fragmented, competed against each other for pennies, and for that or whatever other reasons got left behind as the new microcomputer world went for DOS, Unix etc. Systems that look cheaper up front but lack the infrastructure that eventually
[15:22] jfw: turns out necessary, condemning everyone to pile on their own versions of whichever missing pieces
[15:24] jfw: funny about a python project going even explicitly to add on a lisp layer, seeing as python supposedly took off as the easier-to-swallow, good-enough replacement for lisp
[15:32] jfw: but in other words, it's more of a political failure, with everyone going short-sightedly to his own way, with the result that there's no commons to rely on, then some sort of irreplaceable technical magic in Lisp syntax or anything.
[15:34] jfw: much as I do like its conceptual economy and elegance.
[21:21] whaack: first for September!
[22:47] dorion: hey whaack, how goes ?
Day changed to 2024-09-03
[20:06] jfw: dorion: protip from the cookbook: 2 Tbsp pure cocoa powder added to a sweet-enough-already fruit based smoothie. excelente.
[21:16] dorion: jfw, ok. paulette just got some beans I can grind up.
[21:25] jfw: you just grind them straight, no fermentation or anything? I tried doing that once and they just got all moldy, never learned a proper process.
[21:26] jfw: (tried leaving them to ferment, I mean, as I'd read that's what's done)
[21:26] jfw: I recall she did something more involved for us once.
[21:46] jfw: ugh, apparently ye olde ChillingEffects changed their name to LumenDatabase and is the place to go if you wish not to find any database, but only teases of vague tidbits of information followed by bot-administered proof of stupidity should you try to click any further.
[21:47] jfw: makes sense then that it's the designated compost heap where google forwards their dmca takedown notices for public transparency & accountability and such.
[21:51] jfw: for such lulz as can be had though, the first page search results for 'rfk' cite a link taken down because 'The reported URLs are sharing a copy of my clients copyrighted material (photographs, videos) without permission' with original URL onlyfans.com and allegedly infringing URLs including the likes of 'leaknudes.com' along with... amazon s3, wordpress, and the new york times.
Day changed to 2024-09-04
[16:29] whaack: dorion: all is swell, recently bought some land here. It's ~2 hectareas of trees on a hill 15m drive from the beach, paid about $1.50 per square meter.
[16:29] whaack: how is it in Panama?
[17:35] jfw: whaack: you gonna build some treehouses now?
[17:35] jfw: does it come with utilities, any water resources?
[17:37] whaack: nope, no electricity nor water, but there is a big project being built and there's only 1 lot that separates me from that project, so getting water/electricity within 1-3 years looks promising
[17:38] whaack: jfw: how's the jaw?
[17:39] jfw: about as usual; pretty well recovered from the tooth extractions so far, just keep having to brush the stuck food out of the sockets.
[17:40] jfw: otherwise, been on the lookout for higher level expertise in treatment options
[17:42] jfw: speaking of utilities just out of reach, it looks like the ISP connection is moving forward, at least with another 'inspection' tomorrow
[18:34] jfw: (incidentally, I finally learned that a hectare is simply a square hectameter, ie 1/100 square km.)
Day changed to 2024-09-05
[19:38] jfw: http://jfxpt.com/2024/jwrd-logs-for-Sep-2024/#12430 - things are looking good here, it seems while we were waiting the provider has already got their fiber trunk to the building, or at least got the rights and the physical rope to pull it through what turns out to be a pre-existing buried duct network owned by the state (ASEP) for the neighborhood.
[19:38] sourcerer: 2024-09-04 17:42:37 (#jwrd) jfw: speaking of utilities just out of reach, it looks like the ISP connection is moving forward, at least with another 'inspection' tomorrow
[19:42] jfw: normally these guys use their own ducts but there's been a specific policy for cable burial in obarrio in the works since 2011 if I heard right.
[19:49] jfw: at least it beats the situation the other side of the train tracks, so to speak.
[19:49] sourcerer: 2024-08-19 16:55:17 (#jwrd) jfw: home network is back. the optical fiber was a lie, it's some "hybrid fiber-coax" HFCS abortion but we'll see if it holds up better than the last guys' coax.
[19:50] jfw: no trouble noticed so far from that connection though.
[19:52] jfw: who knew that being near "the center" wasn't enough, it matters which specific block you're on. real estate stuff!
Day changed to 2024-09-20
[17:11] jfw: wb cruciform
Day changed to 2024-09-26
[01:23] jfw: http://jfxpt.com/2024/jwrd-logs-for-Sep-2024/#12432 - after some excavation, not quite street but sidewalk at least, further confusing communications and another 5 days delay... the signal is finally live!
[01:23] sourcerer: 2024-09-05 19:38:39 (#jwrd) jfw: http://jfxpt.com/2024/jwrd-logs-for-Sep-2024/#12430 - things are looking good here, it seems while we were waiting the provider has already got their fiber trunk to the building, or at least got the rights and the physical rope to pull it through what turns out to be a pre-existing buried duct network owned by the state (ASEP) for the neighborhood.
[01:27] jfw: and none of the prevalent "must use our special router" bullshit either. they placed a managed switch of some nameless chinese variety to convert the fiber to copper ethernet, but it doesn't appear too uppity, I just set the public IP on my side as conveyed on the delivery document and it works. the switch even appears to have a proper serial port management interface.
[01:39] jfw: less pleasing news from the frontiers of modern-PC-architecture hell: a new AMD Ryzen build with Asus board boots to BIOS setup, and isn't locked to Secure Boot, and has a menu option to enable CSM (compatiblity support module i.e. the traditional BIOS boot path largely bypassing the UEFI nonsense), but it's grayed out, can't be set. First plausible suggestion is that some integrated GPUs no
[01:39] jfw: longer provide the VGA BIOS and so the config utility refuses to allow it unless you add a discrete graphics card.
[01:43] jfw: the boot order allows selecting "Legacy HDD" or "UEFI HDD", but even selecting Legacy, it still fails to boot the drive; no errors or anything, just reboots back into configuration.
Day changed to 2024-09-27
[17:38] jfw: the PCIe graphics card did the trick, after a rather long delay of nothing but black screens and cryptically blinking power LED. in fact, I hit it with an old enough card that once it finally woke up and put out a signal, the BIOS informed me that my card didn't support UEFI and so it had enabled the compatibility module all by itself.
[17:39] jfw: then there was further hell on the software side but that's another story, albeit related.
[19:43] dorion: http://jfxpt.com/2024/jwrd-logs-for-Sep-2024/#12446 -- ha ! win.
[19:43] sourcerer: 2024-09-27 17:38:42 (#jwrd) jfw: the PCIe graphics card did the trick, after a rather long delay of nothing but black screens and cryptically blinking power LED. in fact, I hit it with an old enough card that once it finally woke up and put out a signal, the BIOS informed me that my card didn't support UEFI and so it had enabled the compatibility module all by itself.
Day changed to 2024-09-30
[01:45] jfw: Greenspun's Tenth Rule of Programming holds that "Any sufficiently complicated C or Fortran program contains an ad-hoc, informally-specified bug-ridden slow implementation of half of Common Lisp." Case in point, GCC: here I was, belaboring under the notion that it was written in C. Come to find out, it includes [https://gcc.gnu.org/onlinedocs/gccint/Type-Information.html][a meta-compiler of sorts
[01:45] jfw: for its own code] in order to garbage collect itself between passes.
[02:10] jfw: it's been there for a while, too.
[08:36] lru: not just C or Fortran, but I've seen one python project do the same, with a small lisp interpreter written independentyly and specifically in python
[08:37] lru: maybe I should learn lisp before I accidently write it in c++
[15:22] jfw: I'm not sure there's any way around it though, from where we are today. perhaps in the 80s it had a chance to become the definitive system, but the vendors fragmented, competed against each other for pennies, and for that or whatever other reasons got left behind as the new microcomputer world went for DOS, Unix etc. Systems that look cheaper up front but lack the infrastructure that eventually
[15:22] jfw: turns out necessary, condemning everyone to pile on their own versions of whichever missing pieces
[15:24] jfw: funny about a python project going even explicitly to add on a lisp layer, seeing as python supposedly took off as the easier-to-swallow, good-enough replacement for lisp
[15:32] jfw: but in other words, it's more of a political failure, with everyone going short-sightedly to his own way, with the result that there's no commons to rely on, then some sort of irreplaceable technical magic in Lisp syntax or anything.
[15:34] jfw: much as I do like its conceptual economy and elegance.