Fixpoint

Day changed to 2023-07-03
[00:12] whaack: http://ztkfg.com/2023/07/the-rsi-saga-continued/ & http://ztkfg.com/2023/07/remarks-on-ulnar-nerve-compression/
[00:12] whaack: !E view-height
[00:12] nzbtcexplorer: block_height: 796934
[00:12] nzbtcexplorer: mins_since_last_block: 9
[00:14] whaack: !e view-height
[00:14] btcexplorer: block_height: 796935
[00:14] btcexplorer: mins_since_last_block: -15
[01:42] jfw: whaack, is it measuring that time delta based on the block header's time field or how is it possible to be negative?
[12:41] jfw: sstacks, whaack: with tomorrow being a US holiday and whaack at least being in that social environment, we're thinking to reschedule tomorrow's training perhaps for Wednesday, does that work for you?
[12:49] jfw: Blake, are you back in town?
[13:13] dorion: good morning #jwrd.
[13:13] dorion: Blake, are you available to come over for some coworking on Wednesday and Thursday ?
[13:27] whaack: jfw: I appreciate that. Yes let's meet on Wednesday.
[13:30] whaack: jfw: yes it takes the difference between the timestamp included in the block header and the time of the server
[13:31] whaack: http://welshcomputing.com/paste/a5jcmzeh9y <-- exact code here
[13:32] jfw: whaack: to me that seems like a comparison without a common reference frame, ie between bitcoin time and local server time
[13:33] jfw: and "time since last block" to me means literally "how long has it been since we last saw a new block"
[13:34] jfw: ie a high value would mean "node is stuck" not "node is behind"
[13:35] whaack: You're absolutely right, the key is misleading. The important information to convey is how long it's been since the server has imported a new block.
[13:41] whaack: Looks like it's time to make a new list of to-do items for the explorer and get cracking.
[17:33] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#8009 -- yeah, we can share them. whaack, they are transcriptions of your group. part of the idea is, having the text, we analyze the content more efficiently to improve it and scripts can form the basis for a 'textbook'.
[17:33] sourcerer: 2023-06-27 19:56:02 (#jwrd) 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.
[17:35] jfw: we can just post it as-is in the odt format for now, if that bothers anyone then they can do the conversion, the text is there now at least.
[17:36] dorion: jfw, I already converted the first and he's writing as plain text.
[17:36] dorion: writing the 2nd*
[17:37] jfw: dorion: oh ok, I hadn't yet seen whether good use was made of the formatted medium.
[18:04] Blake: Hello everyone, sorry I was not connected for a couple days. I have been advancing with the transcription of the second video. Do you want me to submit the parts as I go along or when I complete it? I have about an hour left.
[18:15] dorion: Blake, you can wait to send it all at once.
Day changed to 2023-07-04
[00:47] sstacks: jfw: sorry for not answering. If we meet on Wed. is fine by me.
[01:28] jfw: sstacks: all good; Wednesday it is, then.
[04:09] jfw: Blake: the problem is not that you had connection trouble. The problem is that when you're on, you proceed with this one-way communication flow, seemingly without a clue that you might have missed something while you were out. You know?
[16:49] whaack: si estoy 100 usd in colones
[16:49] whaack: aqui
[16:50] whaack: si estoy 100 usd in colones
[16:50] whaack: aqui
[16:50] whaack: lo quiere in coloaqui
[16:51] whaack2: ^ keyboard malfunction
[16:53] whaack2: My keyboard has the ability to store macros. I can click a key to set a macro and then click a series of keys to store in that macro
[16:53] whaack2: It appears what has happened is that I accidentally started recording a macro months ago and stored an extremely long sequence that contains messages I wrote to others
[16:54] whaack2: Just now, I must've accidentally clicked whatever I bound the macro to and my keyboard was uncontrollably sending the buffer contents. I had to unplug it
[16:54] whaack2: si estoy 100 usd in colones
[16:54] whaack2: aqui
[16:56] whaack2: goddamn happened again
[16:57] whaack2: pretty sure i know the offending key
[17:59] jfw: whack: heh, no :registers command to view the stored recordings?
[18:05] Blake: Ok, will do. Yes sorry, now that I am back in PTY I am not always at home with the computer.
[18:49] jfw: blake, this reply doesn't make sense to me, can you rephrase? will do what exactly?
[19:50] Blake: Yes, of course, I meant that the wifi connection problem is not a factor anymore because I am not in the US, the thing is that I leave my computer home so when I'm out I do not get the IRC notifications.
[20:23] jfw: blake, but just because something isn't going "ding", doesn't mean you lose the capacity to read, lolz
[20:32] jfw: blake, do you understand the situation you've got yourself into and what you need to do about it? it seems to me that you don't, but I'm not going to compulsively give advice if it's not wanted
[22:12] dorion: well, he'll be coming over tomorrow, so we can sort it out further then.
[22:35] jfw: dorion: what time?
Day changed to 2023-07-05
[03:45] dorion: jfw, I had asked him the same right about when you asked me and haven't heard back. I suggested 830am.
[04:08] jfw: dorion: thx for the followup and as we discussed, you can handle things tomorrow if the timing doesn't work out for me and we'll expect him back on Thursday.
[04:15] Blake: jfw: I can understand the frustration, however, I am still trying to figure IRC out. I hope tomorrow you guys can talk me through it a bit better. About the time, I talked with Robinson and confirmed for tomorrow at 8:30am, but I need the location so I can uber there.
[04:26] Blake: See you tomorrow.
[16:36] Blake: jfw: There is a comment in your moderation queue http://jfxpt.com/2023/grand-reopening-of-jwrd-the-irc-channel/#comment-2421
[16:41] blakeeus: jfw: Tomorrow I will get to all the messages I have not attended yet.
[16:56] dorion: blakeeus, welcome to online personhood, cheers !
[17:04] jfw: blakeeus: comment approved. Glad to hear it about the backlog and looking forward to seeing it.
[17:48] sstacks: jfw, whaack: at this moment I have an unexpected errand to do. Not sure if im going to make it in time. Ill do my best
[19:25] jfw: sstacks: alright, good luck
[20:21] jfw: added a http://jfxpt.com/reference-configurations/ page reachable from the sidebar to anchor that tmux.conf for starters.
[21:01] sstacks: Connecting
Day changed to 2023-07-06
[14:28] blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7678 dorion: Yes, I'm starting to get a bit more used to it with guidance, currently I am trying to get YRC through tmux in the SSH server.
[14:28] 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.
[14:33] blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7747 jfw: Initially, yes, however, now I understand why I am writing the transcriptions out manually; that is so I retain and can get more involved in the topic by improving my knowledge.
[14:33] sourcerer: 2023-06-19 18:22:23 (#jwrd) 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?
[14:36] blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7754 jfw, whaack: Yes, I see the possibility of there being wording and spelling mistakes, even missing out words or lines.
[14:36] sourcerer: 2023-06-19 18:40:10 (#jwrd) 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!
[14:37] blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7760 dorion: Yes, sorry.
[14:37] sourcerer: 2023-06-20 17:29:03 (#jwrd) dorion: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7751 -- I'd guess he means proprietary, but I'll let him clarify.
[14:38] blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7766 whaack: Hi
[14:38] sourcerer: 2023-06-20 20:53:03 (#jwrd) whaack: Hi Blake
[14:41] blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7949 whaack: I believe it was part of the group, the video that touches the topic of permutations.
[14:41] 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?
[14:44] blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7956 dorion: Thanks! Hope to have the each one come out mejor. Answering your next message about how long it took me: I worked about 2-3 hours a day from Tuesday to Saturday.
[14:44] sourcerer: 2023-06-26 14:36:09 (#jwrd) 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:45] blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7986 dorion: Hecho
[14:45] sourcerer: 2023-06-27 12:07:32 (#jwrd) 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.
[14:48] blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7997 dorion: Yes for this second transcription and the future ones to come (unless something changes of course) I will be using Nano for it. I am learing how to use it better with the manual.
[14:48] sourcerer: 2023-06-27 16:51:19 (#jwrd) 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.
[14:49] blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7999 dorion: This is not a factor anymore, so we are good to go
[14:49] sourcerer: 2023-06-27 17:01:32 (#jwrd) dorion: Blake, in ubuntu, to restart the networking services/interfaces you can : 1) open a terminal ; 2) issue : $ sudo service network-manager restart
[14:51] blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8035 jfw: Yes, made it back and am appreciative not just to be in Panama, but to be able to come over and advance on projects here in the HQ
[14:51] sourcerer: 2023-07-03 12:49:59 (#jwrd) jfw: Blake, are you back in town?
[14:55] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8090 -- alright, start reading the texts I linked you on yrc. I'm not sure if it's installed on your server yet.
[14:55] sourcerer: 2023-07-06 14:28:41 (#jwrd) blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7678 dorion: Yes, I'm starting to get a bit more used to it with guidance, currently I am trying to get YRC through tmux in the SSH server.
[14:58] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8094 -- well, it's not just mispellings but miswordings too. for context, whaack has some ongoing wrist pains (it's in the logs) and is using some STT to give his hands a rest. so some of his output here can be pretty wtf ? for the untrained eye, but it's lulzy for us since we know the context and know him well enough to understand what he means.
[14:58] sourcerer: 2023-07-06 14:36:47 (#jwrd) blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7754 jfw, whaack: Yes, I see the possibility of there being wording and spelling mistakes, even missing out words or lines.
[14:59] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8102 -- alright, so 10-15 hours for 90 minutes of class.
[14:59] sourcerer: 2023-07-06 14:44:04 (#jwrd) blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7956 dorion: Thanks! Hope to have the each one come out mejor. Answering your next message about how long it took me: I worked about 2-3 hours a day from Tuesday to Saturday.
[15:00] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8104 -- claro.
[15:00] sourcerer: 2023-07-06 14:45:20 (#jwrd) blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7986 dorion: Hecho
[15:01] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8106 -- nice, there's also vim, but that's a longer term project as a tool to add to you belt. has a steeper learning curve than nano, but brings more leverage once you know it.
[15:01] sourcerer: 2023-07-06 14:48:35 (#jwrd) blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7997 dorion: Yes for this second transcription and the future ones to come (unless something changes of course) I will be using Nano for it. I am learing how to use it better with the manual.
[15:01] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8110 -- ;-)
[15:01] sourcerer: 2023-07-06 14:51:26 (#jwrd) blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8035 jfw: Yes, made it back and am appreciative not just to be in Panama, but to be able to come over and advance on projects here in the HQ
[15:21] dorion: yeeee, now blakeeus is on yrc !!
[15:29] blakeeus: Hello!
[16:52] jfw: blakeeus: congrats on that, and on discovering that the logs are there to be used - apparently even this is not so obvious a concept as it seemed
[16:53] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8092 - that's part of it, dorion mentioned another
[16:53] sourcerer: 2023-07-06 14:33:04 (#jwrd) blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7747 jfw: Initially, yes, however, now I understand why I am writing the transcriptions out manually; that is so I retain and can get more involved in the topic by improving my knowledge.
[16:53] sourcerer: 2023-06-17 22:22:16 (#jwrd) 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.
[16:56] jfw: blakeeus: otherwise, what struck me as funny was that through your (reasonable) desire for easier & simpler methods what you ended up at was a massive pile of someone else's broken software, leaving you scratching your head and unable to proceed at all
[16:59] jfw: software problems can be fixed, but it tends to be quite labor intensive (and skilled labor too); so at a certain point it might make sense to look into, but not before even gaining the experience of doing it the simple way.
[17:04] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8096 - fwiw I hadn't even guessed that you meant 'proprietary', the words seem nothing alike in either meaning, pronunciation or spelling; brain-level typo I guess. it got some good chuckles anyway.
[17:04] sourcerer: 2023-07-06 14:37:40 (#jwrd) blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7760 dorion: Yes, sorry.
[17:08] jfw: dorion: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7956 - when do I get to see the results?? I'm anticipating this new kind of look in the mirror, "omg do I really sound like THAT? did I really say THAT?"
[17:08] sourcerer: 2023-06-26 14:36:09 (#jwrd) 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.
[17:10] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8110 - sounds like it'll be a good change of environment for you.
[17:10] sourcerer: 2023-07-06 14:51:26 (#jwrd) blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8035 jfw: Yes, made it back and am appreciative not just to be in Panama, but to be able to come over and advance on projects here in the HQ
[17:14] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8114 - indeed the miswordings are the worst, for being the most subtle. basically all the present "AI", from the humble assistive onscreen keyboards to the massive neural networks, operates without any grasp of *meaning*, merely looking for ~ highest probability match from a noisy sample or "sounds human-like"
[17:14] sourcerer: 2023-07-06 14:58:22 (#jwrd) dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8094 -- well, it's not just mispellings but miswordings too. for context, whaack has some ongoing wrist pains (it's in the logs) and is using some STT to give his hands a rest. so some of his output here can be pretty wtf ? for the untrained eye, but it's lulzy for us since we know the context and know him well enoug
[17:20] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8116 - ten to one sounds rather painful, though I suppose it might include some leisurely replays for understanding
[17:20] sourcerer: 2023-07-06 14:59:44 (#jwrd) dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8102 -- alright, so 10-15 hours for 90 minutes of class.
[17:21] jfw: blakeeus: what was/is your process like there?
[17:31] jfw: I did try to help on that, though the conversation was jammed, what can I say.
[17:31] sourcerer: 2023-06-19 18:37:04 (#jwrd) jfw: note that there are software and hardware approaches to streamlining even the manual transcription process which might be worth a look.
[17:36] jfw: sstacks, whaack: reminder of office hours today, 4pm panama time; let me know if you want to do a call otherwise I'll just check in here
[18:13] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8138 - to further belabor this point, it means that AI output is *at best* wikipedia, and unless you're very sharp indeed your chances of noticing when you're being fed sewage are not good.
[18:13] sourcerer: 2023-07-06 17:14:15 (#jwrd) jfw: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8114 - indeed the miswordings are the worst, for being the most subtle. basically all the present "AI", from the humble assistive onscreen keyboards to the massive neural networks, operates without any grasp of *meaning*, merely looking for ~ highest probability match from a noisy sample or "sounds human-like"
[20:18] whaack: Great I'll be online
[20:19] whaack: Hey blakeus good to see you here
[20:57] whaack: ill join the zoom in 5ish mins
Day changed to 2023-07-07
[13:29] dorion: blakeeus, this trilema on domain name strategy is worth the read as you pick yours.
[13:40] jfw: possibly http://jfxpt.com/2023/fixpoint-is-moving-in-domain-name-space/ too
[13:46] blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8114 dorion: Yeah it would just add more work since I would not only have to listen to the video, but edit the monstrous text it "gifted" me.
[13:46] sourcerer: 2023-07-06 14:58:22 (#jwrd) dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8094 -- well, it's not just mispellings but miswordings too. for context, whaack has some ongoing wrist pains (it's in the logs) and is using some STT to give his hands a rest. so some of his output here can be pretty wtf ? for the untrained eye, but it's lulzy for us since we know the context and know him well enoug
[13:48] blakeeus: I'm still in the trainer
[13:48] sourcerer: 2023-07-06 15:01:07 (#jwrd) dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8106 -- nice, there's also vim, but that's a longer term project as a tool to add to you belt. has a steeper learning curve than nano, but brings more leverage once you know it.
[13:50] blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8131 jfw: Yeah, I reached a dead-end while looking for a way to make the task "easier / faster". But now I realize why it should me done with man power and not machine power
[13:50] sourcerer: 2023-07-06 16:59:54 (#jwrd) jfw: software problems can be fixed, but it tends to be quite labor intensive (and skilled labor too); so at a certain point it might make sense to look into, but not before even gaining the experience of doing it the simple way.
[13:51] blakeeus: jfw: Exactly.
[13:51] sourcerer: 2023-07-06 17:14:15 (#jwrd) jfw: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8114 - indeed the miswordings are the worst, for being the most subtle. basically all the present "AI", from the humble assistive onscreen keyboards to the massive neural networks, operates without any grasp of *meaning*, merely looking for ~ highest probability match from a noisy sample or "sounds human-like"
[13:54] blakeeus: jfw: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8142 What I have been doing is spliting my screen between the nano text editor and the video. I just type as I listen, but, of course, I have to frequently pause or replay segements to make sure I wrote everything down correctly.
[13:54] sourcerer: 2023-07-06 17:21:27 (#jwrd) jfw: blakeeus: what was/is your process like there?
[13:55] blakeeus: I'll give it a look -- jfw
[13:56] blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8149 Glad to be here
[13:56] sourcerer: 2023-07-06 20:19:01 (#jwrd) whaack: Hey blakeus good to see you here
[14:14] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8161 - that's how it goes, indeed; so what you can do is make sure those frequent actions (play, pause, replay) are as efficient as reasonably possible
[14:14] sourcerer: 2023-07-07 13:54:05 (#jwrd) blakeeus: jfw: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8142 What I have been doing is spliting my screen between the nano text editor and the video. I just type as I listen, but, of course, I have to frequently pause or replay segements to make sure I wrote everything down correctly.
[14:17] jfw: for instance, last time I did this I worked out a vim configuration to bind some function keys so I could use them in a single keystroke without leaving the editor or leaving the main keyboard area. for another step upscale there's foot pedals too
[14:49] blakeeus: Hmmm, interesting, that's cool. For now though I think I'll just stick to my way of the traditional play/pause/rewind technique.
[16:20] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8153 -- exactly, good point.
[16:20] sourcerer: 2023-07-07 13:46:57 (#jwrd) blakeeus: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8114 dorion: Yeah it would just add more work since I would not only have to listen to the video, but edit the monstrous text it "gifted" me.
[16:22] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8168 -- ever known anyone to use foot pedals though ? lolz.
[16:22] sourcerer: 2023-07-07 14:17:46 (#jwrd) jfw: for instance, last time I did this I worked out a vim configuration to bind some function keys so I could use them in a single keystroke without leaving the editor or leaving the main keyboard area. for another step upscale there's foot pedals too
[16:46] jfw: dorion: yes
[16:46] jfw: my mom & colleagues who did extensive transcription work
[16:48] jfw: granted this was back when the audio came on a cassette tape so it was a player with integrated pedals or some such, wouldn't have been possible to hotkey it
[17:02] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8134 -- I've checked it into a new subdir under training/key-management/ , sorry for the delay.
[17:02] sourcerer: 2023-07-06 17:08:33 (#jwrd) jfw: dorion: http://jfxpt.com/2023/jwrd-logs-for-Jun-2023/#7956 - when do I get to see the results?? I'm anticipating this new kind of look in the mirror, "omg do I really sound like THAT? did I really say THAT?"
[18:42] jfw: ty dorion.
[18:48] jfw: blakeeus: on a scale of one to five, how confident would you say you are in the accuracy of your output, as in capturing the correct words first of all and then spelling them correctly? (It's understood that there is some "transcriber's discretion" and it's usually proper to leave out the vocal filler like ums, uhs, repeated words and the like.)
[18:50] jfw: for a first level statistical takeaway, apparently between the three of us we spoke upwards of 16k words in that two hour span, which'd be about twice my longest blog article!
[19:07] jfw: but in nausea news, the dovecot wiki "docs", which despite the token man pages for the executables, would seem to be the *only* docs for the configuration file, are just as wikipedious as their name suggests - authoritative sounding but with factually incorrect tidbits sprinkled in designed to make the reader end up as dumb as the author.
[19:07] sourcerer: 2023-07-06 18:13:14 (#jwrd) jfw: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8138 - to further belabor this point, it means that AI output is *at best* wikipedia, and unless you're very sharp indeed your chances of noticing when you're being fed sewage are not good.
Day changed to 2023-07-08
[14:49] sstacks: blakeeus: thanks for your collaboration on the transcriptions of the recordings!
[14:50] sstacks: jfw: im changing my ISP next week. This will be in anyway troublesome with the edge router?
[22:35] jfw: sstacks: I've worked with computers (and ISPs) for too long to assure you that any change will not be troublesome in any way; still, nothing in particular comes to mind to beware. who's the new ISP?
[22:36] sstacks: cable&wireless
[22:36] jfw: the fibrafast thing?
[22:36] sstacks: Nah, on my building that isnt enabled yet
[22:37] jfw: dsl then?
[22:37] sstacks: Yes
[22:39] jfw: ok; I don't have experience with that service from them. ideally, they won't force you to use their own router/wifi but rather have some type of modem with single ethernet port; then you'll have the option of using the ERL as the top-level router and putting wifi (if needed) below it on the untrusted port.
[22:41] jfw: basically there's less to go wrong in that configuration. but otherwise it should still work fine to put the ERL below whatever other router, technically that means a double NAT.
[22:44] jfw: I did however have ill experience with that company in terms of any capacity to communicate with someone who has a clue about networks.
Day changed to 2023-07-10
[04:33] blakeeus_: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8180 jfw: On a scale of 1-5 of how confident I feel on the output... I would rate it a 3.5-4.0
[04:33] sourcerer: 2023-07-07 18:48:29 (#jwrd) jfw: blakeeus: on a scale of one to five, how confident would you say you are in the accuracy of your output, as in capturing the correct words first of all and then spelling them correctly? (It's understood that there is some "transcriber's discretion" and it's usually proper to leave out the vocal filler like ums, uhs, repeated words and the like.)
[04:34] blakeeus_: This is because I do leave out repeated words and the "noises/sounds", but some words/phrases are said very quickly and are mumbled
[04:35] blakeeus_: So I have trouble catching exactly what is said the first time I hear it, so I go back and re-listen until I got it. But this still gives me uncertainty of if I was correct
[04:35] blakeeus_: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8181 jfw: That's incredible hahaha
[04:35] sourcerer: 2023-07-07 18:50:37 (#jwrd) jfw: for a first level statistical takeaway, apparently between the three of us we spoke upwards of 16k words in that two hour span, which'd be about twice my longest blog article!
[04:36] blakeeus_: 16k words... wow!
[04:37] blakeeus_: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8182 jfw: Yeah I bet, what is your opinion on the articles dodge report publishes?
[04:37] sourcerer: 2023-07-07 19:07:32 (#jwrd) jfw: but in nausea news, the dovecot wiki "docs", which despite the token man pages for the executables, would seem to be the *only* docs for the configuration file, are just as wikipedious as their name suggests - authoritative sounding but with factually incorrect tidbits sprinkled in designed to make the reader en
[04:38] blakeeus_: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8184 sstacks: No problem! It's kind of my job haha
[04:38] sourcerer: 2023-07-08 14:49:09 (#jwrd) sstacks: blakeeus: thanks for your collaboration on the transcriptions of the recordings!
[10:28] sstacks: blakeeus: I know my friend. Even when someone receives a service, must be grateful
[13:14] dorion: blakeeus, can you paste the yrc error you're getting into http://welshcomputing.com/paste and share it here ?
[14:53] blakeeus_: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8206 sstacks: Very true.
[14:53] sourcerer: 2023-07-10 10:28:11 (#jwrd) sstacks: blakeeus: I know my friend. Even when someone receives a service, must be grateful
[15:00] blakeeus_: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8207 dorion: 14:45:00 <s7g3.jwrd.net> 433 blakeeus Nickname already in use
[15:00] sourcerer: 2023-07-10 13:14:26 (#jwrd) dorion: blakeeus, can you paste the yrc error you're getting into http://welshcomputing.com/paste and share it here ?
[15:00] blakeeus_: 14:48:04 ERROR: connection to jwrd not registered
[15:00] blakeeus_: 14:48:18 ERROR: connect: connection already active for jwrd
[15:00] blakeeus_: 14:48:25 ERROR: connect: no addrs for network jwrd
[15:00] blakeeus_: 14:49:00 ERROR: registration timed out
[15:00] blakeeus_: 14:49:00 connection closed
[15:00] blakeeus_: 14:49:00 reconnecting in 1 s
[15:00] blakeeus_: 14:49:01 connecting to 116.202.223.107:6667
[15:00] blakeeus_: 14:49:01 connection established
[15:00] blakeeus_: 14:49:01 <s7g3.jwrd.net> 433 blakeeus Nickname already in use
[15:00] blakeeus_: 14:49:38 ERROR: can't send messages here
[15:00] blakeeus_: I also pasted it in the website
[15:03] dorion: blakeeus_, lol, but the point of pasting in the website is to share the link.
[15:04] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8220 -- this is your key though. I'm guessing instead of doing `tmux attach` and picking up your yrc in use, you started a new session.
[15:04] sourcerer: 2023-07-10 15:00:34 (#jwrd) blakeeus_: 14:49:01 <s7g3.jwrd.net> 433 blakeeus Nickname already in use
[15:05] dorion: so, quit the yrc that's giving you an error. if you are running that one in a tmux, exit that tmux session. then try tmux attach.
[15:06] jfw: I expect so too; the "no addrs" thing looks odd though as well
[15:11] jfw: blakeeus_, one tip to save you at least a little typing is you can abbreviate speaker names, eg just using the initials (JW, WH, SR)
[15:12] jfw: after writing them out in full the first time they appear in a given transcript
[16:38] blakeeus_: Alright, I'll try that out. Thanks for the tip Jacob.
[16:40] dorion: blakeeus_, what am I, chopped liver ? ;-p
[20:33] dorion: whaack, sstacks, how about office hours via a zoom again this week ? 4pm panama time on thursday. anyone else that's been here is welcome to join. blakeeus, caai, jwm, Barbarian... I think that's it.
[20:41] dorion: was drdb deployed on collin's install ? I see the last commit in the gport was august 2022, but not seeing it mentioned in the pecp reports or discussed in our pm. we were holding board meetings via zoom at the time.
[20:48] dorion: whoops, meant for that to go to jfw pm.. oh well.
[20:52] dorion: for those following the software editions discussion.
[22:39] blakeeus_: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8231 dorion: Sorry, what do you mean by that?
[22:39] sourcerer: 2023-07-10 16:40:45 (#jwrd) dorion: blakeeus_, what am I, chopped liver ? ;-p
Day changed to 2023-07-11
[00:11] jfw: blakeeus_: beats me, sounds like possibly a Seinfeld reference or similar, but I'd guess the intent was to point out that you thanked me for the tip (for which you're welcome) while his tips regarding your irc trouble whooshed right past you.
[00:12] jfw: dorion: I'd be surprised if it's really not mentioned in the reports - possibly it ended up in a more direct email thread - but the answer is yes.
[03:01] blakeeus_: jfw: Ah yes, now I understand. The "Alright, I'll try that out" was meant for him. My bad for being unclear.
[03:26] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8236 <--> chopped liver.
[03:26] sourcerer: 2023-07-10 22:39:16 (#jwrd) blakeeus_: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8231 dorion: Sorry, what do you mean by that?
[03:26] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8240 -- aok.
[03:26] sourcerer: 2023-07-11 03:01:02 (#jwrd) blakeeus_: jfw: Ah yes, now I understand. The "Alright, I'll try that out" was meant for him. My bad for being unclear.
[15:15] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8239 -- eh, you're right, I typo'd my grep.
[15:15] sourcerer: 2023-07-11 00:12:45 (#jwrd) jfw: dorion: I'd be surprised if it's really not mentioned in the reports - possibly it ended up in a more direct email thread - but the answer is yes.
[16:29] jfw: wherein blakeeus sees the value in being specific and dorion sees the valu in careful speling!
[16:31] jfw: and jfw sees the value in checking urbandictionary moar, I guess.
[17:49] sstacks: dorion: If I recover well from the flu, maybe I can make it. Since yesterday ive been feeling pretty bad
[17:53] dorion: sstacks, nice to hear from you, sorry to hear you're under the weather. I wish you a quick recovery.
[22:53] jfw: to recap, whaack can't make office hours this thursday but saturday afternoon might work for both.
Day changed to 2023-07-12
[01:01] jfw: whaack, sstacks: latest video & diagram as well as the session 1 transcript are up.
[01:34] whaack: in scholastic newz, the collegeboard has moved to digital tests for the SAT https://bluebook.collegeboard.org/
[01:38] whaack: it's BYOC. you have to give 'root' access to the app,so it can 'lock you out' of using your computer for cheating
[01:42] whaack: so much lol, https://bluebook.collegeboard.org/students/approved-devices external keyboard approved for ipads but not laptops
[01:47] whaack: No support for any linux distro
[01:48] whaack: and they dont even mention that they dont support linux
[01:57] jfw: does that mean they jailbreak the ipad? :D
Day changed to 2023-07-13
[15:26] sstacks: Morning guys
[15:26] sstacks: dorion: Have BingoBoingo stopped blogging?
[16:11] jfw: sstacks: he took down (or stopped feeding) his blog & news site some time ago. out of curiosity, where did you come across him?
[16:12] jfw: also http://jfxpt.com/2023/jwrd-logs-for-Feb-2023/#6074 , http://jfxpt.com/2023/jwrd-logs-for-Mar-2023/#6185
[16:12] sourcerer: 2023-02-28 03:44:46 (#jwrd) jfw: dorion, whaack: well, BingoBoingo's still online - sorta
[16:12] sourcerer: 2023-03-03 20:26:26 (#jwrd) dorion: http://fixpoint.welshcomputing.com/2023/jwrd-logs-for-Feb-2023/#6074 -- good to see he found himself a full time documentation role he seems to be satisfied with.
[16:47] dorion: jfw, I had linked to him in a swamp sstacks and I inhabit.
[16:49] dorion: sstacks, how's your node syncing going by the way ? have you been keeping an eye on it and running fstrim from time to time ?
[16:49] sourcerer: 2023-04-01 15:48:10 (#jwrd) dorion: also, remember to run, as root, `fstrim -v /home/` every week to improve the longevity of your ssd.
[16:53] sstacks: jfw: yes, Dorion shared a blog post of Boingo on a whatsapp group
[16:54] sstacks: dorion: ok i just issued getinfo, its says 641857 on "block"
[16:54] sstacks: "blocks"
[17:00] dorion: sstacks, notbad. are you getting blocks recently ? you can do `grep SetBestChain ~/.bitcoin/debug.log` ... which will take quite a while if you have the same debug log from the beginning... but nevertheless when it finishes you'll see the timestamp for the last block the node accepted.
[17:00] sstacks: dorion: ill run it now
[17:01] dorion: sstacks, do it as `time grep SetBestChain ~/.bitcoin/debug.log` to measure how long it takes to complete
[17:03] dorion: ftr, I keep a tmux window going with `tail -f ~/.bitcoin/debug.log | grep -E 'ProcessBlock|SetBestChain' so I have an easily viewable, running update on when I got the last good block. it also shows when I'm getting bastard blocks too.
[17:04] sstacks: dorion: i got this from the first command:
[17:04] sstacks: .bitcoin/debug.log:SetBestChain: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 work=4295032833
[17:04] dorion: `tail -f ~/.bitcoin/debug.log | grep -E 'ProcessBlock|SetBestChain'` **
[17:06] dorion: sstacks, that's it ? that looks like the genesis block. it should spit out the report for all 641k+ blocks.
[17:09] sstacks: dorion: yes, i ran this "grep SetBestChain ~/.bitcoin/debug.log"
[17:20] jfw: sstacks, did you run as user or root?
[17:20] jfw: dorion, I don't see the difference in your command correction?
[17:20] sstacks: jfw: root
[17:21] jfw: sstacks: there you go, everything to do with the node needs to be the regular user because that's where the data is
[17:23] sstacks: jfw: darn,wrong about that again. Ran it on user and its loading a bunch of data now
[17:23] sstacks: will report after its done
[17:32] sstacks: log loading still ongoing
[17:33] sstacks: impressive
[21:40] jfw: sstacks: impressively inefficient, haha
Day changed to 2023-07-15
[00:17] jfw: whaack, sstacks, jwm etc, anyone game for that zoom hangout meanwhile moved to tomorrow ?
[00:17] sourcerer: 2023-07-10 20:33:23 (#jwrd) dorion: whaack, sstacks, how about office hours via a zoom again this week ? 4pm panama time on thursday. anyone else that's been here is welcome to join. blakeeus, caai, jwm, Barbarian... I think that's it.
[00:17] sourcerer: 2023-07-11 22:53:29 (#jwrd) jfw: to recap, whaack can't make office hours this thursday but saturday afternoon might work for both.
[17:08] jfw: https://teddit.net/r/DataHoarder/comments/eb9z1q/3ware_9750_on_ubuntu/ Error 429 "Too Many Requests" - looks like reddit finally broke the last usable way of even reading the damn thing.
[18:17] jfw: and meanwhile in "github makes it so easy to grab code", it's no longer able to display source files when you click on them.
[18:20] jfw: the logical progression from no longer being able to serve repositories for cloning, to be sure.
[18:20] sourcerer: 2022-04-03 19:30:00 (#jwrd) jfw: In unsurprising but still aggravating progress, github no longer supports git.
[18:25] jfw: and fitting the theory of how the "platforms" game goes.
[18:31] jfw: the release download links also stopped working some time ago too, in case I didn't mention it yet.
[19:03] jfw: and in further cancerous test suites, designed to fail when run after the year in which it was released.
[20:15] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8293 -- I can see src files on my v88 firefox (have to allow js though), but not v45 firefox.
[20:15] sourcerer: 2023-07-15 18:17:17 (#jwrd) jfw: and meanwhile in "github makes it so easy to grab code", it's no longer able to display source files when you click on them.
[20:17] jfw: dorion: myeah, didn't used to need js.
[20:22] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8298 -- idjits.
[20:22] sourcerer: 2023-07-15 19:03:01 (#jwrd) jfw: and in further cancerous test suites, designed to fail when run after the year in which it was released.
[22:35] dorion: For our July <a href="http://dorion-mode.com/2023/05/the-junto-by-jwrd/">Junto</a> we're returning to TEKA.
[22:35] dorion: <a href="/wp-content/uploads/2023/04/teka-2.jpg"><img src="/wp-content/uploads/2023/04/teka-2-720px.jpg" alt="teka-2" title="teka-2" width="720" class="aligncenter" /></a>
[22:35] dorion: <h3>Details</h3>
[22:35] dorion: <strong>When</strong> : Wednesday, July 26th, 2023 from 5:30-8pm.
[22:35] dorion: <strong>Where</strong> : TEKA, Calle 70, San Francisco, Panama City, Panama
[22:35] dorion: <strong>What</strong> :
[22:35] dorion: <ul>
[22:35] dorion: <li>Happy Hour and networking ;</li>
[22:35] dorion: <li>A ~40 minute presentation by <a href="http://jfxpt.com">Jacob Welsh</a> and <a href="http://dorion-mode.com">Robinson Dorion</a> : <em>Practical and Elite Internet Chat Protocols</em> ;</li>
[22:35] dorion: <li>Social hour and networking ;</li>
[22:35] dorion: </ul>
[22:35] dorion: <strong>Who</strong> : it's open the public, cool people only though.
[22:35] dorion: <strong>Note</strong> : you're expected to consume at least $25 of food and/or drink, which is easy and pleasant at TEKA given the quality they deliver.
[22:35] dorion: <strong>RSVP</strong> : you must RSVP get yourself on the list. Submit the contact form at <a href="http://jwrd.net"</a>jwrd.net</a>
[22:35] dorion: <h3>Themes</h3>
[22:35] dorion: <ul>
[22:35] dorion: <li>Chat has become a dominant form of Internet communication. At the high level, there are two classes of chat systems : protocols and products aka platforms.</li>
[22:35] dorion: <li>What are the costs and benefits of each ?</li>
[22:35] dorion: <li>Most are familiar with products ; Internet Relay Chat (IRC) and <a href="http://ossasepia.com/2022/02/04/whats-so-interesting-about-eulora2/">Eulora2</a> Chat are examples of Protocols. What are these protocols and how are they superior to the various <a href="http://dorion-mode.com/2019/11/jwrd-computing-the-why-how-what-and-way-forward/#footnote_2_153">fast food</a> chat products ?</li>
[22:35] dorion: <li>A demonstration of configuring and using an IRC client.</li>
[22:35] dorion: <li>JWRD is actively contributing to the development of Eulora2, which, at present, is not open to the public. As its owner <a href="http://ossasepia.com/2023/02/17/how-are-things-moving-in-eulora2/#comment-29168">explained</a>, newcomers are best served building up their interactions with people already involved. Thus, this is an opportunity to participate in the meta-game and take steps towards
[22:35] dorion: being allowed in the club.</li>
[22:35] dorion: <li>This presentation builds on the topics covered on prior Junto presentations, namely, <em><a href="http://dorion-mode.com/2023/04/event-why-you-need-passwords-and-how-to-make-them-strong/">Why you need passwords and how to make them strong</a></em> and <em><a href="http://dorion-mode.com/2023/06/junto-how-to-be-a-person-online-the-rsa-algorithm-and-web-of-trust/">How to be a person online: the
[22:35] dorion: RSA algorithm and Web of Trust</a></em>. JWRD is committed to helping people dissatisfied with being <a href="http://dorion-mode.com/2023/06/junto-how-to-be-a-person-online-the-rsa-algorithm-and-web-of-trust/?b=If%20you%20don&e=#select">Internet peasants</a> save time and money in transforming themselves into people.</li>
[22:35] dorion: </ul>
[22:35] dorion: TEKA is located on Calle 70 in Panama City's San Francisco neighborhood, have a <a href="https://goo.gl/maps/2RuuQe8jCPVSRZ727">map</a> :
[22:35] dorion: <a href="/wp-content/uploads/2023/04/teka-3.jpg"><img src="/wp-content/uploads/2023/04/teka-3-720px.jpg" alt="teka-3" title="teka-3" width="720" class="aligncenter" /></a>
[22:35] dorion: <em>Salud y nos vemos alla</em> !
[22:35] dorion: oh shit.
[22:36] dorion: I thought I had the url on my buffer. ffs. sorry !!!!
[22:38] dorion: so so 31337, lolz.
[22:42] jfw: tl;dr.
[22:43] dorion: jfw, better to read the article anyways. easier on the eyes !
[22:46] jfw: it's also getting a lil repetitive, though I suppose that's fine given what it is.
[23:11] dorion: jfw, agreed. one way to change it up a bit would be to go to a different venue, which I'm open to and perhaps will move on for august. but on the other hand, teka has been real solid.
[23:12] jfw: heh, I just meant the text of the article.
[23:13] jfw: I'm likely to be out traveling Aug-Sept.
[23:49] dorion: yup, but I plan to still have'em.
Day changed to 2023-07-16
[03:43] dorion: http://dorion-mode.com/2023/07/so-i-kissed-a-frog-and-didnt-turn-into-a-prince-but-had-a-long-look-into-the-abyss-and-managed-to-survive-so-let-me-tell-you-about-it/
[03:57] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8337 -- I agree it's getting repetitive and that it's also fine and maybe as it should be. I'm using a template to write the articles, which obviously makes it easier to produce them. I also think makes it's easier for people to process the info and decide if they want to come. I don't reckon changing the style is going to affect if people come.
[03:57] sourcerer: 2023-07-15 22:46:51 (#jwrd) jfw: it's also getting a lil repetitive, though I suppose that's fine given what it is.
[03:57] dorion: they're either interested and available and come or not.
[16:56] jfw: the what it is I had in mind is basically more of a publicity flyer than an "article" proper. it's more meant to stand on its own with less reliance on being consumed as part of a larger whole, which is how the repetition/automation could be justified - 'static linking'.
[16:56] sourcerer: 2023-07-15 22:46:51 (#jwrd) jfw: it's also getting a lil repetitive, though I suppose that's fine given what it is.
[17:03] jfw: and to the matter that my 3ware and strace links were hinting at - we now (finally) have full control of the hardware RAID card in our server "s6" that's been sitting on the shelf, straight from its Gales Linux operating system living atop said RAID card, removing the need to deal with the various miseries of BIOS based configuration utilities.
[17:05] jfw: sub-quests produced indeed an strace gport and got openbsd's ftp-proxy working on our PF firewall setup.
[17:06] jfw: moreover, this was motivated by finally finding a promising local datacenter where to park the server.
[17:15] jfw: up next there (besides further negotiation) is to test the feasibility of running a bitcoin node on it. conventional wisdom has it that one "needs" an SSD for that, but then this is a RAID-10, with battery backed write cache and oodles of RAM on the server for read cache, so it'll be a new data point for me.
[17:15] jfw: that's Metric oodles, of course, to be specific.
[19:26] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8346 -- so you're suggesting just publishing flyers likes this ? where do you suggest we announce publication of the videos and slides and photos from the event ? not to mention
[19:26] sourcerer: 2023-07-16 16:56:52 (#jwrd) jfw: the what it is I had in mind is basically more of a publicity flyer than an "article" proper. it's more meant to stand on its own with less reliance on being consumed as part of a larger whole, which is how the repetition/automation could be justified - 'static linking'.
[19:26] dorion: [http://dorion-mode.com/2023/06/junto-how-to-be-a-person-online-the-rsa-algorithm-and-web-of-trust/#comment-4474[comments] people might want to leave. also, we're using the contact form for RSVPs, which we can link to in an article, but not on a flyer.
[19:27] dorion: another thing is if it's an article I can leverage the url direction/completion in mp-wp whereas if it's a file under uploads or similar it doesn't work. furthermore, with articles, it easier for people to find the history.
[19:29] dorion: jfw, what makes you say the junto is meant to stand on its own ? as far as I see it, it's an entry point to get people consuming/contributing to the larger whole.
[19:30] jfw: dorion, I don't think you're following my meaning
[19:30] dorion: at this point, I don't really see and advantages of a flyer vs article because flyers will get repetitive too.
[19:31] jfw: again, not suggesting it should be somewhere different or in some different style; I was attempting to better name the essence of what those items are, even if technically speaking they're in "the blog which is the place where articles go and therefore they're articles"
[19:34] jfw: I'm describing not prescribing, in other words.
[19:35] dorion: jfw, I doubt I am taking your meaning. ok.
Day changed to 2023-07-17
[14:25] dorion: blakeeus, http://welshcomputing.com/paste/hrzedr4i32
[14:45] blakeeus: http://welshcomputing.com/paste/xxht6h8x8g ,dorion:
[15:00] dorion: mysterious scribblings ? secret codes ? poems, no less.
[18:14] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8292 -- there's still the archive method.
[18:14] sourcerer: 2023-07-15 17:08:31 (#jwrd) jfw: https://teddit.net/r/DataHoarder/comments/eb9z1q/3ware_9750_on_ubuntu/ Error 429 "Too Many Requests" - looks like reddit finally broke the last usable way of even reading the damn thing.
[22:05] jfw: dorion: ah, ty. in that case not sure why I started using teddit... maybe just slowness of the archive route
[22:26] dorion: jfw, well, teddit did work for a time. I think there are multiple instances of it.. didn't look into it though since not finding myself needing it really at all.
[23:49] jfw: yeah, the "need" has usually been when there's some search result (see, they happily serve their plain-text to search robots - NOT to humans!) and "I'd better not leave this stone unturned", which then ends up quite as seen here, someone with a simimlar problem being answered if at all by others with no clue.
[23:51] jfw: no clue of value at least; the "try another version" seen there was the ticket indeed but something that had already occurred to me to try much earlier.
Day changed to 2023-07-18
[01:57] jfw: sounds like the progress in ussrization of the ussa has come far indeed - I'm hearing of 9 months wait for a routine dental cleaning, similar for assorted specialists, "8-13 weeks" ETA for passport renewal which estimate doesn't decrease as the weeks tick by
[02:07] dorion: yeah, I hear you, I know you know reddit sux donkey dick.
[02:07] dorion: hm, I renewed my passport by mail via the embassy here and got in back in a week, iirc. maybe 2 weeks tops.
[03:43] dorion: http://dorion-mode.com/2023/07/hey-you-hipster-morons-why-do-you-want-thinking-people-to-hate-you-so-much-theyd-not-piss-down-your-throat-if-your-guts-were-on-fire/
[03:51] jfw: dorion: pretty good re passport, perhaps just the resident inmates get the "when we feel like it" treatment
[03:51] jfw: curious how it goes for whaack too
[23:09] dorion: how ya doin' sstacks ?
Day changed to 2023-07-19
[23:18] jfw: whaack: have you done any further looking into servers, perhaps something to bring back on this trip? because it's looking like we're moving on this sooner rather than later.
[23:18] sourcerer: 2023-02-22 01:42:24 (#jwrd) whaack: yes, i was planning to do that here in CR, but i'd be happy to host my box in Panama. I may be fine with you guys obtaining the box, I was interested in colocating partially for the learning experience.
[23:18] sourcerer: 2023-07-16 17:06:38 (#jwrd) jfw: moreover, this was motivated by finally finding a promising local datacenter where to park the server.
[23:21] jfw: need to work out the details but we'd be looking at something on the order of 200 usd per month per rack unit including power and 10mbps bandwidth
[23:24] jfw: the ISPs there provide dedicated bandwidth, so the more clients we can get, the more capacity we'd have for them to share, and at a certain point we could get a half or full cabinet which would reduce the "per slice" cost
[23:27] jfw: whaack: if you wanted to try running on an apu1, we could set that up for you fairly soon, with SSD and FUCKGOATS builtin
[23:31] jfw: it's unclear yet if/how one can be squeezed in a single rack unit, due to the bulky power adapter; so might be a thing where we have to buy 2U and then put in a bunch of them.
[23:38] jfw: one rack unit is 1.75" or 44.45 mm in height, from what I gather (and verified approximately)
Day changed to 2023-07-20
[21:15] dorion: !e view-height
[21:15] btcexplorer: block_height: 799571
[21:15] btcexplorer: mins_since_last_block: -11
[21:15] dorion: we're almost at 800k, exciting times.
[21:26] jfw: 840k would be more exciting I'd think
[22:10] dorion: well, yeah.
[23:01] jfw: you around, sstacks?
Day changed to 2023-07-21
[21:32] jfw: http://jfxpt.com/2023/that-frog-prince-story-as-seen-from-the-home-castle/
Day changed to 2023-07-23
[21:16] dorion: http://dorion-mode.com/2023/07/the-root-of-our-dispute-is-i-value-substance-over-form-and-thus-manage-to-learn-and-grow-while-you-cling-to-form-and-thus-dwell-in-mediocrity/
Day changed to 2023-07-24
[04:15] jfw: !e view-height
[04:15] btcexplorer: block_height: 800006
[04:15] btcexplorer: mins_since_last_block: -14
[18:56] dorion: fyi : http://dorion-mode.com/2023/07/junto-practical-and-elite-internet-chat-protocols/#comment-4505
[22:24] sstacks: hey guys, how is it going
[22:27] sstacks: Ive heard several times in the past that node runners can reject suspicious (malicious?) transactions. With the limited understanding I have, I know this is possible in theory. But in practice, how this is achieved in the practice? I guess im wondering about how to run actively a node, rather than passively.
[23:44] jfw: hi sstacks, it's going alright, how about you?
[23:46] jfw: in principle you could edit the code of your node to filter transactions based on anything computable; in practice it certainly filters already by a number of criteria, some configurable.
[23:47] jfw: what sort of thing do you have in mind as suspicious/malicious? because by themselves those don't seem like particularly well defined things
[23:48] jfw: note that in bitcoin, if a transaction is valid and gets included in a block then by definition it is legitimate
[23:49] jfw: that is, the key is the owner of the bitcoin and its signature is sufficient proof of the owner's will
[23:52] jfw: hence possibly why people uncomfortable with this stark reality gravitate toward "segregating witnesses", "third keys" and the like, anything to dilute the unfair!! power of the key
[23:56] sstacks: jfw: hey my friend. Doing great, thank God. So when I said "malicious" was thinking in the hypothetical case in which a single entity manage to acquire most of the hashing power, enough to manipulate the ledger.
[23:58] jfw: ah, there's nothing you can really do there from a technical approach, no. you could tune out the world basically but that doesn't make it stop being what it is.
[23:59] jfw: how's one to judge whoat's a "single entity" for instance?
[23:59] jfw: whoat's, lol. who's, or what's.
Day changed to 2023-07-25
[00:00] jfw: that's the heart of the sybil attack
[00:09] jfw: there is perhaps of interest http://trilema.com/2016/the-necessary-prerequisite-for-any-change-to-the-bitcoin-protocol/
[17:14] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8401 -- one thing you might notice in your debug.log is "ERROR: AcceptToMemoryPool() : nonstandard transaction type" ; this is because the reference implementation doesn't recognize the softfork transactions, e.g. multisig and segwit. as I understand, the effect is that we don't pass these transactions along to our peers because it's essentially spam.
[17:14] sourcerer: 2023-07-24 22:27:03 (#jwrd) sstacks: Ive heard several times in the past that node runners can reject suspicious (malicious?) transactions. With the limited understanding I have, I know this is possible in theory. But in practice, how this is achieved in the practice? I guess im wondering about how to run actively a node, rather than passively.
[17:14] dorion: due to the backwards compatibility of the softfork, when miners include those in a block, the block is valid.
[17:17] dorion: HOWEVER, when the miners decide to stop censoring the ANYONECANSPEND transactions and take the money that's lying on the table, our nodes won't flinch because those are valid transactions, per the protocol.
[17:23] jfw: dorion is correct; the 'standard' criteria are more strict than 'valid' but apply only to transaction relay (technically: accepting into the local memory pool), otherwise anyone with a different idea of 'standard' would go onto their own fork. another criterion is the -minrelaytxfee.
[17:26] jfw: messing with the "standard" rules is also pretty obnoxious though, eg the whole -lows/-highs business comes about because peers sometimes won't relay signatures that naturally come up in the high-S form (a sort of weak mitigation effort for transaction malleability)
[18:17] jfw: sstacks, I recall you had the homework saved last time but not sent, is that still the case or did I miss it?
[18:41] dorion: sstacks, the bitcoin codebase we inherited was in fact more defensive against hostile nodes that sent heathen commands, i.e. it disconnected from node that spoke heathen to it. the permissive mode vpatch gives the operator the option to 'slut it up' a bit and not immediately disconnect from heathens. the
[18:41] dorion: upside of which is better connectivity and we've not observed much downside.
[18:44] dorion: whaack reported trouble maintaining sync with the tip, until he applied the permissive mode and now it appears he's staying in sync.
[18:44] sourcerer: 2023-02-21 14:20:08 (#jwrd) whaack: dorion: per your suggestion i updated my bitcoind to contain jfw's permissive patch. after restarting bitcoind and letting it sync last night, i got considerably closer to the chain tip, but as of writing i seem to be stuck at block 777598 http://explorer.ztkfg.com/?args=view-height
[19:04] sstacks: hey guys, sorry, just got back to the desk. Thanks for responses.
[19:06] sstacks: jfw: http://welshcomputing.com/paste/wruaxyn443, this is the last hw
[19:07] dorion: sstacks, you're welcome.
[19:56] jfw: dorion: well, one upside of *not* using permissive is you get a better picture of what peers are running compatible nodes.
[19:57] jfw: eg, I'm running it now and used it for validating my recently updated list
[19:58] jfw: *running without it i.e. disconnecting noncompliant peers (which is arguably more polite than silently failing to accept valid transactions, too)
[21:22] sstacks: http://welshcomputing.com/paste/vifjbqj88z
[22:37] sstacks: shttp://welshcomputing.com/paste/vifjbqj88z session 15 hw
Day changed to 2023-07-26
[13:31] dorion: jfw, good point about getting a better picture, but as far as being polite to noncompliant nodes, I don't see how they've earned politeness. I keep connections with them because they'll relay valid transactions and perhaps provide better connectivity to the mining cartel, but why do I care if it's not polite to relay their bullshit ?
[13:32] dorion: they're there to be used, literally, fuck them. tear open, enjoy contents, discard husk.
[13:54] jfw: dorion, did I say they'd earned politeness?
[13:54] jfw: far as I know I was speaking of ontology not ethics
[13:57] jfw: "why do I care if it's not polite to relay their bullshit ?" - I'm really not sure what you're responding to there.
[14:23] jfw: hmm, also note the linked article describes that TO-CE-HD as the chief male fantasy then goes on to say that living one's fantasies is the surest road to unhappiness.
Day changed to 2023-07-27
[21:45] jfw: in my quest for bread baking improvements, 'Chocolatisimo' had some good selection of wooden utensils and mason jars, among the mountains of bulk plastic clamshells; ingredients though were nothing special for my purposes. lots of prefab dessert ingredients for convenience. no vanilla beans, the usual extracts only. hundreds of pounds of King Arthur flours in bulk bags - but the whole wheat ones
[21:45] jfw: were 14 months old and the refined ones were 'enriched' in the fine print. they also re-pack it down into 5lb bags, which are duly marked as being packed just the other day! the second degree of freshness, what more could I want.
[22:05] sstacks: "Chocolatisimo" is located at Albrook Mall right?
[22:05] sstacks: I have the store's sign in my head, but cant remember the location.
[22:29] jfw: sstacks: this one was via porras at the corner behind pricesmart.
[22:30] sstacks: jfw: Yes! Besides Panabrisas or something like that
[22:31] jfw: not sure, it had most of the streetfront signage to itself.
[22:32] jfw: how's the dog-training, sstacks?
[22:35] sstacks: jfw: It was good, now im heading to El Ingenio to pick up my wife from a friends house.
[22:36] sstacks: We had the training at home, since he has been behaving badly with visitors.
[22:36] sstacks: Anticipating rain as well, since day was greysih
[22:38] jfw: behaving badly like barking/hostile or too excited/jumping on them or what?
[22:40] sstacks: jfw: excited/jumping kinda thing.
[22:42] jfw: aha. pretty limited in my knowledge here but I'd guess the approach would be calming voices & body language, maybe redirect attention with smelly treats
[22:43] jfw: only giving them once calmed down, of course
[22:44] jfw: I gather dog training requires some degree of owner training too since it requires long-term consistency
[22:46] jfw: I guess the "sit" is relatively easy to train and would be naturally calming
[23:39] sstacks: im back
[23:42] jfw: sstacks, I'm here but not much longer - did you have anything to discuss from the course?
[23:47] sstacks: jfw: Indeed, you're not wrong at all. We both have been training. Thats one of the reasons I chose this trainer back in the day (when I first started the training during (illegal) lockdowns). He insisted on my indispensable active participation on the process, so it would be sustainable over time. My wrong doing was quitting the training after release.
[23:55] jfw: nice. that point about the lockdowns being illegal, not sure I heard it before though it sounds quite possible, I have heard that most of those random police checkpoints are illegal
[23:56] jfw: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8457 - we wrapped that up by zoom call, ftr.
[23:56] sourcerer: 2023-07-27 23:42:29 (#jwrd) jfw: sstacks, I'm here but not much longer - did you have anything to discuss from the course?
Day changed to 2023-07-28
[13:01] sstacks: morning guys
[13:02] sstacks: jfw: indeed, most police checkpoints are illegal. According to law, there's a couple requisites they must meet to be legit. Most of those random checkpoints arent legit.
[15:07] jfw: heh, reminds me of this flap among the campus feminists back in my university days when some politician on the pro-life side of the abortion fray spoke the phrase "for cases of legitimate rape..."
[20:55] sstacks: jfw: Hahaha!!
[20:56] sstacks: jfw: casually, today were a crash between two cars via Veracruz caused by: a speeding dude and a checkpoint near a curve.
[20:59] jfw: To Protect And Swerve.
Day changed to 2023-07-29
[01:38] dorion: Barbarian, mind dropping a line here in the coming days ? we want to talk to you about a hosting offer.
[01:40] dorion: whaack, that goes for you too.
[01:43] dorion: http://jfxpt.com/2023/jwrd-logs-for-Jul-2023/#8467 -- I tell ya folks, this guy is full of zingers today. lol.
[01:43] sourcerer: 2023-07-28 20:59:34 (#jwrd) jfw: To Protect And Swerve.
[01:44] jfw: that one's not original but happy to pass it down.
[01:46] dorion: a snippet from behind the mighty walls of e2 earlier today.
[01:50] jfw: indeed, it seems it was that indeed (assumed we're using the same green-energy flourescent tube servers as everyone else in town) and the deal is still open just with higher than anticipated costs.