Day changed to 2023-06-01
[02:43] jfw: welcome back jwm!
[02:43] jfw: indeed it is a new server IP, though that change was a while back so I'd forgotten.
[14:40] dorion_road: http://jfxpt.com/2023/grand-reopening-of-jwrd-the-irc-channel/#comment-2394
[16:44] jfw: dorion_road: party's on!
[18:11] sstacks: jfw: That would be nice bro. Ill tell my wife so we can program that visit. It would be good to have some experienced guidance on that
[18:39] jfw: sstacks, cool. I'm not a pro baker by any means but can certainly share what I've picked up.
[21:20] sstacks: jfw: http://welshcomputing.com/paste/q7xnm8rbwp Session 11 Homework. --whaack, sstacks
[23:37] jwm: Good to be back - and glad my machine lasted in transit - it was a coin flip.
[23:38] jwm: of course i come back to a discussion on how i am poisoning myself with nasty flour as i am about to go to the local pizza joint for a beer and a slice to watch some basketball =(
[23:38] jwm: maybe you convinced me to get the wings
[23:46] jfw: ha! I wouldn't turn down a slice at a local joint; the flour snobbery comes when I look at what I'm consuming on a ~daily basis
[23:48] jfw: nothing against the wings if they're good tho
[23:51] sstacks: jfw: im with you. Id take a pizza slice anytime. Regular consumption of refined flour is where lies the real danger.
[23:51] jfw: sstacks: what sort of danger do you have in mind anyway?
[23:59] sstacks: jfw: Well, for example, when flour is subjected to industrial processes, it subtracts or even takes away the potential nutrients it could provide. We are talking about the germ and the bran. This leads to the contribution of fiber, protein, vitamins, etc. be much less (if not 0). Perhaps this is why refined flours (of any kind) also cause high blood glucose levels. It provides a cheap carbohydrate and will also have a higher caloric load
Day changed to 2023-06-02
[00:00] sstacks: jfw: sued google translate since theres some things i didnt know how to spell
[00:00] sstacks: jfw: used*, i didint sued google
[00:01] sstacks: jfw: so theres a potentially good book regarding this subject. Its called Grain Brain.
[00:08] jfw: sstacks: right, white flour has less of those things (not zero protein, though it's incomplete protein in any case ie without the full contingent of essential amino acids for humans) and is higher glycemic (raises blood sugar faster) compared to whole grain. this much I think is uncontroversial.
[00:16] jfw: however there are still "industrial process" whole wheat flours. so beyond that what comes to mind are 1) freshness of the product, as the oils in the bran & germ are more prone to oxidizing / rancidity; 2) dubious things that might be added to extend shelf life by slowing that process; 3) the government-pushed "enrichments" for "public health benefits", especially the folic acid
Day changed to 2023-06-04
[00:48] jfw: dorion_road: wiktionary broke your 'jerga panamenya' link without redirect; managed to dig it out via the deletion log: https://es.wiktionary.org/wiki/Ap%C3%A9ndice:Paname%C3%B1ismos
Day changed to 2023-06-05
[20:41] dorion_road: jfw, thanks for the heads up.
Day changed to 2023-06-06
[20:21] dorion_road: fyi, sstacks pinged me and said he'd be 15 minutes late.
[20:37] jfw: alright, I don't have time for more than 15 mins of overrun today so we'll try to fit the 90 minutes. though if whaack doesn't get the memo I guess we'll start on time.
[20:57] jfw: whaack, sstacks: http://welshcomputing.com/paste/gx5htsakwt << homework response.
[21:11] sstacks: Im here
Day changed to 2023-06-09
[22:23] dorion_road: in other "no one could've predicted, deterministic signatures leak private keys : https://www.nobsbitcoin.com/the-curious-case-of-the-half-half-bitcoin-ecdsa-nonces/
Day changed to 2023-06-10
[16:37] jfw: dorion_road: nice. "rfc6979-like constructions are toast but rfc6979 itself is totally fine, we promise!"
Day changed to 2023-06-12
[14:45] dorion: http://jfxpt.com/2023/jwrd-logs-for-May-2023/#7459 - I'm back at headquarters.
[14:45] sourcerer: 2023-05-14 06:04:29 (#jwrd) dorion: dorion_road will be my nick while I'm on the road and my road key remains the same.
[18:34] dorion: welcome Blake.
[18:39] dorion: here's an example of linking a prior line : http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7620
[18:39] sourcerer: 2023-06-12 14:45:17 (#jwrd) dorion: http://jfxpt.com/2023/jwrd-logs-for-May-2023/#7459 - I'm back at headquarters.
Day changed to 2023-06-13
[01:19] sstacks: jfw, dorion: hey guys. Tomorrow im having some upgrades on my house office. I need to unplug everything and take out the desks. Tomorrow we using the training server, or were going to use the offline/online machines?
[01:29] jfw: sstacks: tomorrow is most likely to involve the online machine and the router.
[01:35] jfw: whaack (and sstacks too if interested but this is pretty arcane), since "tar -p" didn't show up in the busybox help despite being included in my lesson, I had a look at what's up:
[01:39] jfw: first, its meaning is indeed to fully preserve permissions; the case where it makes a difference is when the indicated permissions are broader than the user's umask. for instance if the archive indicates a file with mode 777, it'll likely come out 755 instead in normal usage, like when a regular file is created (unless run by root, as a special exception made by tar itself). but with -p it'll
[01:39] jfw: preserve the indicated mode fully.
[01:40] jfw: and this applies
[01:40] jfw: gah
[01:44] jfw: pardon the cutoff there, it was hairier than I thought and needed a yet closer look...
[01:46] jfw: so, second: busybox tar as we found it *did* include some support for -p but left it undocumented and broken, with the "am I root?" check incorrectly taking priority. in the current Gales, including as seen on the training server, I'd fixed both of those issues.
[19:44] dorion: sstacks, whaack, since office hours haven't been very busy historically, we're thinking to offer a call over zoom. can just be to catch up and chat. let us know if you're interested.
[22:42] jfw_demo: hello world!
[22:42] sstacks: hello master
[22:42] jfw_demo bows
[23:12] whaack2: Dorian: that sounds great, I started using a voice dictation tool that is working pretty well. So I hope to be more active in channel. Either way I would love to do the zooms on Thursday. As I told Jacob, I cannot do this Thursday but in future weeks I should be able to
[23:14] whaack2: jfw: my block explorer is up to date on one of the mirrors. It seems the other fell behind because bitcoind crashed. I will save the debug.log file
Day changed to 2023-06-14
[00:17] whaack: !e view-height
[00:17] bitcoindexplorer: block_height: 789007
[00:17] bitcoindexplorer: mins_since_last_block: 50278
[00:20] whaack: !e view-height
[00:20] btcexplorer: block_height: 789014
[00:20] btcexplorer: mins_since_last_block: 50219
[00:20] whaack: should be sync'd in a couple of hours, bitcoind is up again
[00:21] whaack: this bot may choke on lookups of addresses with lots of txns
[00:21] whaack: but it *should* just take a while and spit back a result eventually
[00:27] jfw: whaack, does this mean you got the desktop working?
[00:30] whaack: No I did not get the desktop working but I in fact had backed up my credentials so I was able to connect from another computer
[00:31] jfw: well that's one good thing at least
[00:31] whaack: Unfortunately fixing the desktop will be a task for when I return to Costa Rica I don't have time to do it now
[00:31] jfw: currently banging my head against the Ubuntu installer; evidently it's trying to outdo Windows in every possible way. What do you mean I have to give a name, location, username & password? I'm just installing the OS, dammit, I'm not even the intended user! Next it'll be asking for birthday, social security and vaccine card I assume.
[00:35] jfw: come to think of it, it perhaps inherited this nonsense from debian. in the practical half of my first sysadmin job interview, I was asked to diagnose a known compromised machine; it had simply been ssh'ed into using the default "debian" user and password that the installer at the time forced you to create.
[00:36] jfw: http://trilema.com/2014/ubuntu-is-a-worse-piece-of-shit-than-ms-dos-ever-was/ and all
[00:37] jfw: whaack: did you get to check the cause of the crash?
[00:56] jfw: now check out this wonder, somehow this ubuntu installer ostensibly from april 2014 ("14.04.1") includes a browser first released in february 2019 ("Firefox Quantum 65.0.1").
[01:17] whaack: I am getting a connection refused air anytime I try to pipe something to nc welshcomputing.com 4
[01:17] whaack: jfw: any idea why this may be? host file is good , i can connect to welshcomputing.com/paste with links
[01:18] jfw: whaack, sounds like firewall
[01:18] jfw: we have port 4 open in the current ERL config but dunno if you have an older one, or something else
[01:26] whaack: As a work around do you know how to get text into the links browser buffer?
[01:29] whaack: jfw: I guess I am looking for something akin to xclip
[02:12] jfw: whaack: tmux can do copy & paste
[02:12] jfw: or maybe send to another machine and paste there
[02:14] jfw: or adapting http://jfxpt.com/2020/from-the-forum-log-27-29-december-2019/#footnote_1_97
[03:09] dorion: Blake, your machine is all ready to go, I'll hand it to you at tomorrow's junto.
[03:20] jfw: fwiw, I ended up following this recipe so I expect it'll prompt for a new username etc. on the first bootup.
[03:25] whaack: So I just tested the hot wallet and did a successful transaction. However when I sent the transaction, or signed it rather, I had forgot to feed the fuck goats RNG into dev/urandom. I would just like to point out that from a user experience standpoint, it seems wrong to me that you can compromise your key in this way and there is no notification to the operator.
[03:29] whaack: Another question: does Jen Key automatically call gbw-save? It seems it does, and I think it should because it would be disastrous if someone generated a key sent money to that key and then didn't type gbw-save
[03:30] dorion: whaack, did you read the warning ?
[03:32] whaack: No I have not or at least not recently, still I don't see this as part of a
[03:33] whaack: ..hardware failure.
[03:33] whaack: Anyways I have to go for now I can discuss this later but I am packing for my trip tomorrow.
[03:36] dorion: whaack, alright, bon voyage.
[03:36] jfw: whaack: I suppose your argument is basically that the linux RNG APIs are "unsafe at any speed" and their usage should be removed from cryptographic software
[03:37] jfw: well, either that or fix the kernel, you didn't exclude that option indeed.
[03:39] dorion: so Blake, getting to know and use tools like IRC and Linux and Bitcoin involves reading the manuals for your tools. while you installed hexchat, to start, let's view that strategically as a fallback option and introduce you to our yrc.
[03:40] dorion: it'll be most useful for you to run yours from your training server, which maintains a pretty much constant net connection. I run mine on a server as well.
[03:41] jfw: whaack: gbw-node gen-key does not automatically save, no, as per the usual model of editing a file in working memory and updating disk only when explicitly saved
[03:42] jfw: *gbw-signer gen-key
[03:45] dorion: Blake, the yrc manual and README will be installed on the server and in addition, thanks to jfw's codeview tool, you can also read them on the web, as I've linked.
[03:45] jfw: though I suppose it lacks the feedbacks usually associated with that, "are you sure you want to quit with unsaved changes" and such
[03:53] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7670 -- well, for the key to have spendable inputs, one would think you'd have it backed up already. or what scenario(s) are you envisioning ?
[03:53] sourcerer: 2023-06-14 03:29:14 (#jwrd) whaack: Another question: does Jen Key automatically call gbw-save? It seems it does, and I think it should because it would be disastrous if someone generated a key sent money to that key and then didn't type gbw-save
[03:55] dorion: p.s. Jen Key, lolz.
[03:56] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7677 -- now there's a good point.
[03:56] sourcerer: 2023-06-14 03:37:15 (#jwrd) jfw: well, either that or fix the kernel, you didn't exclude that option indeed.
[03:56] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7686 - speech to text; all hail the new robot overlords.
[03:56] sourcerer: 2023-06-14 03:55:57 (#jwrd) dorion: p.s. Jen Key, lolz.
[03:58] jfw: to my mind the question is, what exactly is the code supposed to do instead - what alternative is there? on each operation prompt the user for a device path? which still won't guarantee they're giving the correct path?
[03:59] dorion: jfw, eh, wut overloards ? we know he'd type it fine if his hand's weren't sore. let his hands rest as we chuckle at the dumb bot.
[04:00] jfw was merely joining in observing the bot antics.
[04:01] jfw: perhaps nobody here accused the present "AI" of being cool, but the locals do.
[04:06] dorion: jfw. yeah I get it. "local yokels" who don't grok IRC.
[13:09] sstacks: morning frens
[13:11] sstacks: reviewing the bitcoind -help, cant find a command that let me check the progress/state of my bitcoind client. Is this possible?
[15:05] dorion: sstacks, while it's running, you issue bitcoind --help ; -help only shows configuration options.
[15:06] dorion: let us know the height when you find it !
[15:16] whaack: The process of using voice to text involves editing at the end. But there are some really funny ones like jen K that I sometimes want to keep. The Jen Key typo I somehow missed. Maybe for the next few days I will keep the Errors that I don't believe affect the meaning of the message
[15:16] whaack: That way there's less typing and more LOL
[15:16] whaack: That's another funny thing about saying LOL is it always puts it in capital letters for dramatic effect I guess LOL
[15:20] whaack: jfw: I can't offer a solution regarding the interface not displaying whether or not the fuck goats is feeding the orangey. As far as I can tell the problem is just operator error and the solution is to refine my process not change the code.
[15:21] whaack: Orangey equals RNG
[16:17] dorion: whaack, LOL (typed).
[16:18] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7698 - you mean "bitcoind help", i.e. "help" is itself an rpc command.
[16:18] sourcerer: 2023-06-14 15:05:55 (#jwrd) dorion: sstacks, while it's running, you issue bitcoind --help ; -help only shows configuration options.
[16:21] dorion: haha, riiiight.
[22:21] sstacks: hey guys, just noticed i did fot answer from you guys. Checking logs atm
Day changed to 2023-06-15
[21:07] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7709 - not sure what to make of this, sstacks.
[21:07] sourcerer: 2023-06-14 22:21:36 (#jwrd) sstacks: hey guys, just noticed i did fot answer from you guys. Checking logs atm
Day changed to 2023-06-17
[20:05] Blake: test
[20:07] Blake: Guys, hi - This is Daniel, Blake's dad. Blake had to step out, I thought I'd mention that in case you were waiting for him.
[20:09] Blake: While we wait for him to return, what he was saying was:
[20:11] Blake: 1. He found paid services to help with the transcriptions, and some are cool in that they insert subtitles into the video which can also be exported as text files.
[20:14] Blake: Anyway, he kept looking for free alternatives to make his task a little easier. One option is to use the "Voice typing" feature in Google Docs, essentially have a video playing and the sound feeds into the Voice typing into a document. That would still require editing, but it would simplify the task.
[20:14] Blake: Ah, see you now R, I will let Blake continue when he returns.
[20:20] dorion: thanks daniel. yeah, no rush. looking forward to reading Blake finish the question.
[20:35] Blake: Hey, I'm back, continuing what my dad was saying, the problem is that for the text-to-speech feature to work, I will need a newer or more updated version of Firefox.
[20:36] Blake: Because the version on the computer now does not support this feature.
[20:36] Blake: So what I did was install chromium, and it turns out that it did allow speech-to-text but it does not work for some reason
[20:37] Blake: What do you guys suggest me to do?
[22:17] dorion: Blake, thanks for explaining your thought process there. the first thing I'll say is I appreciate your initiative to research tools to help you with the exercise. generally though when it comes to automation, it's best practice to do the task manually. when you do, you give yourself a baseline for what it takes on your own skin, both from a time and energy perspective and lower level insight on
[22:17] dorion: the steps in the process.
[22:22] dorion: approaching automation from this perspective allows you to avoid the costs of premature optimization. it also allows you to see which parts of the process actually need and benefit from automation.
[22:32] dorion: I appreciate your focus on the end result/deliverable of the task, i.e. written transcripts of the videos. that being said, zooming out a bit, there are a few other points to consider : a) learning computers, like anything, takes exposure. watching the videos and typing out the transcript will give you focused, quality exposure to the content. you'll still need practice and time apart from
[22:32] dorion: "transcription mode" to pick it up, but each mode builds the others.
[22:35] dorion: yeah, it takes time, , but it's an investment in yourself.
[22:37] dorion: "which is a cost" was supposed to go between the commas, lol.
[22:40] dorion: b) we shared the videos with you, but we're not making them available to the public or other 3rd parties. google isn't really our friend, so we're not really keen to have you share the materials with google or other websites.
[22:41] dorion: I looked into an open source tool myself this year, called "pocketsphinx", and the output was a jumbled mess of incomprehensibility to the point of lulz. I should actually publish that sometime.
[22:45] dorion: I realize transcribing could be somewhat boring/tedious, so what I suggest you do is to go at it in doses, e.g. 60-90 minute sessions, 1 session a day. keep track of how far you get in the video so you have a record of your efficiency.
[22:46] dorion: it may also help allow the content to sink deeper into you too.
[22:48] dorion: during the other daily time you have allocated, remember I said to look into yrc.
[22:48] sourcerer: 2023-06-14 03:39:51 (#jwrd) dorion: so Blake, getting to know and use tools like IRC and Linux and Bitcoin involves reading the manuals for your tools. while you installed hexchat, to start, let's view that strategically as a fallback option and introduce you to our yrc.
[22:49] dorion: Blake, how much time do you expect to be working on jwrd tasks while you're traveling ?
Day changed to 2023-06-18
[12:13] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7723 -- I meant, "it's best practice to do the task manually first*." lol.
[12:13] sourcerer: 2023-06-17 22:17:17 (#jwrd) dorion: Blake, thanks for explaining your thought process there. the first thing I'll say is I appreciate your initiative to research tools to help you with the exercise. generally though when it comes to automation, it's best practice to do the task manually. when you do, you give yourself a baseline for what it takes on your own skin, both from a time and energy persp
[19:00] Blake: Well, some days I expect to dedicate 2 or 3 hours to working, others maybe longer or shorter
[19:02] Blake: Ok, I understand, so basically I will manually transcribe the videos by typing in real time as I watch
[19:02] Blake: So i can capture and retain the content
[19:03] Blake: Also, I understand the propitiatory aspects of the videos so I will do as told
Day changed to 2023-06-19
[13:29] whaack: !e view-height
[13:29] btcexplorer: block_height: 794580
[13:29] btcexplorer: mins_since_last_block: 4685
[13:32] whaack: Looks like my note still struggling to think << I am leaving the speech to text puzzle
[18:22] jfw: Blake: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7716 - does this line from your dad agree with the words you would use for what you were trying to do? that is, making easier & simplifying?
[18:22] sourcerer: 2023-06-17 20:14:00 (#jwrd) Blake: Anyway, he kept looking for free alternatives to make his task a little easier. One option is to use the "Voice typing" feature in Google Docs, essentially have a video playing and the sound feeds into the Voice typing into a document. That would still require editing, but it would simplify the task.
[18:26] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7719 - how did you reach this conclusion?
[18:26] sourcerer: 2023-06-17 20:35:18 (#jwrd) Blake: Hey, I'm back, continuing what my dad was saying, the problem is that for the text-to-speech feature to work, I will need a newer or more updated version of Firefox.
[18:35] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7742 - after looking up "propitiatory" in a couple sources I can't make sense of what you're saying there; can you try rephrasing please?
[18:35] sourcerer: 2023-06-18 19:03:52 (#jwrd) Blake: Also, I understand the propitiatory aspects of the videos so I will do as told
[18:37] jfw: note that there are software and hardware approaches to streamlining even the manual transcription process which might be worth a look.
[18:40] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7746 - ha, that one's clearly for Blake, as a taste of what the finest in STT tools are going to leave him even under their ideal circumstances!
[18:40] sourcerer: 2023-06-19 13:32:22 (#jwrd) whaack: Looks like my note still struggling to think << I am leaving the speech to text puzzle
Day changed to 2023-06-20
[17:28] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7739 -- alright, sounds good.
[17:28] sourcerer: 2023-06-18 19:00:10 (#jwrd) Blake: Well, some days I expect to dedicate 2 or 3 hours to working, others maybe longer or shorter
[17:28] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7741 -- cool.
[17:28] sourcerer: 2023-06-18 19:02:52 (#jwrd) Blake: So i can capture and retain the content
[17:29] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7751 -- I'd guess he means proprietary, but I'll let him clarify.
[17:29] sourcerer: 2023-06-19 18:35:34 (#jwrd) jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7742 - after looking up "propitiatory" in a couple sources I can't make sense of what you're saying there; can you try rephrasing please?
[20:45] whaack: !e view-height
[20:45] btcexplorer: block_height: 794667
[20:45] btcexplorer: mins_since_last_block: 5654
[20:52] sstacks: jfw: sorry to ask. Im having trouble connecting thru yrc with my thinkpad
[20:53] whaack: Hi Blake
[20:53] sstacks: jfw: "Error: Mode to unknown target: :sstacksyrc! xxxxxxxx MODE sstacksyrc :+i
[20:53] sstacks: this output is from yrc
[20:54] whaack: The best SST I have used is the won with the iPhone. The one I am using now is the Mack OS native SST. I am not sure why this one is a little worse but I think it may just be because the microphone is not as good on the Mac computer
[20:57] jfw: sstacks: that's a harmless error, it means the server sent something the client didn't understand but in this case it's unimportant
[20:58] jfw: at least that's how it reads to me on first glance, though it'd be nice to check on why the target is unknown.
[21:00] sstacksyrc: hello
[21:01] jfw: ahoy sstacksyrc, you made it!
[21:01] sstacksyrc: had some good backup
Day changed to 2023-06-21
[01:28] whaack: !e view-height
[01:28] btcexplorer: block_height: 794743
[01:28] btcexplorer: mins_since_last_block: 5181
[13:45] whaack: !e view-height
[13:45] btcexplorer: block_height: 794794
[13:45] btcexplorer: mins_since_last_block: 5455
[13:46] whaack: It seems that the notice thinking at a rate that is so slow that it never makes enough progress to get caught up with the tip.
[13:48] whaack: I have a more beefy server running at 103.6.212.28 that is available for use. Just type that IP into your browser in order to access the service
[13:49] whaack: I will try to get the IRC bot running on that server
[14:21] dorion: whaack, any idea why it's struggling to sync to the tip ? is this on ssd or spinning platters ? how many peers do you have ? are you getting flooded w/ bastards ?
[14:23] dorion: sometimes when I'm behind, I'll restart to node w/ connect=$ipoftrustednode and to simplify with one connection until I'm at the tip. then I'll restart again w/ a list of addnode= in the config.
[14:35] dorion: whaack, sstacks, Blake, jfw, etc. will tomorrow at 1900 utc work for everyone for the office hours call ?
[14:35] dorion: whaack, please loop atlas in too.
[14:37] sstacks: dorion: this is 2pm Panama time. Ill be having problems with this time and even with the 4pm time. I have a vet's appointment at 3pm.
[14:37] dorion: whaack, I think he connected at one point, but haven't seen him in a while.
[14:37] sourcerer: 2023-05-24 03:28:56 (#jwrd) dorion_road: welcome barbarian.
[14:38] dorion: sstacks, alright. could you do earlier ? say 1pm Panama time ?
[14:39] sstacks: dorion: Yes! Im sorry for inconvenience.
[14:40] dorion: does 1800 utc/1300 panama time work for everyone else then ?
[15:51] jfw: dorion: works for me.
[22:49] whaack: I cannot do that time. I am busy between 1630 UTC and 22 00 UTC. Any other time should work. I may be able to connect at 18 UTC but I will be commuting on a train and only able to talk for maximum one hour
[22:49] whaack: I want to somehow make this work. Is it possible for others to do 10:30 AM Panama time?
Day changed to 2023-06-22
[01:11] jfw: 10:30am Panama is ok for me too, but I begin to wonder if there's something more generally wrong with the usual 4pm slot since something always seems to be coming up for someone.
[01:50] dorion: I have a meeting at 11am tomorrow, will need to be afk by 1030ish :-/
[01:55] jfw: how about the usual 4pm but on friday?
[12:06] dorion: jfw, that'll work for me.
[14:08] whaack2: That time works for me as well
[14:09] whaack2: Dorian: I have not been able to look into why the sink is so slow. I may try your restart method only connected to trusted peers later today
[14:14] whaack2: I pinged Atlas on other communication channels. Unfortunately, it seems shitcoiners have stolen his time with promises of large pots of gold that are supposed to arrive very quickly.
[15:01] dorion: whaack2, alright.
[15:41] jfw: whaack: well at least "large pots of gold arriving quickly" is a bet that will play out soon enough. hopefully the returns are measured against btc too.
[15:44] jfw: at first glance the current machine learning research looked like quite a froth, that the inquisitive but unguided mind could easily burn inordinate amounts of time trying to get on top of
[15:49] jfw: (then add 'blockchain' and easy money to the mix for maximum shiny)
[16:20] whaack: !e view-height
[16:20] btcexplorer: block_height: 795211
[16:20] btcexplorer: mins_since_last_block: 2788
[16:54] whaack: !e2 view-height
[16:54] btcexplorer: whaack: my valid commands are: src, uptime, version, help, view-height, view-address, view-utxos, view-balance, view-block, view-raw-block, view-tx, view-raw-tx, push
[16:54] btcexplorer2: block_height: 795466
[16:54] btcexplorer2: mins_since_last_block: 6
[16:54] jfw: lolz
[16:54] whaack: lol will fix
[16:55] whaack: !nze view-height
[16:55] nzbtcexplorer: block_height: 795466
[16:55] nzbtcexplorer: mins_since_last_block: 7
[16:56] whaack: nz = New Zealand
[16:56] whaack: gotta run for now
[16:59] jfw: the republican bots used single-char callsigns, fwiw
Day changed to 2023-06-23
[01:12] whaack: !E view-height
[01:13] whaack: !E view-height
[01:13] nzbtcexplorer: block_height: 795517
[01:13] nzbtcexplorer: mins_since_last_block: 1
[01:13] whaack: !e view-height
[01:13] btcexplorer: block_height: 795276
[01:13] btcexplorer: mins_since_last_block: 2679
[01:14] whaack: jfw: updated to match spec
[01:15] whaack: There are still more things to do in order to get it to spec. For example there is no way atm to send a private message for help
[03:01] Barbarian_: Hello
[03:10] Barbarian_: So glad to be remembered, I would be terribly pleased to be a part of the call tomorrow at 4PM. Regarding the chitchat about the "Big shiny" it would be best if we schedule a seperate call to discuss this project.
[13:51] whaack: Good to see you in chat, barbarian. I'm not sure if the meeting today is confirmed, sstacks do you plan to come?
[13:59] whaack: Also barbarian, i think talking about the 'big shiny' is best discussed on irc. This way the conversation is logged and can be reviewed and commented on by the participants and anyone else. It's also asynchronous so people can respond when they have free time instead of having to take a block out of their day.
[18:15] Barbarian_: Hello all, looking forward to the chat this afternoon. Going forward there will be no discussion regarding the "Big Shiny" as to not detract from the very important work we are doing here.
[19:09] dorion: sstacks can't make it, but I think we should go ahead.
[19:54] Barbarian_: So where will this call be hosted?
[20:02] dorion: Barbarian, on zoom.
[20:03] Barbarian_: Okay
[20:03] Barbarian_: let me quickly set up an account
[20:39] jfw: barbarian: afaik an "account" isn't necessary, you can just connect using the meeting ID + passcode like last time. it can be helpful to pre-install the software though; the version I use is available at http://welshcomputing.com/files/zoom/
[20:40] Barbarian: Okay just connceting now
[20:41] Barbarian: Connected
[20:43] jfw: well we won't be starting for another 20 minutes or so, but I expect you can just leave it there.
[20:43] Barbarian: Okay
[20:44] whaack: !e view-height
[20:44] btcexplorer: block_height: 795576
[20:44] btcexplorer: mins_since_last_block: 479
[20:44] whaack: much progress
[20:45] whaack: Great to have you joining today Atlas
[20:45] Barbarian: Glad to be joining myself
[20:46] Barbarian: !e view-height
[20:46] btcexplorer: block_height: 795576
[20:46] btcexplorer: mins_since_last_block: 481
[20:46] Barbarian: Cool that you have a block explorer integrated into the IRC.
[20:46] Barbarian: What are some of the commands?
[20:47] whaack: !e help
[20:47] btcexplorer: whaack: my valid commands are: src, uptime, version, help, view-height, view-address, view-utxos, view-balance, view-block, view-raw-block, view-tx, view-raw-tx, push
[20:47] whaack: ^^
[20:47] whaack: Try one.
[20:48] Barbarian: nice
[20:48] Barbarian: !e view-address 1As8fqoyZam1G5kLqKd4AW5pNMFN35N8BS
[20:48] btcexplorer: http://paste.deedbot.org/?id=-wMN 1 of 1
[20:49] whaack: This block explore was built on top of jay FW's gbw-node
[20:49] Barbarian: !e uptime
[20:49] btcexplorer: Barbarian: time since my last reconnect : 4d 7h 19m
[20:49] whaack: jfw*
[20:49] Barbarian: !e uptime jfw
[20:49] btcexplorer: Barbarian: time since my last reconnect : 4d 7h 19m
[20:49] Barbarian: Cool
[20:50] Barbarian: So how did you code this?
[20:50] Barbarian: I would love to know more about how it works.
[20:50] dorion: !e src
[20:50] btcexplorer: dorion: my source code can be seen at: http://ztkfg.com/2020/07/a-bitcoin-block-explorer-the-why-the-how
[20:52] Barbarian: interesting
[20:54] Barbarian: !e version
[20:54] btcexplorer: I am 'trbexplorer' version 630877.
[20:54] whaack: I'm excited to start blogging again. I'll have to do my first STT assisted article
[20:54] whaack: That version number is meaningless. I should fix it
[20:55] Barbarian: nice, I've heard that speech2text tech is improving daily
[20:55] whaack: Maybe it is. But it still a painful experience. I won't correct these sentences so that you can see the types of errors it makes. Mind you I am also speaking in a slow and unnatural manner to make it easier for the computer to understand me
[20:56] whaack: But you can also see that it is pretty impressive. It certainly is helping me out a lot
[20:56] Barbarian: Yeah
[20:57] Barbarian: Which one are you using now?
[20:57] whaack: I am using Apple's built-in speech to text for Mac OS 10.16
[20:58] whaack: Sorry, 10.13
[20:58] Barbarian: Okay
[20:59] whaack: Unfortunately it was too much of a hassle to transport my microphone. It may work better if I got good external mic
[20:59] Barbarian: Certainly.
[21:00] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7831 - I don't think "full compliance" or anything is essential right now, fwiw; we can adapt it to our needs if and when the time comes. that spec is best which specifies least, or at least doesn't prematurely overspecify.
[21:00] sourcerer: 2023-06-23 01:15:56 (#jwrd) whaack: There are still more things to do in order to get it to spec. For example there is no way atm to send a private message for help
[22:00] Barbarian: https://twitter.com/shinohai2017
[22:02] Barbarian: https://twitter.com/FacetSir
[22:02] Barbarian: https://twitter.com/DreadBong0
[22:30] whaack: Thanks for coming barbarian. You should hang out an this channel and get working on some cool project. Also you may want to start a blog. It provides you a way to analyze your own thoughts among a million other benefits.
[22:47] Barbarian: Maybe
[23:35] Barbarian: I will certainly be in IRC more, just maybe about the blog.
Day changed to 2023-06-24
[14:52] whaack: !e view–height
[14:53] whaack: hm, btcexplorer seems to have died last night. How sad
[14:53] whaack: !E view–height
[14:53] nzbtcexplorer: whaack: my valid commands are: src, uptime, version, help, view-height, view-address, view-utxos, view-balance, view-block, view-raw-block, view-tx, view-raw-tx, push
[14:53] whaack: !E view-height
[14:54] nzbtcexplorer: block_height: 795727
[14:54] nzbtcexplorer: mins_since_last_block: 10
[14:58] whaack: !e view-height
[14:58] btcexplorer: block_height: 795653
[14:58] btcexplorer: mins_since_last_block: 719
[15:28] dorion: Barbarian, ever read : http://trilema.com/2014/a-conceit-or-the-importance-of-blogging/ ?
[16:29] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7893 - this came up from someone mentioning shinohai as a sort of shitcoin sommelier. it looks to be the guy
[16:29] sourcerer: 2023-06-23 22:00:21 (#jwrd) Barbarian: https://twitter.com/shinohai2017
[16:39] jfw: barbarian: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7898 - perhaps as an easier question to start with, do you do much writing at all, whether for other venues or just for yourself?
[16:39] sourcerer: 2023-06-23 23:35:42 (#jwrd) Barbarian: I will certainly be in IRC more, just maybe about the blog.
[16:41] jfw: I recall at high school age I was resentfully slogging through school assigned essays with no patience remaining to write for myself, though I certainly could have and quite likely would have benefitted
[16:46] jfw: !E view-height
[16:46] nzbtcexplorer: block_height: 795739
[16:46] nzbtcexplorer: mins_since_last_block: 6
[16:47] jfw: whaack: btcexplorer and nzbtcexplorer are added to sourcerer's bots list so their output is dimmed in the web log view.
[19:40] Barbarian: jfw, thanks for the advice. I will check out that trilema article on a bit. Right now I'm a bit busy.
[19:40] Barbarian: *in
[20:00] jfw: I wasn't aware of having given any advice per se, heh.
[22:07] whaack: Jay FW: it looks like 1.deep bot.org is down. paste. Deed bot.org is a dependency of PTC explore are. I may switch to your paid service. Taste service. Aced service. Paste Service
[22:08] whaack: I left in the speech to text errors there cause they were quite hilarious.
[22:57] jfw: whaack: the errors quite recall the experience of trying to type with pnoje onscreen keyboards with the various swiping & predictive assistance modes. "so fast!!"
[23:00] jfw: yes, unless you're maintaining relations with trinque and can expect things to get things like that fixed timely (which MP et al could not on various occasions) it would make sense to look for alternatives, and you're welcome to use mine.
[23:00] jfw: *expect to get things
[23:04] jfw: if you use the web submission gateway it should be a drop-in replacement, or if you use the raw tcp mode it shouldn't need any web libraries at all.
[23:07] jfw: I call it "gateway" because it's literally just a php script that receives a POST then forwards it to the same tcp service.
Day changed to 2023-06-25
[15:12] whaack: !e view-height
[15:12] btcexplorer: block_height: 795870
[15:12] btcexplorer: mins_since_last_block: -9
[15:13] whaack: Not only did we sink, but we got to the future!
[22:43] jfw: ahoy blake, how are travels going?
[22:44] Blake: Hey, everything's going well over here, spending time with my grandma and dedicating a couple hours a day to the tasks at hand. How are you guys?
[22:46] jfw: doing alright here
[22:46] jfw: I heard you had some troubles with irc connectivity?
[22:49] dorion: heya, Blake. all good here.
[22:56] jfw: Blake: I'm glad to hear all is well and you got some work time in. It looks like you're not at the keyboard now so we can continue the conversation some other time.
[23:07] Blake: Sorry,I was finishing up the video, it's all done now. I'm glad everything is good over there.
[23:08] Blake: Yes Jacob, the problem is that the device will not connect to the internet / wifi at my grandma's residence, so I can only connect when I am "home".
[23:13] dorion: Blake, when do you expect to be able to turn in the transcript for the first video ?
[23:15] Blake: Now, I finished it 10min ago
[23:18] dorion: nice. what kind of document did you write it in ?
[23:18] Blake: Libre Office Writer
[23:19] Blake: How do I send it to you?
[23:21] dorion: alright, email it to me.
[23:22] Blake: Ok, what's your email?
[23:22] Blake: I'll do it in a while, I'm going to the gym
[23:44] whaack: blake: thanks for transcribing. I'm curious to see what the class looks like in text format. I guess I'm assuming hear that the transcriptions are going to be made available to us. Is that true dorian? Also, Blake did you transcribe our lesson or the first class of a different group?
Day changed to 2023-06-26
[00:57] dorion: Blake, check your pm.
[01:06] jfw: Blake, did you notice you missed some responses & questions from last week?
[01:07] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7940 - what "device" do you mean? (and for any helpful bystanders, I'm asking him specifically, no need to guess.)
[01:07] sourcerer: 2023-06-25 23:08:21 (#jwrd) Blake: Yes Jacob, the problem is that the device will not connect to the internet / wifi at my grandma's residence, so I can only connect when I am "home".
[04:41] jfw: http://jfxpt.com/2023/jwrd-dovecot-initial-release-aka-version-240/ finally!
[14:34] dorion: jfw, fuckin' sweet, conyo.
[14:36] dorion: Blake, on first pass of your work, for your first time and on a relatively abstract lesson, you did an outstanding job. It was a pleasure to read.
[14:38] dorion: thank god it's monday, good morning to all ((except any socialist who might be reading the log at some point. FU. obviously)).
[14:52] dorion: jfw linked this classic in another channel and upon rereading this morning, I'm sharing here. it's well worth the read for everyone.
[15:49] jfw: good morning dorion, you're sounding cheerful today.
[15:50] jfw: dorion: "conyo" ??
[16:15] dorion: jfw, ny for n with ~ hat.
[16:16] dorion: Blake, you mentioned the transcription took you longer than you expected, how long did it take you actually ?
[17:31] whaack: hm..nzexplorer disconnected now
[17:33] jfw: whaack: indeed, of its own accord apparently
[17:35] whaack: BTC explorer disconnected after being up for about one to 2 days, same for NZ Explorer. So it looks like there may be a problem with the irc component of the bot. First step may be to check the reconnect logic.
[17:36] whaack: Congrats Jeff W on Dove caught. I haven't looked at the article in detail but it looks like you have" been a busy boy" again
[17:36] jfw: dorion: as in, "con~o m (fam) Vulva." ? I still dun geddit
[17:38] jfw: whaack: well the six months between the last patch / release timestamp and article chafes a bit but yeah. -Jeff W
[17:40] whaack: Jay FW: the way that I think he's using the phrase conyo the meaning what approximate to "wow" similar to the way English speakers may say "damn" to emphasize being impressed
[17:42] whaack: The man has many names exclamation Point
[17:43] whaack: I say! All the time and this time it Decides to turn into two words. I can't understand this program.
[17:49] dorion: jfw, talk to more people in spanish and you'll get it, but whaack has it, it adds emphasis.
[17:49] jfw: I did check the jerga panamenya file too, fwiw.
[17:50] dorion: whaack, does your bot keep a log ? anything interesting there ?
[17:51] dorion: jfw, their equivalent is cucha. tbf, I've heard it most from venezuelanas.
[17:52] jfw: oh, chucha, why didn't you just say so!! lolz
[17:52] jfw: yeah haven't hung out much with vzla/os yet.
[20:38] whaack: dorion: it keep a log I didn't notice anything interesting there
[20:45] whaack: !e view-height
[20:45] btcexplorer: block_height: 796057
[20:45] btcexplorer: mins_since_last_block: 0
[20:45] whaack: !E view-height
[20:45] nzbtcexplorer: block_height: 796057
[20:45] nzbtcexplorer: mins_since_last_block: 16
Day changed to 2023-06-27
[12:05] dorion: buenos dias a todos.
[12:07] dorion: Blake, the next task for you is to establish an ssh key which we'll use to provide you server access. in the group 8 directory, there's an orientation file that has ssh instructions. follow the steps under the macosx header on your Linux.
[13:34] whaack: morning gents
[13:47] whaack: Barbarian: why don't you get started on some project? For example, you could try setting up a gpg key. Or installing gales bitcoin wallet.
[16:35] jfw: creating a gpg key, while not that big of a project in itself, is foundational for sure.
[16:39] dorion: whaack, good question and pointers. Barbarian, note for the gbw-node side of gbw, you'll need a local bitcoind.
[16:41] dorion: yrc would also be a good entry point. fundamental development there will involve adapting it to speak the eulora2 comms protocol.
[16:41] sourcerer: 2023-06-14 03:39:51 (#jwrd) dorion: so Blake, getting to know and use tools like IRC and Linux and Bitcoin involves reading the manuals for your tools. while you installed hexchat, to start, let's view that strategically as a fallback option and introduce you to our yrc.
[16:43] jfw: I forget, does Barbarian have a linux box or his own computer at all?
[16:45] dorion: we're working to make eulora2 our primary means of chat because it's superior to IRC in many ways. in the shortrun we'll maintain IRC as a fallback, but as we develop eulora2, IRC will become increasingly less relevant.
[16:47] dorion: in the wider lens there, once yrc speaks e2, it could be developed further to be a full text-based client for the "game-game".
[16:48] dorion: jfw, i dunno. i'd assume he at least has a laptop of his own, but will let him clarify.
[16:51] dorion: Blake, for the next transcription, use nano instead of libreoffice. nano is terminal based and reads/writes plain text files. to open it, open a terminal and type "nano" and hit enter.
[16:55] dorion: that will open the program. at the bottom, you'll see a menu. the '^' character means the CRTL button and the 'M' character means Meta or alt. go ahead and explore the menu and practice saving, exiting and reopening some test files. you can also issue at a terminal "man nano" for its manual page and "man --help" for a summarized help.
[17:01] dorion: Blake, in ubuntu, to restart the networking services/interfaces you can : 1) open a terminal ; 2) issue : $ sudo service network-manager restart
[17:03] dorion: in your case, we'll see if that does anything to solve your wifi connection issues. more generally, this can be used when you want to apply networking changes from configuration files, such as /etc/hosts
[18:49] jfw: dorion, am I reading half of a conversation with blake here? or how did we get to restarting network-manager
[18:54] jfw: "nano --help" I assume you mean
[18:56] dorion: jfw, right. thanks.
[18:56] dorion: jfw, yeah, it's a half conversation, he's stuck in the swamps because laptop isn't connecting to the network he's on.
[19:01] jfw: does ubuntu really interpose the networkmanager crap on top of the hosts file? not that I'm against shooting the stinking thing in the head at every opportunity but I didn't know it had got its tentacles quite that deep
[19:04] dorion: yeah, I've changed an ip in /etc/hosts and the browser didn't know about the change until I restarted the networking. barbaric, but is what it is.
[19:05] jfw: hm, possibly that's the browser caching the file itself and it just happens to be triggered to refresh that by seeing the interface go down.
[19:07] jfw: sanely speaking there's nothing required to "apply" a change to the hosts file besides saving it. but sanity is understood to be excluded once browsers get involved.
[19:56] jfw: dorion: I'll second whaack's question on what you intend to do with the transcripts. far as I'm concerned we should post them for the class.
[19:56] sourcerer: 2023-06-25 23:44:18 (#jwrd) whaack: blake: thanks for transcribing. I'm curious to see what the class looks like in text format. I guess I'm assuming hear that the transcriptions are going to be made available to us. Is that true dorian? Also, Blake did you transcribe our lesson or the first class of a different group?
[23:11] jfw: whaack: on your question of why do you need a route for the local subnet/link if the default route seems to cover it anyway, here's the linux kernel's response to the attempt to create a default route through a gateway not included in any directly connected address range:
[23:12] jfw: # route add default gw 10.9.1.1 dev eth0
[23:13] jfw: route: ioctl 0x890b failed: Network unreachable
[23:15] jfw: (I get this still doesn't quite address if/why it has to be that way.)
[23:20] jfw: I suppose you could look at it as a sanity check - it won't accept a gateway address that it doesn't have a way to reach through one of its direct links, and it's not going to add a special case for "but what if the gateway is actually included in the route that I'm now adding". that would seem quite circular to me.
Day changed to 2023-06-29
[21:02] jfw: sstacks, whaack: I'm here for the office hours if anyone needs it.
[21:31] whaack: jfw: just saw this now. i am also online but unfortunately dealing with the painful task of renewing Government documents
[21:32] whaack: While I am here I am renewing my get out of jail permission slip
[21:45] jfw: whaack: heh, I didn't know they made those at least for us non-Clintons
[21:46] jfw: but if you mean drivers' license then yeah, less painful to renew than to reinstate later if it expires.
[21:46] whaack: I'm referring to my passport LOL
[21:46] jfw: aok
[21:47] whaack: Off to take the photo will be back later
[21:47] jfw: dorion & I both had that renewed while in panama, fwiw.
[21:48] jfw: I get the "get out of jail" part now.
[02:43] jfw: welcome back jwm!
[02:43] jfw: indeed it is a new server IP, though that change was a while back so I'd forgotten.
[14:40] dorion_road: http://jfxpt.com/2023/grand-reopening-of-jwrd-the-irc-channel/#comment-2394
[16:44] jfw: dorion_road: party's on!
[18:11] sstacks: jfw: That would be nice bro. Ill tell my wife so we can program that visit. It would be good to have some experienced guidance on that
[18:39] jfw: sstacks, cool. I'm not a pro baker by any means but can certainly share what I've picked up.
[21:20] sstacks: jfw: http://welshcomputing.com/paste/q7xnm8rbwp Session 11 Homework. --whaack, sstacks
[23:37] jwm: Good to be back - and glad my machine lasted in transit - it was a coin flip.
[23:38] jwm: of course i come back to a discussion on how i am poisoning myself with nasty flour as i am about to go to the local pizza joint for a beer and a slice to watch some basketball =(
[23:38] jwm: maybe you convinced me to get the wings
[23:46] jfw: ha! I wouldn't turn down a slice at a local joint; the flour snobbery comes when I look at what I'm consuming on a ~daily basis
[23:48] jfw: nothing against the wings if they're good tho
[23:51] sstacks: jfw: im with you. Id take a pizza slice anytime. Regular consumption of refined flour is where lies the real danger.
[23:51] jfw: sstacks: what sort of danger do you have in mind anyway?
[23:59] sstacks: jfw: Well, for example, when flour is subjected to industrial processes, it subtracts or even takes away the potential nutrients it could provide. We are talking about the germ and the bran. This leads to the contribution of fiber, protein, vitamins, etc. be much less (if not 0). Perhaps this is why refined flours (of any kind) also cause high blood glucose levels. It provides a cheap carbohydrate and will also have a higher caloric load
Day changed to 2023-06-02
[00:00] sstacks: jfw: sued google translate since theres some things i didnt know how to spell
[00:00] sstacks: jfw: used*, i didint sued google
[00:01] sstacks: jfw: so theres a potentially good book regarding this subject. Its called Grain Brain.
[00:08] jfw: sstacks: right, white flour has less of those things (not zero protein, though it's incomplete protein in any case ie without the full contingent of essential amino acids for humans) and is higher glycemic (raises blood sugar faster) compared to whole grain. this much I think is uncontroversial.
[00:16] jfw: however there are still "industrial process" whole wheat flours. so beyond that what comes to mind are 1) freshness of the product, as the oils in the bran & germ are more prone to oxidizing / rancidity; 2) dubious things that might be added to extend shelf life by slowing that process; 3) the government-pushed "enrichments" for "public health benefits", especially the folic acid
Day changed to 2023-06-04
[00:48] jfw: dorion_road: wiktionary broke your 'jerga panamenya' link without redirect; managed to dig it out via the deletion log: https://es.wiktionary.org/wiki/Ap%C3%A9ndice:Paname%C3%B1ismos
Day changed to 2023-06-05
[20:41] dorion_road: jfw, thanks for the heads up.
Day changed to 2023-06-06
[20:21] dorion_road: fyi, sstacks pinged me and said he'd be 15 minutes late.
[20:37] jfw: alright, I don't have time for more than 15 mins of overrun today so we'll try to fit the 90 minutes. though if whaack doesn't get the memo I guess we'll start on time.
[20:57] jfw: whaack, sstacks: http://welshcomputing.com/paste/gx5htsakwt << homework response.
[21:11] sstacks: Im here
Day changed to 2023-06-09
[22:23] dorion_road: in other "no one could've predicted, deterministic signatures leak private keys : https://www.nobsbitcoin.com/the-curious-case-of-the-half-half-bitcoin-ecdsa-nonces/
Day changed to 2023-06-10
[16:37] jfw: dorion_road: nice. "rfc6979-like constructions are toast but rfc6979 itself is totally fine, we promise!"
Day changed to 2023-06-12
[14:45] dorion: http://jfxpt.com/2023/jwrd-logs-for-May-2023/#7459 - I'm back at headquarters.
[14:45] sourcerer: 2023-05-14 06:04:29 (#jwrd) dorion: dorion_road will be my nick while I'm on the road and my road key remains the same.
[18:34] dorion: welcome Blake.
[18:39] dorion: here's an example of linking a prior line : http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7620
[18:39] sourcerer: 2023-06-12 14:45:17 (#jwrd) dorion: http://jfxpt.com/2023/jwrd-logs-for-May-2023/#7459 - I'm back at headquarters.
Day changed to 2023-06-13
[01:19] sstacks: jfw, dorion: hey guys. Tomorrow im having some upgrades on my house office. I need to unplug everything and take out the desks. Tomorrow we using the training server, or were going to use the offline/online machines?
[01:29] jfw: sstacks: tomorrow is most likely to involve the online machine and the router.
[01:35] jfw: whaack (and sstacks too if interested but this is pretty arcane), since "tar -p" didn't show up in the busybox help despite being included in my lesson, I had a look at what's up:
[01:39] jfw: first, its meaning is indeed to fully preserve permissions; the case where it makes a difference is when the indicated permissions are broader than the user's umask. for instance if the archive indicates a file with mode 777, it'll likely come out 755 instead in normal usage, like when a regular file is created (unless run by root, as a special exception made by tar itself). but with -p it'll
[01:39] jfw: preserve the indicated mode fully.
[01:40] jfw: and this applies
[01:40] jfw: gah
[01:44] jfw: pardon the cutoff there, it was hairier than I thought and needed a yet closer look...
[01:46] jfw: so, second: busybox tar as we found it *did* include some support for -p but left it undocumented and broken, with the "am I root?" check incorrectly taking priority. in the current Gales, including as seen on the training server, I'd fixed both of those issues.
[19:44] dorion: sstacks, whaack, since office hours haven't been very busy historically, we're thinking to offer a call over zoom. can just be to catch up and chat. let us know if you're interested.
[22:42] jfw_demo: hello world!
[22:42] sstacks: hello master
[22:42] jfw_demo bows
[23:12] whaack2: Dorian: that sounds great, I started using a voice dictation tool that is working pretty well. So I hope to be more active in channel. Either way I would love to do the zooms on Thursday. As I told Jacob, I cannot do this Thursday but in future weeks I should be able to
[23:14] whaack2: jfw: my block explorer is up to date on one of the mirrors. It seems the other fell behind because bitcoind crashed. I will save the debug.log file
Day changed to 2023-06-14
[00:17] whaack: !e view-height
[00:17] bitcoindexplorer: block_height: 789007
[00:17] bitcoindexplorer: mins_since_last_block: 50278
[00:20] whaack: !e view-height
[00:20] btcexplorer: block_height: 789014
[00:20] btcexplorer: mins_since_last_block: 50219
[00:20] whaack: should be sync'd in a couple of hours, bitcoind is up again
[00:21] whaack: this bot may choke on lookups of addresses with lots of txns
[00:21] whaack: but it *should* just take a while and spit back a result eventually
[00:27] jfw: whaack, does this mean you got the desktop working?
[00:30] whaack: No I did not get the desktop working but I in fact had backed up my credentials so I was able to connect from another computer
[00:31] jfw: well that's one good thing at least
[00:31] whaack: Unfortunately fixing the desktop will be a task for when I return to Costa Rica I don't have time to do it now
[00:31] jfw: currently banging my head against the Ubuntu installer; evidently it's trying to outdo Windows in every possible way. What do you mean I have to give a name, location, username & password? I'm just installing the OS, dammit, I'm not even the intended user! Next it'll be asking for birthday, social security and vaccine card I assume.
[00:35] jfw: come to think of it, it perhaps inherited this nonsense from debian. in the practical half of my first sysadmin job interview, I was asked to diagnose a known compromised machine; it had simply been ssh'ed into using the default "debian" user and password that the installer at the time forced you to create.
[00:36] jfw: http://trilema.com/2014/ubuntu-is-a-worse-piece-of-shit-than-ms-dos-ever-was/ and all
[00:37] jfw: whaack: did you get to check the cause of the crash?
[00:56] jfw: now check out this wonder, somehow this ubuntu installer ostensibly from april 2014 ("14.04.1") includes a browser first released in february 2019 ("Firefox Quantum 65.0.1").
[01:17] whaack: I am getting a connection refused air anytime I try to pipe something to nc welshcomputing.com 4
[01:17] whaack: jfw: any idea why this may be? host file is good , i can connect to welshcomputing.com/paste with links
[01:18] jfw: whaack, sounds like firewall
[01:18] jfw: we have port 4 open in the current ERL config but dunno if you have an older one, or something else
[01:26] whaack: As a work around do you know how to get text into the links browser buffer?
[01:29] whaack: jfw: I guess I am looking for something akin to xclip
[02:12] jfw: whaack: tmux can do copy & paste
[02:12] jfw: or maybe send to another machine and paste there
[02:14] jfw: or adapting http://jfxpt.com/2020/from-the-forum-log-27-29-december-2019/#footnote_1_97
[03:09] dorion: Blake, your machine is all ready to go, I'll hand it to you at tomorrow's junto.
[03:20] jfw: fwiw, I ended up following this recipe so I expect it'll prompt for a new username etc. on the first bootup.
[03:25] whaack: So I just tested the hot wallet and did a successful transaction. However when I sent the transaction, or signed it rather, I had forgot to feed the fuck goats RNG into dev/urandom. I would just like to point out that from a user experience standpoint, it seems wrong to me that you can compromise your key in this way and there is no notification to the operator.
[03:29] whaack: Another question: does Jen Key automatically call gbw-save? It seems it does, and I think it should because it would be disastrous if someone generated a key sent money to that key and then didn't type gbw-save
[03:30] dorion: whaack, did you read the warning ?
[03:32] whaack: No I have not or at least not recently, still I don't see this as part of a
[03:33] whaack: ..hardware failure.
[03:33] whaack: Anyways I have to go for now I can discuss this later but I am packing for my trip tomorrow.
[03:36] dorion: whaack, alright, bon voyage.
[03:36] jfw: whaack: I suppose your argument is basically that the linux RNG APIs are "unsafe at any speed" and their usage should be removed from cryptographic software
[03:37] jfw: well, either that or fix the kernel, you didn't exclude that option indeed.
[03:39] dorion: so Blake, getting to know and use tools like IRC and Linux and Bitcoin involves reading the manuals for your tools. while you installed hexchat, to start, let's view that strategically as a fallback option and introduce you to our yrc.
[03:40] dorion: it'll be most useful for you to run yours from your training server, which maintains a pretty much constant net connection. I run mine on a server as well.
[03:41] jfw: whaack: gbw-node gen-key does not automatically save, no, as per the usual model of editing a file in working memory and updating disk only when explicitly saved
[03:42] jfw: *gbw-signer gen-key
[03:45] dorion: Blake, the yrc manual and README will be installed on the server and in addition, thanks to jfw's codeview tool, you can also read them on the web, as I've linked.
[03:45] jfw: though I suppose it lacks the feedbacks usually associated with that, "are you sure you want to quit with unsaved changes" and such
[03:53] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7670 -- well, for the key to have spendable inputs, one would think you'd have it backed up already. or what scenario(s) are you envisioning ?
[03:53] sourcerer: 2023-06-14 03:29:14 (#jwrd) whaack: Another question: does Jen Key automatically call gbw-save? It seems it does, and I think it should because it would be disastrous if someone generated a key sent money to that key and then didn't type gbw-save
[03:55] dorion: p.s. Jen Key, lolz.
[03:56] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7677 -- now there's a good point.
[03:56] sourcerer: 2023-06-14 03:37:15 (#jwrd) jfw: well, either that or fix the kernel, you didn't exclude that option indeed.
[03:56] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7686 - speech to text; all hail the new robot overlords.
[03:56] sourcerer: 2023-06-14 03:55:57 (#jwrd) dorion: p.s. Jen Key, lolz.
[03:58] jfw: to my mind the question is, what exactly is the code supposed to do instead - what alternative is there? on each operation prompt the user for a device path? which still won't guarantee they're giving the correct path?
[03:59] dorion: jfw, eh, wut overloards ? we know he'd type it fine if his hand's weren't sore. let his hands rest as we chuckle at the dumb bot.
[04:00] jfw was merely joining in observing the bot antics.
[04:01] jfw: perhaps nobody here accused the present "AI" of being cool, but the locals do.
[04:06] dorion: jfw. yeah I get it. "local yokels" who don't grok IRC.
[13:09] sstacks: morning frens
[13:11] sstacks: reviewing the bitcoind -help, cant find a command that let me check the progress/state of my bitcoind client. Is this possible?
[15:05] dorion: sstacks, while it's running, you issue bitcoind --help ; -help only shows configuration options.
[15:06] dorion: let us know the height when you find it !
[15:16] whaack: The process of using voice to text involves editing at the end. But there are some really funny ones like jen K that I sometimes want to keep. The Jen Key typo I somehow missed. Maybe for the next few days I will keep the Errors that I don't believe affect the meaning of the message
[15:16] whaack: That way there's less typing and more LOL
[15:16] whaack: That's another funny thing about saying LOL is it always puts it in capital letters for dramatic effect I guess LOL
[15:20] whaack: jfw: I can't offer a solution regarding the interface not displaying whether or not the fuck goats is feeding the orangey. As far as I can tell the problem is just operator error and the solution is to refine my process not change the code.
[15:21] whaack: Orangey equals RNG
[16:17] dorion: whaack, LOL (typed).
[16:18] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7698 - you mean "bitcoind help", i.e. "help" is itself an rpc command.
[16:18] sourcerer: 2023-06-14 15:05:55 (#jwrd) dorion: sstacks, while it's running, you issue bitcoind --help ; -help only shows configuration options.
[16:21] dorion: haha, riiiight.
[22:21] sstacks: hey guys, just noticed i did fot answer from you guys. Checking logs atm
Day changed to 2023-06-15
[21:07] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7709 - not sure what to make of this, sstacks.
[21:07] sourcerer: 2023-06-14 22:21:36 (#jwrd) sstacks: hey guys, just noticed i did fot answer from you guys. Checking logs atm
Day changed to 2023-06-17
[20:05] Blake: test
[20:07] Blake: Guys, hi - This is Daniel, Blake's dad. Blake had to step out, I thought I'd mention that in case you were waiting for him.
[20:09] Blake: While we wait for him to return, what he was saying was:
[20:11] Blake: 1. He found paid services to help with the transcriptions, and some are cool in that they insert subtitles into the video which can also be exported as text files.
[20:14] Blake: Anyway, he kept looking for free alternatives to make his task a little easier. One option is to use the "Voice typing" feature in Google Docs, essentially have a video playing and the sound feeds into the Voice typing into a document. That would still require editing, but it would simplify the task.
[20:14] Blake: Ah, see you now R, I will let Blake continue when he returns.
[20:20] dorion: thanks daniel. yeah, no rush. looking forward to reading Blake finish the question.
[20:35] Blake: Hey, I'm back, continuing what my dad was saying, the problem is that for the text-to-speech feature to work, I will need a newer or more updated version of Firefox.
[20:36] Blake: Because the version on the computer now does not support this feature.
[20:36] Blake: So what I did was install chromium, and it turns out that it did allow speech-to-text but it does not work for some reason
[20:37] Blake: What do you guys suggest me to do?
[22:17] dorion: Blake, thanks for explaining your thought process there. the first thing I'll say is I appreciate your initiative to research tools to help you with the exercise. generally though when it comes to automation, it's best practice to do the task manually. when you do, you give yourself a baseline for what it takes on your own skin, both from a time and energy perspective and lower level insight on
[22:17] dorion: the steps in the process.
[22:22] dorion: approaching automation from this perspective allows you to avoid the costs of premature optimization. it also allows you to see which parts of the process actually need and benefit from automation.
[22:32] dorion: I appreciate your focus on the end result/deliverable of the task, i.e. written transcripts of the videos. that being said, zooming out a bit, there are a few other points to consider : a) learning computers, like anything, takes exposure. watching the videos and typing out the transcript will give you focused, quality exposure to the content. you'll still need practice and time apart from
[22:32] dorion: "transcription mode" to pick it up, but each mode builds the others.
[22:35] dorion: yeah, it takes time, , but it's an investment in yourself.
[22:37] dorion: "which is a cost" was supposed to go between the commas, lol.
[22:40] dorion: b) we shared the videos with you, but we're not making them available to the public or other 3rd parties. google isn't really our friend, so we're not really keen to have you share the materials with google or other websites.
[22:41] dorion: I looked into an open source tool myself this year, called "pocketsphinx", and the output was a jumbled mess of incomprehensibility to the point of lulz. I should actually publish that sometime.
[22:45] dorion: I realize transcribing could be somewhat boring/tedious, so what I suggest you do is to go at it in doses, e.g. 60-90 minute sessions, 1 session a day. keep track of how far you get in the video so you have a record of your efficiency.
[22:46] dorion: it may also help allow the content to sink deeper into you too.
[22:48] dorion: during the other daily time you have allocated, remember I said to look into yrc.
[22:48] sourcerer: 2023-06-14 03:39:51 (#jwrd) dorion: so Blake, getting to know and use tools like IRC and Linux and Bitcoin involves reading the manuals for your tools. while you installed hexchat, to start, let's view that strategically as a fallback option and introduce you to our yrc.
[22:49] dorion: Blake, how much time do you expect to be working on jwrd tasks while you're traveling ?
Day changed to 2023-06-18
[12:13] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7723 -- I meant, "it's best practice to do the task manually first*." lol.
[12:13] sourcerer: 2023-06-17 22:17:17 (#jwrd) dorion: Blake, thanks for explaining your thought process there. the first thing I'll say is I appreciate your initiative to research tools to help you with the exercise. generally though when it comes to automation, it's best practice to do the task manually. when you do, you give yourself a baseline for what it takes on your own skin, both from a time and energy persp
[19:00] Blake: Well, some days I expect to dedicate 2 or 3 hours to working, others maybe longer or shorter
[19:02] Blake: Ok, I understand, so basically I will manually transcribe the videos by typing in real time as I watch
[19:02] Blake: So i can capture and retain the content
[19:03] Blake: Also, I understand the propitiatory aspects of the videos so I will do as told
Day changed to 2023-06-19
[13:29] whaack: !e view-height
[13:29] btcexplorer: block_height: 794580
[13:29] btcexplorer: mins_since_last_block: 4685
[13:32] whaack: Looks like my note still struggling to think << I am leaving the speech to text puzzle
[18:22] jfw: Blake: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7716 - does this line from your dad agree with the words you would use for what you were trying to do? that is, making easier & simplifying?
[18:22] sourcerer: 2023-06-17 20:14:00 (#jwrd) Blake: Anyway, he kept looking for free alternatives to make his task a little easier. One option is to use the "Voice typing" feature in Google Docs, essentially have a video playing and the sound feeds into the Voice typing into a document. That would still require editing, but it would simplify the task.
[18:26] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7719 - how did you reach this conclusion?
[18:26] sourcerer: 2023-06-17 20:35:18 (#jwrd) Blake: Hey, I'm back, continuing what my dad was saying, the problem is that for the text-to-speech feature to work, I will need a newer or more updated version of Firefox.
[18:35] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7742 - after looking up "propitiatory" in a couple sources I can't make sense of what you're saying there; can you try rephrasing please?
[18:35] sourcerer: 2023-06-18 19:03:52 (#jwrd) Blake: Also, I understand the propitiatory aspects of the videos so I will do as told
[18:37] jfw: note that there are software and hardware approaches to streamlining even the manual transcription process which might be worth a look.
[18:40] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7746 - ha, that one's clearly for Blake, as a taste of what the finest in STT tools are going to leave him even under their ideal circumstances!
[18:40] sourcerer: 2023-06-19 13:32:22 (#jwrd) whaack: Looks like my note still struggling to think << I am leaving the speech to text puzzle
Day changed to 2023-06-20
[17:28] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7739 -- alright, sounds good.
[17:28] sourcerer: 2023-06-18 19:00:10 (#jwrd) Blake: Well, some days I expect to dedicate 2 or 3 hours to working, others maybe longer or shorter
[17:28] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7741 -- cool.
[17:28] sourcerer: 2023-06-18 19:02:52 (#jwrd) Blake: So i can capture and retain the content
[17:29] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7751 -- I'd guess he means proprietary, but I'll let him clarify.
[17:29] sourcerer: 2023-06-19 18:35:34 (#jwrd) jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7742 - after looking up "propitiatory" in a couple sources I can't make sense of what you're saying there; can you try rephrasing please?
[20:45] whaack: !e view-height
[20:45] btcexplorer: block_height: 794667
[20:45] btcexplorer: mins_since_last_block: 5654
[20:52] sstacks: jfw: sorry to ask. Im having trouble connecting thru yrc with my thinkpad
[20:53] whaack: Hi Blake
[20:53] sstacks: jfw: "Error: Mode to unknown target: :sstacksyrc! xxxxxxxx MODE sstacksyrc :+i
[20:53] sstacks: this output is from yrc
[20:54] whaack: The best SST I have used is the won with the iPhone. The one I am using now is the Mack OS native SST. I am not sure why this one is a little worse but I think it may just be because the microphone is not as good on the Mac computer
[20:57] jfw: sstacks: that's a harmless error, it means the server sent something the client didn't understand but in this case it's unimportant
[20:58] jfw: at least that's how it reads to me on first glance, though it'd be nice to check on why the target is unknown.
[21:00] sstacksyrc: hello
[21:01] jfw: ahoy sstacksyrc, you made it!
[21:01] sstacksyrc: had some good backup
Day changed to 2023-06-21
[01:28] whaack: !e view-height
[01:28] btcexplorer: block_height: 794743
[01:28] btcexplorer: mins_since_last_block: 5181
[13:45] whaack: !e view-height
[13:45] btcexplorer: block_height: 794794
[13:45] btcexplorer: mins_since_last_block: 5455
[13:46] whaack: It seems that the notice thinking at a rate that is so slow that it never makes enough progress to get caught up with the tip.
[13:48] whaack: I have a more beefy server running at 103.6.212.28 that is available for use. Just type that IP into your browser in order to access the service
[13:49] whaack: I will try to get the IRC bot running on that server
[14:21] dorion: whaack, any idea why it's struggling to sync to the tip ? is this on ssd or spinning platters ? how many peers do you have ? are you getting flooded w/ bastards ?
[14:23] dorion: sometimes when I'm behind, I'll restart to node w/ connect=$ipoftrustednode and to simplify with one connection until I'm at the tip. then I'll restart again w/ a list of addnode= in the config.
[14:35] dorion: whaack, sstacks, Blake, jfw, etc. will tomorrow at 1900 utc work for everyone for the office hours call ?
[14:35] dorion: whaack, please loop atlas in too.
[14:37] sstacks: dorion: this is 2pm Panama time. Ill be having problems with this time and even with the 4pm time. I have a vet's appointment at 3pm.
[14:37] dorion: whaack, I think he connected at one point, but haven't seen him in a while.
[14:37] sourcerer: 2023-05-24 03:28:56 (#jwrd) dorion_road: welcome barbarian.
[14:38] dorion: sstacks, alright. could you do earlier ? say 1pm Panama time ?
[14:39] sstacks: dorion: Yes! Im sorry for inconvenience.
[14:40] dorion: does 1800 utc/1300 panama time work for everyone else then ?
[15:51] jfw: dorion: works for me.
[22:49] whaack: I cannot do that time. I am busy between 1630 UTC and 22 00 UTC. Any other time should work. I may be able to connect at 18 UTC but I will be commuting on a train and only able to talk for maximum one hour
[22:49] whaack: I want to somehow make this work. Is it possible for others to do 10:30 AM Panama time?
Day changed to 2023-06-22
[01:11] jfw: 10:30am Panama is ok for me too, but I begin to wonder if there's something more generally wrong with the usual 4pm slot since something always seems to be coming up for someone.
[01:50] dorion: I have a meeting at 11am tomorrow, will need to be afk by 1030ish :-/
[01:55] jfw: how about the usual 4pm but on friday?
[12:06] dorion: jfw, that'll work for me.
[14:08] whaack2: That time works for me as well
[14:09] whaack2: Dorian: I have not been able to look into why the sink is so slow. I may try your restart method only connected to trusted peers later today
[14:14] whaack2: I pinged Atlas on other communication channels. Unfortunately, it seems shitcoiners have stolen his time with promises of large pots of gold that are supposed to arrive very quickly.
[15:01] dorion: whaack2, alright.
[15:41] jfw: whaack: well at least "large pots of gold arriving quickly" is a bet that will play out soon enough. hopefully the returns are measured against btc too.
[15:44] jfw: at first glance the current machine learning research looked like quite a froth, that the inquisitive but unguided mind could easily burn inordinate amounts of time trying to get on top of
[15:49] jfw: (then add 'blockchain' and easy money to the mix for maximum shiny)
[16:20] whaack: !e view-height
[16:20] btcexplorer: block_height: 795211
[16:20] btcexplorer: mins_since_last_block: 2788
[16:54] whaack: !e2 view-height
[16:54] btcexplorer: whaack: my valid commands are: src, uptime, version, help, view-height, view-address, view-utxos, view-balance, view-block, view-raw-block, view-tx, view-raw-tx, push
[16:54] btcexplorer2: block_height: 795466
[16:54] btcexplorer2: mins_since_last_block: 6
[16:54] jfw: lolz
[16:54] whaack: lol will fix
[16:55] whaack: !nze view-height
[16:55] nzbtcexplorer: block_height: 795466
[16:55] nzbtcexplorer: mins_since_last_block: 7
[16:56] whaack: nz = New Zealand
[16:56] whaack: gotta run for now
[16:59] jfw: the republican bots used single-char callsigns, fwiw
Day changed to 2023-06-23
[01:12] whaack: !E view-height
[01:13] whaack: !E view-height
[01:13] nzbtcexplorer: block_height: 795517
[01:13] nzbtcexplorer: mins_since_last_block: 1
[01:13] whaack: !e view-height
[01:13] btcexplorer: block_height: 795276
[01:13] btcexplorer: mins_since_last_block: 2679
[01:14] whaack: jfw: updated to match spec
[01:15] whaack: There are still more things to do in order to get it to spec. For example there is no way atm to send a private message for help
[03:01] Barbarian_: Hello
[03:10] Barbarian_: So glad to be remembered, I would be terribly pleased to be a part of the call tomorrow at 4PM. Regarding the chitchat about the "Big shiny" it would be best if we schedule a seperate call to discuss this project.
[13:51] whaack: Good to see you in chat, barbarian. I'm not sure if the meeting today is confirmed, sstacks do you plan to come?
[13:59] whaack: Also barbarian, i think talking about the 'big shiny' is best discussed on irc. This way the conversation is logged and can be reviewed and commented on by the participants and anyone else. It's also asynchronous so people can respond when they have free time instead of having to take a block out of their day.
[18:15] Barbarian_: Hello all, looking forward to the chat this afternoon. Going forward there will be no discussion regarding the "Big Shiny" as to not detract from the very important work we are doing here.
[19:09] dorion: sstacks can't make it, but I think we should go ahead.
[19:54] Barbarian_: So where will this call be hosted?
[20:02] dorion: Barbarian, on zoom.
[20:03] Barbarian_: Okay
[20:03] Barbarian_: let me quickly set up an account
[20:39] jfw: barbarian: afaik an "account" isn't necessary, you can just connect using the meeting ID + passcode like last time. it can be helpful to pre-install the software though; the version I use is available at http://welshcomputing.com/files/zoom/
[20:40] Barbarian: Okay just connceting now
[20:41] Barbarian: Connected
[20:43] jfw: well we won't be starting for another 20 minutes or so, but I expect you can just leave it there.
[20:43] Barbarian: Okay
[20:44] whaack: !e view-height
[20:44] btcexplorer: block_height: 795576
[20:44] btcexplorer: mins_since_last_block: 479
[20:44] whaack: much progress
[20:45] whaack: Great to have you joining today Atlas
[20:45] Barbarian: Glad to be joining myself
[20:46] Barbarian: !e view-height
[20:46] btcexplorer: block_height: 795576
[20:46] btcexplorer: mins_since_last_block: 481
[20:46] Barbarian: Cool that you have a block explorer integrated into the IRC.
[20:46] Barbarian: What are some of the commands?
[20:47] whaack: !e help
[20:47] btcexplorer: whaack: my valid commands are: src, uptime, version, help, view-height, view-address, view-utxos, view-balance, view-block, view-raw-block, view-tx, view-raw-tx, push
[20:47] whaack: ^^
[20:47] whaack: Try one.
[20:48] Barbarian: nice
[20:48] Barbarian: !e view-address 1As8fqoyZam1G5kLqKd4AW5pNMFN35N8BS
[20:48] btcexplorer: http://paste.deedbot.org/?id=-wMN 1 of 1
[20:49] whaack: This block explore was built on top of jay FW's gbw-node
[20:49] Barbarian: !e uptime
[20:49] btcexplorer: Barbarian: time since my last reconnect : 4d 7h 19m
[20:49] whaack: jfw*
[20:49] Barbarian: !e uptime jfw
[20:49] btcexplorer: Barbarian: time since my last reconnect : 4d 7h 19m
[20:49] Barbarian: Cool
[20:50] Barbarian: So how did you code this?
[20:50] Barbarian: I would love to know more about how it works.
[20:50] dorion: !e src
[20:50] btcexplorer: dorion: my source code can be seen at: http://ztkfg.com/2020/07/a-bitcoin-block-explorer-the-why-the-how
[20:52] Barbarian: interesting
[20:54] Barbarian: !e version
[20:54] btcexplorer: I am 'trbexplorer' version 630877.
[20:54] whaack: I'm excited to start blogging again. I'll have to do my first STT assisted article
[20:54] whaack: That version number is meaningless. I should fix it
[20:55] Barbarian: nice, I've heard that speech2text tech is improving daily
[20:55] whaack: Maybe it is. But it still a painful experience. I won't correct these sentences so that you can see the types of errors it makes. Mind you I am also speaking in a slow and unnatural manner to make it easier for the computer to understand me
[20:56] whaack: But you can also see that it is pretty impressive. It certainly is helping me out a lot
[20:56] Barbarian: Yeah
[20:57] Barbarian: Which one are you using now?
[20:57] whaack: I am using Apple's built-in speech to text for Mac OS 10.16
[20:58] whaack: Sorry, 10.13
[20:58] Barbarian: Okay
[20:59] whaack: Unfortunately it was too much of a hassle to transport my microphone. It may work better if I got good external mic
[20:59] Barbarian: Certainly.
[21:00] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7831 - I don't think "full compliance" or anything is essential right now, fwiw; we can adapt it to our needs if and when the time comes. that spec is best which specifies least, or at least doesn't prematurely overspecify.
[21:00] sourcerer: 2023-06-23 01:15:56 (#jwrd) whaack: There are still more things to do in order to get it to spec. For example there is no way atm to send a private message for help
[22:00] Barbarian: https://twitter.com/shinohai2017
[22:02] Barbarian: https://twitter.com/FacetSir
[22:02] Barbarian: https://twitter.com/DreadBong0
[22:30] whaack: Thanks for coming barbarian. You should hang out an this channel and get working on some cool project. Also you may want to start a blog. It provides you a way to analyze your own thoughts among a million other benefits.
[22:47] Barbarian: Maybe
[23:35] Barbarian: I will certainly be in IRC more, just maybe about the blog.
Day changed to 2023-06-24
[14:52] whaack: !e view–height
[14:53] whaack: hm, btcexplorer seems to have died last night. How sad
[14:53] whaack: !E view–height
[14:53] nzbtcexplorer: whaack: my valid commands are: src, uptime, version, help, view-height, view-address, view-utxos, view-balance, view-block, view-raw-block, view-tx, view-raw-tx, push
[14:53] whaack: !E view-height
[14:54] nzbtcexplorer: block_height: 795727
[14:54] nzbtcexplorer: mins_since_last_block: 10
[14:58] whaack: !e view-height
[14:58] btcexplorer: block_height: 795653
[14:58] btcexplorer: mins_since_last_block: 719
[15:28] dorion: Barbarian, ever read : http://trilema.com/2014/a-conceit-or-the-importance-of-blogging/ ?
[16:29] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7893 - this came up from someone mentioning shinohai as a sort of shitcoin sommelier. it looks to be the guy
[16:29] sourcerer: 2023-06-23 22:00:21 (#jwrd) Barbarian: https://twitter.com/shinohai2017
[16:39] jfw: barbarian: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7898 - perhaps as an easier question to start with, do you do much writing at all, whether for other venues or just for yourself?
[16:39] sourcerer: 2023-06-23 23:35:42 (#jwrd) Barbarian: I will certainly be in IRC more, just maybe about the blog.
[16:41] jfw: I recall at high school age I was resentfully slogging through school assigned essays with no patience remaining to write for myself, though I certainly could have and quite likely would have benefitted
[16:46] jfw: !E view-height
[16:46] nzbtcexplorer: block_height: 795739
[16:46] nzbtcexplorer: mins_since_last_block: 6
[16:47] jfw: whaack: btcexplorer and nzbtcexplorer are added to sourcerer's bots list so their output is dimmed in the web log view.
[19:40] Barbarian: jfw, thanks for the advice. I will check out that trilema article on a bit. Right now I'm a bit busy.
[19:40] Barbarian: *in
[20:00] jfw: I wasn't aware of having given any advice per se, heh.
[22:07] whaack: Jay FW: it looks like 1.deep bot.org is down. paste. Deed bot.org is a dependency of PTC explore are. I may switch to your paid service. Taste service. Aced service. Paste Service
[22:08] whaack: I left in the speech to text errors there cause they were quite hilarious.
[22:57] jfw: whaack: the errors quite recall the experience of trying to type with pnoje onscreen keyboards with the various swiping & predictive assistance modes. "so fast!!"
[23:00] jfw: yes, unless you're maintaining relations with trinque and can expect things to get things like that fixed timely (which MP et al could not on various occasions) it would make sense to look for alternatives, and you're welcome to use mine.
[23:00] jfw: *expect to get things
[23:04] jfw: if you use the web submission gateway it should be a drop-in replacement, or if you use the raw tcp mode it shouldn't need any web libraries at all.
[23:07] jfw: I call it "gateway" because it's literally just a php script that receives a POST then forwards it to the same tcp service.
Day changed to 2023-06-25
[15:12] whaack: !e view-height
[15:12] btcexplorer: block_height: 795870
[15:12] btcexplorer: mins_since_last_block: -9
[15:13] whaack: Not only did we sink, but we got to the future!
[22:43] jfw: ahoy blake, how are travels going?
[22:44] Blake: Hey, everything's going well over here, spending time with my grandma and dedicating a couple hours a day to the tasks at hand. How are you guys?
[22:46] jfw: doing alright here
[22:46] jfw: I heard you had some troubles with irc connectivity?
[22:49] dorion: heya, Blake. all good here.
[22:56] jfw: Blake: I'm glad to hear all is well and you got some work time in. It looks like you're not at the keyboard now so we can continue the conversation some other time.
[23:07] Blake: Sorry,I was finishing up the video, it's all done now. I'm glad everything is good over there.
[23:08] Blake: Yes Jacob, the problem is that the device will not connect to the internet / wifi at my grandma's residence, so I can only connect when I am "home".
[23:13] dorion: Blake, when do you expect to be able to turn in the transcript for the first video ?
[23:15] Blake: Now, I finished it 10min ago
[23:18] dorion: nice. what kind of document did you write it in ?
[23:18] Blake: Libre Office Writer
[23:19] Blake: How do I send it to you?
[23:21] dorion: alright, email it to me.
[23:22] Blake: Ok, what's your email?
[23:22] Blake: I'll do it in a while, I'm going to the gym
[23:44] whaack: blake: thanks for transcribing. I'm curious to see what the class looks like in text format. I guess I'm assuming hear that the transcriptions are going to be made available to us. Is that true dorian? Also, Blake did you transcribe our lesson or the first class of a different group?
Day changed to 2023-06-26
[00:57] dorion: Blake, check your pm.
[01:06] jfw: Blake, did you notice you missed some responses & questions from last week?
[01:07] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7940 - what "device" do you mean? (and for any helpful bystanders, I'm asking him specifically, no need to guess.)
[01:07] sourcerer: 2023-06-25 23:08:21 (#jwrd) Blake: Yes Jacob, the problem is that the device will not connect to the internet / wifi at my grandma's residence, so I can only connect when I am "home".
[04:41] jfw: http://jfxpt.com/2023/jwrd-dovecot-initial-release-aka-version-240/ finally!
[14:34] dorion: jfw, fuckin' sweet, conyo.
[14:36] dorion: Blake, on first pass of your work, for your first time and on a relatively abstract lesson, you did an outstanding job. It was a pleasure to read.
[14:38] dorion: thank god it's monday, good morning to all ((except any socialist who might be reading the log at some point. FU. obviously)).
[14:52] dorion: jfw linked this classic in another channel and upon rereading this morning, I'm sharing here. it's well worth the read for everyone.
[15:49] jfw: good morning dorion, you're sounding cheerful today.
[15:50] jfw: dorion: "conyo" ??
[16:15] dorion: jfw, ny for n with ~ hat.
[16:16] dorion: Blake, you mentioned the transcription took you longer than you expected, how long did it take you actually ?
[17:31] whaack: hm..nzexplorer disconnected now
[17:33] jfw: whaack: indeed, of its own accord apparently
[17:35] whaack: BTC explorer disconnected after being up for about one to 2 days, same for NZ Explorer. So it looks like there may be a problem with the irc component of the bot. First step may be to check the reconnect logic.
[17:36] whaack: Congrats Jeff W on Dove caught. I haven't looked at the article in detail but it looks like you have" been a busy boy" again
[17:36] jfw: dorion: as in, "con~o m (fam) Vulva." ? I still dun geddit
[17:38] jfw: whaack: well the six months between the last patch / release timestamp and article chafes a bit but yeah. -Jeff W
[17:40] whaack: Jay FW: the way that I think he's using the phrase conyo the meaning what approximate to "wow" similar to the way English speakers may say "damn" to emphasize being impressed
[17:42] whaack: The man has many names exclamation Point
[17:43] whaack: I say! All the time and this time it Decides to turn into two words. I can't understand this program.
[17:49] dorion: jfw, talk to more people in spanish and you'll get it, but whaack has it, it adds emphasis.
[17:49] jfw: I did check the jerga panamenya file too, fwiw.
[17:50] dorion: whaack, does your bot keep a log ? anything interesting there ?
[17:51] dorion: jfw, their equivalent is cucha. tbf, I've heard it most from venezuelanas.
[17:52] jfw: oh, chucha, why didn't you just say so!! lolz
[17:52] jfw: yeah haven't hung out much with vzla/os yet.
[20:38] whaack: dorion: it keep a log I didn't notice anything interesting there
[20:45] whaack: !e view-height
[20:45] btcexplorer: block_height: 796057
[20:45] btcexplorer: mins_since_last_block: 0
[20:45] whaack: !E view-height
[20:45] nzbtcexplorer: block_height: 796057
[20:45] nzbtcexplorer: mins_since_last_block: 16
Day changed to 2023-06-27
[12:05] dorion: buenos dias a todos.
[12:07] dorion: Blake, the next task for you is to establish an ssh key which we'll use to provide you server access. in the group 8 directory, there's an orientation file that has ssh instructions. follow the steps under the macosx header on your Linux.
[13:34] whaack: morning gents
[13:47] whaack: Barbarian: why don't you get started on some project? For example, you could try setting up a gpg key. Or installing gales bitcoin wallet.
[16:35] jfw: creating a gpg key, while not that big of a project in itself, is foundational for sure.
[16:39] dorion: whaack, good question and pointers. Barbarian, note for the gbw-node side of gbw, you'll need a local bitcoind.
[16:41] dorion: yrc would also be a good entry point. fundamental development there will involve adapting it to speak the eulora2 comms protocol.
[16:41] sourcerer: 2023-06-14 03:39:51 (#jwrd) dorion: so Blake, getting to know and use tools like IRC and Linux and Bitcoin involves reading the manuals for your tools. while you installed hexchat, to start, let's view that strategically as a fallback option and introduce you to our yrc.
[16:43] jfw: I forget, does Barbarian have a linux box or his own computer at all?
[16:45] dorion: we're working to make eulora2 our primary means of chat because it's superior to IRC in many ways. in the shortrun we'll maintain IRC as a fallback, but as we develop eulora2, IRC will become increasingly less relevant.
[16:47] dorion: in the wider lens there, once yrc speaks e2, it could be developed further to be a full text-based client for the "game-game".
[16:48] dorion: jfw, i dunno. i'd assume he at least has a laptop of his own, but will let him clarify.
[16:51] dorion: Blake, for the next transcription, use nano instead of libreoffice. nano is terminal based and reads/writes plain text files. to open it, open a terminal and type "nano" and hit enter.
[16:55] dorion: that will open the program. at the bottom, you'll see a menu. the '^' character means the CRTL button and the 'M' character means Meta or alt. go ahead and explore the menu and practice saving, exiting and reopening some test files. you can also issue at a terminal "man nano" for its manual page and "man --help" for a summarized help.
[17:01] dorion: Blake, in ubuntu, to restart the networking services/interfaces you can : 1) open a terminal ; 2) issue : $ sudo service network-manager restart
[17:03] dorion: in your case, we'll see if that does anything to solve your wifi connection issues. more generally, this can be used when you want to apply networking changes from configuration files, such as /etc/hosts
[18:49] jfw: dorion, am I reading half of a conversation with blake here? or how did we get to restarting network-manager
[18:54] jfw: "nano --help" I assume you mean
[18:56] dorion: jfw, right. thanks.
[18:56] dorion: jfw, yeah, it's a half conversation, he's stuck in the swamps because laptop isn't connecting to the network he's on.
[19:01] jfw: does ubuntu really interpose the networkmanager crap on top of the hosts file? not that I'm against shooting the stinking thing in the head at every opportunity but I didn't know it had got its tentacles quite that deep
[19:04] dorion: yeah, I've changed an ip in /etc/hosts and the browser didn't know about the change until I restarted the networking. barbaric, but is what it is.
[19:05] jfw: hm, possibly that's the browser caching the file itself and it just happens to be triggered to refresh that by seeing the interface go down.
[19:07] jfw: sanely speaking there's nothing required to "apply" a change to the hosts file besides saving it. but sanity is understood to be excluded once browsers get involved.
[19:56] jfw: dorion: I'll second whaack's question on what you intend to do with the transcripts. far as I'm concerned we should post them for the class.
[19:56] sourcerer: 2023-06-25 23:44:18 (#jwrd) whaack: blake: thanks for transcribing. I'm curious to see what the class looks like in text format. I guess I'm assuming hear that the transcriptions are going to be made available to us. Is that true dorian? Also, Blake did you transcribe our lesson or the first class of a different group?
[23:11] jfw: whaack: on your question of why do you need a route for the local subnet/link if the default route seems to cover it anyway, here's the linux kernel's response to the attempt to create a default route through a gateway not included in any directly connected address range:
[23:12] jfw: # route add default gw 10.9.1.1 dev eth0
[23:13] jfw: route: ioctl 0x890b failed: Network unreachable
[23:15] jfw: (I get this still doesn't quite address if/why it has to be that way.)
[23:20] jfw: I suppose you could look at it as a sanity check - it won't accept a gateway address that it doesn't have a way to reach through one of its direct links, and it's not going to add a special case for "but what if the gateway is actually included in the route that I'm now adding". that would seem quite circular to me.
Day changed to 2023-06-29
[21:02] jfw: sstacks, whaack: I'm here for the office hours if anyone needs it.
[21:31] whaack: jfw: just saw this now. i am also online but unfortunately dealing with the painful task of renewing Government documents
[21:32] whaack: While I am here I am renewing my get out of jail permission slip
[21:45] jfw: whaack: heh, I didn't know they made those at least for us non-Clintons
[21:46] jfw: but if you mean drivers' license then yeah, less painful to renew than to reinstate later if it expires.
[21:46] whaack: I'm referring to my passport LOL
[21:46] jfw: aok
[21:47] whaack: Off to take the photo will be back later
[21:47] jfw: dorion & I both had that renewed while in panama, fwiw.
[21:48] jfw: I get the "get out of jail" part now.