267d 10h 23m74d 15h 6m42d 16h 5m61d 1h 37m1d 19h 15m13d 3h 22m1d 2h 41m6d 5h 32m148d 8h 13m

BingoBoingo: diana_coman: Comment's responded to, avatar.png replaced, planning started
whaack: diana_coman: ahh.. I can't help but think you will get some joy out of reading this message. Not because you wish me ill but because you'll be glad luck didn't prevent me from being punished for a mistake. The RAV4 is currently out of operation on the side of the road near my surfpal's house. The dashboard lights went haywire and something felt very off with the transmission as I was dropping him
whaack: off at his place. After I turned off the car it would not start again.
whaack: diana_coman: EOD Report G: I took the time to pay the debt of not setting up backup systems on my new computer. When mounting my HDD I had a few questions that lead me to reading about the ext4 file system and GPT (GUID Partition Table). WTI: When I have a specific question, instead of just trying to answer that question, try to find out what is the broader misunderstanding and learn that topic.
whaack: B: I used a command, mkfs.ext4, on my hdd before fully understanding the command. Now my hdd is not listed in /dev/ and I don't know why. WTI: I don't know what to say. Obviously, don't use commands before understanding what they do.
jfw: whaack: I get the idea you're talking about an external hdd, maybe usb, though you don't say so. Normally mkfs shouldn't make device nodes come and go or even change the partition table at all. Checked the syslog + kernel log?
jfw: re the car, yeesh, electrical AND transmission problems at once? Might help to provide some detail on "haywire" and "felt very off"
jfw: and "would not start" too, lol. Wouldn't crank at all? Any lights?
diana_coman: - lmao; should I even ask if you checked the battery at least? (if you even have what to check it with...?) ; but surely the taxi-pal sorted it all out by now, right?
ossabot: Logged on 2020-02-21 22:16:05 whaack: diana_coman: ahh.. I can't help but think you will get some joy out of reading this message. Not because you wish me ill but because you'll be glad luck didn't prevent me from being punished for a mistake. The RAV4 is currently out of operation on the side of the road near my surfpal's house. The dashboard lights went haywire and something felt very off with the transmission as I was dropping him
diana_coman: I hope the surfpal at least rubbed it in properly since it's amply deserved.
diana_coman: whaack: I see a great day of lulz!
diana_coman: - you know, maybe his car is running windows?
ossabot: Logged on 2020-02-22 00:17:37 jfw: re the car, yeesh, electrical AND transmission problems at once? Might help to provide some detail on "haywire" and "felt very off"
diana_coman: - glad to hear it! (and I can quite picture it too, heh)
ossabot: Logged on 2020-02-21 16:38:07 jfw: And regarding the wallet. That was the fitting of the keystone into a bridge quite some time in the making, I carried a Cheshire cat's grin upon considering it all.
diana_coman: BingoBoingo:
diana_coman: BingoBoingo: do write up your plan with concrete tasks you aim to do over the next week; you can choose your deadline as it suits you on this but my reading window for those is most usually Monday morning UTC
diana_coman: BingoBoingo: from that comment, you actually have in there quite some seeds for at least one part of your qntra strategy and otherwise re steps for automation (and in general for tasks) - you need to identify what are the machine-tasks essentially ...
diana_coman: ... as opposed to "take a browser"
diana_coman: BingoBoingo: for all new stuff, the iterative learning process goes 1. make a draft 2. ask for feedback 3. implement feedback to have another version of the draft 4. repeat from 2 until feedback comes back ~it's fine.
diana_coman: and for everyone else struggling with new/never-did-before-stuff, seriously, the above ^
BingoBoingo: diana_coman: Thank you, I'll start with my deadline set at 23:59 UTC on Sundays.
BingoBoingo: Unloading the unproductive sort of urgency that had been congesting the brain has been a great help in backing out of the "throw things, test against what sticks" process into "pause and read docs"
BingoBoingo: In other news, a number of visible trb nodes have been wedged for some time.
BingoBoingo has this sort of soft, squishy hypothesis that too many folks setting their version string at 99999 and not enough trb nodes set at lower 50400 to 70001 versions strings leaves the network vulnerable to getting congested with oversized segwit blocks from out of WoT nodes.
jfw: BingoBoingo: I was just noticing my own not getting blocks (even bastards), upon attempting to use it for some testing. I haven't taken a systematic look but I have the notion this happens with some frequency, contrary to some claims that the sync worx fine
jfw: I've been known to swap in a non-malleus_mikehearnificarum build when this happens and presently that seems to have worked.
BingoBoingo: jfw: My one node that survived this event was running version flag 70001
jfw: I'm flying the jolly 99999 roger
BingoBoingo: jfw: The uncomfortably squishy part is that both of these solutions broaden the space of "heathen" nodes that could hand over a valid block.
BingoBoingo: jfw: Maybe it's the case I've got some projection leaking into this thought, but the trb-verse problem seems to have parallels to the Qntra problem in a sort of defensive stagnancy coupled with bravado obscuring a lack.
BingoBoingo: Differently framed: While the potential code problem may be more attractive, there seems to be a network graph problem that's consistently escaped notice.
jfw: BingoBoingo: manpower at least is a none-too-obscured lack
jfw: as far as stagnancy, I've certainly felt the lack of basic stuff like getblock, getrawtransaction and sendrawtransaction. And documentation of ~anything.
diana_coman: BingoBoingo, jfw well, there's been ~0 work on trb for quite a while and moreover nobody really owns it explicitly to start with.
diana_coman: jfw: what's your status/plan for the plan & review this week?
diana_coman: also, is the writing again stuck or falling by the wayside due to focus on the wallet or what?
jfw: diana_coman: I need to check on plans this evening; depending on that I'll do the review then or tomorrow.
diana_coman: jfw: in other words, most likely similar to last week, lolz.
jfw: diana_coman: I think the writing vs. wallet has been more a matter of resistance to getting started and turning to other work to at least get something done. I have things to write on too, just need to buckle down and do it
diana_coman adds to the list of things to ponder just wtf are deadlines such a difficult thing for others.
diana_coman: dorion: where are you with all the pending stuff anyway?
diana_coman: lobbes: how's the server setup, is it really going to eat up the whole weekend+ ?
diana_coman: jfw: honestly, I'm really happy to hear of your progress on the wallet; there is at least that.
jfw: thanks diana_coman, glad to hear it.
jfw: better if more progress on 'fixing my head' too as BingoBoingo puts it, I know.
diana_coman: myeah; I guess I might need to look for a bigger hammer in the end, dunno.
diana_coman: jfw: do tell me something - is the wallet work otherwise really taking up all time/mind-space or is it just that there's ~always something else found to fill the non-wallet space or what exactly?
jfw: it doesn't soak up all the time, no. so as to what does... I guess it's reading or thinking but not being efficient about it
diana_coman: jfw: did you figure out any usefulness for those weekly reviews?
diana_coman: jfw: the above is re this comment
jfw: diana_coman: I haven't taken a proper look at them; but at least they get me to look closer at what's going on and keep a record
jfw: kinda looks like I ignored the comment, huh. I didn't exactly; thought "that's a good idea, I should take the time to do those things"; but then didn't make the time
diana_coman: yeah, all the good intentions, I know.
whaack: diana_coman: revised outline in a tree structure. There is room for improvement, but this is what I could produce in 2 hours. I tried to make every node in the tree be a statement that somehow supports / explains its parent node. For the formatting, I used emacs org mode syntax and added a new line everytime the next node was higher in the tree than the node on
whaack: the current line.
whaack: jfw: All the warning lights on the dashboard went on, the fuel guage / spedometer all dropped to E/0, and the radio turned on/off repeatedly.
diana_coman: whaack:well, structure is better; content, uhm; listen, "links to parent node" is one thing, but *how* it links is more important, lolz.
diana_coman: whaack: for example, just what/why is jwrd now all of a sudden a ...reason??
diana_coman: what is this, fashion or thinking?
whaack: jfw: It's hard to remember what specifically happened with the transmission. The car seemed to switch gears abruptly. It lunged forward abruptly as I was either slowing down or speeding up.
diana_coman: whaack: have a look at this re-write of your first points there:
diana_coman: whaack: do you have any sort of warranty or insurance for this sort of thing?
diana_coman: or what's your plan there anyway?
jfw: whaack: sounds like possibly not a matter of switching gears but the engine losing/regaining ignition which would fit with the electrical symptoms. Still you'll need someone who knows where the alternator is to troubleshoot I imagine, not really sounding like a novice job
diana_coman: whaack: re outline, basically you have a topic (building that local otc network) and then you have clear subtopics that flow naturally, the why build it, the *how* build it at the very least, possibly the previous experience to the extent that you use it to add to the discussion rather than just sticking it on the side.
whaack: diana_coman: I put jwrd there because I see their business model as a great example of building a network of motivated people. But I see that doesn't quite make jwrd a "reason" to build out a btc otc network
diana_coman: whaack: so sure, it can go as example and source of inspiration but it's not a reason, no.
whaack: diana_coman: No I don't have warranty or insurance on the car. I am going to take it to the mechanic on Monday.
diana_coman: whaack: kind of hard to imagine though that this somehow just happened now the first time or something, huh.
whaack: diana_coman: right. Given I bought it used recently the probability this is a serious problem and not something simple like a broken alternator is much higher.
diana_coman: whaack: re that past experience with otc, if you want to focus on it as such, it probably makes an article on its own of the sort "lessons learnt" or "funny recollections" or whatever; but if you stick it in this one, then it's likely it can go either as concrete examples/supporting evidence to/for some points/choices you make or otherwise possibly *against* not taking other paths, not sure I see atm other places where it would ...
diana_coman: ... easily fit as such.
diana_coman: whaack: do you see the core difference between your points and my re-write there?
whaack: diana_coman: I heavily considered making it its own article and/or taking it out of this one.
diana_coman: whaack: so what are the reasons why you decided it better goes in this article then?
whaack: diana_coman: I was thinking about excluding it because I wasn't sure if it fit in the article. Then when I thought "oh i see, I can include it as a list of things to remember going forward" I decided to stick it in. I can see now that I munged it so it fit.
diana_coman: whaack: that is also *not* at all "heavily considered", lolz.
diana_coman: whaack: out of pure curiosity, just what would be "lightly considered" if the above is the heavy version?
whaack: diana_coman: the adverb is useless.
whaack: and misleading
whaack: internally I thought "leave it in.. no no take it out... no leave it in.. no no take it out" about 2-4 times, instead of just once
diana_coman: the poor adverb is just misused really; and otherwise the misuse is -unsurprisingly- not helping you at all, no.
diana_coman: whaack: that is called "I hesitated on whether to include it or not and couldn't make up my mind"
diana_coman: nothing to do with an actual consideration at all really.
whaack: yes, that is the proper way to phrase what I did.
whaack: I'm working on obtaining a good understanding of the difference between my outline and your revision
diana_coman: whaack: try to add/continue on that revision, at any rate.
whaack: diana_coman: The main difference I see is that your outline does a better job at making sure the content is in line with the tree structure. Specifically, in your outline it is clear how a child node relates to ALL of their parents, not just their immediate parent.
diana_coman: whaack: hm, that is given once you do it properly (because guess what, you are related to your grandparents too, not only to your parents, lolz)
diana_coman: whaack: deeper levels should detail (various aspects of) the higher levels, it's not just this sort of superficial "related" as in "oh, if I can find *something* in common then they are related"
diana_coman: and that is really the deeper difference - your outline just mix-and-matches stuff; despite its pretended tree structure, it's still as flat and 2d as it can be; it's not a tree, but at most an image of a tree.
diana_coman: whaack: if it helps, perhaps think of it as a boxes-inside-boxes structure, that's how it works, you should be able to open it up/close it to any level and it should still make FULL sense.
whaack: diana_coman: Okay. The error began with my process at looking at my previous outline and thinking "how do I treeify this". I believe I understand what you mean by the boxing/unboxing. (Org mode actually has the ability to hide/show the contents under any asterisk level)
whaack: diana_coman: I don't know if I fully understand what it means for a point to detail a higher level. How does "why build it?" detail "build a local btc network in guanacaste". I see various types of nodes. Some (like why build it) must be expanded. Leaf nodes obviously can't be expanded. Some, like "finding others with similar mindset (intelligent, self-reliant, ??)", could serve on their own or be
whaack: expanded
diana_coman: whaack: building something implies among others a "why", doesn't it?
diana_coman: well, if it is proper building, true.
diana_coman: to the extent that your focus is on the building rather than the otc term, the detailing goes on to look at what building that thing is all about; and logically speaking you start with...why do it at all, no?
diana_coman: whaack: to contrast perhaps - you could find "related" by the sort of "word association" in which case it could be just about anything really, but to give an example, perhaps it goes "building otc network -> my experience selling btc for weed"
diana_coman: whaack: btw, re leaf nodes, it's not necessarily that they *can't* be expanded; it simply is that the author doesn't care to expand it further for this specific outline/article, that's enough.
whaack laughs, and then sighs
diana_coman: dorion: btw, all the above discussion of tree-structuring might be of use to you too.
whaack: diana_coman: Alright. I was hung up on the wording of the node "Why build it" because I saw it as something that *must* be expanded. (As opposed to my previous "There are multiple reasons why I want to build network of people to trade with." which is a dull sentence, but it stands on its own)
whaack: For log reference: my original 2d outline: , my 2d outline that tries to disguise itself as a tree:, diana_coman's revision of my fake tree outline:

Random(ossasepia) | Download daily DB snapshot | Get Source Code