MP-WP Patch for Enabling HTML Comments

March 25th, 2019

...among other innocuous tags like bold, blockquote, and so forth.

This patch implements Daniel P. Barron's simple fix. Also included is a revision of the trilema-specific database interaction in wp-comments-post.php to the default wp_comments table as pointed out by diana_coman.

*Edit March 26th 2019: My first regrind was still fucked up, as Daniel P. Barron graciously pointed out yet again. I've reground again using correct syntax. So then:

The secondly-reground patch:
mp-wp_html-comments-regrind.vpatch

The corresponding sig:
mp-wp_html-comments-regrind.vpatch.hanbot.sig

---fuxed files, for posterior---

*Edit March 25th 2019: I've reground this patch based on Daniel P. Barron's catch of my incorrect use of a default rather than a variable table name. The reground versions are:

Reground patch:
mp-wp_html-comments-fixed.vpatch

Reground sig:
mp-wp_html-comments-fixed.vpatch.hanbot.sig

The old patch:
mp-wp_html-comments-enabled.vpatch

My old sig:
mp-wp_html-comments-enabled.vpatch.hanbot.sig

Grab my pubkey, if needed, on the about page, or send !!key hanbot to deedbot on Freenode IRC, while ye may.

hanbot's Cuntoo Bake Test Notes - Part IV

March 17th, 2019

On the tail end of part III we were awaitin' the bootstrapper to finish its long and arduous whizzing.

I woke to find that a lot of kernel configuration awaited me as the result of "professional" negligence somewhere deep upstream. asciilifeform kindly provided a standard configuration to work against, so I set myself to y-in', n-in, and occasionally m-in'.

During which my hand-eye coordination got a little wobbly, and I killed the entire run with an unhappy hit of ctrl + c on the wrong keyboard. Because totally, this failure mode was thought about at some point, and it was decided in a stroke of genius that this innocuous operation oughta be capable of murdering arbitrary layers of a process.

Anyway, I proved to myself the value of the script produced in part III, as I had to run it yet again. I can't describe the second kernel configuration walkthrough as anything but pedantic white-knuckling. I kept a list of what trinque's kernel asked for that asciilifeform's configuration file didn't know about; interested parties can grab it here.

Sadly enough, I find that at the end of the config q&a, and hence the end of the bootstrapper script, I'm still left without a genesis with which to compare trinque's signature. Given which vdiff for instance shows vdiff in my path, I'm at a loss as to why no patch was produced. I also note that I lack even a cuntoo/portage directory.

The next steps being review of the script's record during the run, and deferment to the wisdom of the forum, I ask you: wtf?

hanbot's Cuntoo Bake Test Notes - Part III, with Prep Script

March 8th, 2019

Following Part II, I had my machine rebooted and re-attempted preparation for Cuntoo from scratch. I managed to wrap my head around the admittedly simple path problem previously encountered, and ran trinque's bootstrap.sh. As reported in #trilema, the process fell over on looking for the expected kernel configuration file. I'd used the default config/4.9.94-apu2 parameter. Apparently there's more to this than "preferring" your own. Whoops.

I went through both lobbes' and mod6's recent cuntoo adventure reports to look for clues on kernel configuration, and found I could replicate mod6's process of copying the .config file in /usr/src/linux into the cuntoo/config directory.

The bootstrapper's running now; I'm looking forward to seeing what it has to say in the morning.

Meanwhile, the multiple reboots throughout the process thus far meant I had to prepare my machine for the bootstrapper multiple times, which process naturally became easier but still took up a lot of time copypasting and filling in holes in my notes.

I threw the steps into a script, cuntoo-prepper.sh, with signature. Installation of gnat, V, vtools, and associated pressing and setup is included, along with signature and sha512sum checking where relevant. Depending on your setup, you may need to edit your /etc/hosts file to include the various domains involved before running the script1 :

161.0.121.198 ossasepia.com
104.131.72.249 btcbase.org
45.32.123.240 wot.deedbot.org
161.0.121.247 trinque.org
161.0.121.248 thebitcoin.foundation

Go with defaults during the gnat installation lest you end up tangled in directory confusion.

You'll have to manipulate your path a couple of times once the script's finished:


PATH="/usr/gnat/bin:$PATH"; export PATH
export PATH="/usr/gnat/vtoolsp1/vtools:$PATH"

Then do any futzing required for your kernel config, cd to your cuntoo directory, and hit it.

  1. Obviously if you need to enter 161.0.121.247 thewhet.net just to get the prep script, you'll need alla these too. []

hanbot's Cuntoo Bake Test Notes - Part II

February 24th, 2019

See here for Part I of this adventure.

Part II could otherwise be dubbed "let me tell you how computers pissed me the fuck off today", and finds me back at square one with a LiveUSB in virginal state, utterly uncontaminated by the hours1 of time poured into it since last I ranted.

Given as I abandoned dicking about with heathen gentoo until such time as a Republican freeze is clearly available, my goal was simplified into bridging Pizarro's provided Gentoo USB with trinque's cuntoo.

Part I noted my sad fate of having to update /etc/hosts for every goddamned domain involved in grabbing working parts; by the end of the installment herein covered, I had to add:


161.0.121.198 ossassepia.com
104.131.72.249 btcbase.org
45.32.123.240 wot.deedbot.org
161.0.121.248 thebitcoin.foundation
161.0.121.247 trinque.org

As trinque pointed out, I'd require a working vtools. When I went to handle installation thereof, I found myself bootstrap-propelled to the center of the earth, at least theoretically. Having had a version of V on my local machines since asciilifeform's original release, I'd been enjoying a silent luxury in terms of adding on each block required to press a useful patch as they were available. Untangling the mess of what requires whichelse and in what order isn't especially helped by the fact that keccak-flavored vtools as discussed in the logs, my own site, etc, lived at this url, yet the post at that url is titled differently, namely as "vtools complete keccak prerelease". I also remembered having used gnat's gprbuild to get keccak vtools going, yet instructions for same appear in yet a different post.

Not having touched any of this in several months is, I'm sure, part of the problem I had, but let it be stated that getting a currently-useful vtools going without its precursors on board is currently more spaghetti than sandwich.

Anyway, as my working notes say, chill out, grab gnat, then all patches in the keccak-regrind or prerelease post depending on what we're calling it, press to the keccak head with an old V.

Though ave1's gnat is the current cannonical version, I decided to try diana_coman's adacore gnat alone to see if it'd work. This much was as straightforward as I remember, having needed it for phf's keccak vtools during the MP-WP regrind.


curl -v http://ossasepia.com/available_resources/gnat-gpl-2016-x86_64-linux-bin.tar.gz > adacore-gnat.tar.gz
sha512sum adacore-gnat.tar.gz
cat sha512sum-gnat.txt
tar -xvf adacore-gnat.tar.gz
cd gnat-gpl-2016-x86_64-linux-bin
./doinstall
...
cd /usr/gnat
PATH="/usr/gnat/bin:$PATH"; export PATH

...at which point gnatmake -v returns


GNATMAKE GPL 2016 (20160515-49)
herp derp FSF posturing

Then I was ready for V; I'm partial to mod6's ol' v.pl, principally because of his excellent documentation thereof.


curl -v http://thebitcoin.foundation/v/V-20180222.tar.gz > V-20180222.tar.gz
curl -v http://thebitcoin.foundation/v/V-20180222.tar.gz.mod6.sig > V-20180222.tar.gz.mod6.sig
gpg --verify V-20180222.tar.gz.mod6.sig V-20180222.tar.gz
tar -xvf V-20180222.tar.gz
mkdir .seals
mkdir .wot
mkdir patches

Now for vtools:


cd patches
curl -v http://btcbase.org/data/vtools/vdiff_fixes_newline_gcc.vpatch > vdiff_fixes_newline_gcc.vpatch
curl -v http://btcbase.org/data/vtools/keccak.vpatch > keccak.vpatch
curl -v http://btcbase.org/data/vtools/vdiff_keccak.vpatch > vdiff_keccak.vpatch
curl -v http://btcbase.org/data/vtools/vtools_fixes_bitrate_char_array.vpatch > vtools_fixes_bitrate_char_array.vpatch
curl -v http://btcbase.org/data/vtools/vtools_vpatch.vpatch > vtools_vpatch.vpatch
curl -v http://btcbase.org/data/vtools/vtools_fixes_static_tohex.vpatch > vtools_fixes_static_tohex.vpatch
curl -v http://btcbase.org/data/vtools/vtools_vpatch_newline.vpatch > vtools_vpatch_newline.vpatch

cd ..
cd .seals
curl -v http://btcbase.org/data/vtools/vtools_vpatch_newline.vpatch.phf.sig > vtools_vpatch_newline.vpatch.phf.sig
curl -v http://btcbase.org/data/vtools/vtools_fixes_static_tohex.vpatch.phf.sig > vtools_fixes_static_tohex.vpatch.phf.sig
curl -v http://btcbase.org/data/vtools/vtools_vpatch.vpatch.phf.sig > vtools_vpatch.vpatch.phf.sig
curl -v http://btcbase.org/data/vtools/vtools_fixes_bitrate_char_array.vpatch.phf.sig > vtools_fixes_bitrate_char_array.vpatch.phf.sig
curl -v http://btcbase.org/data/vtools/vdiff_keccak.vpatch.phf.sig > vdiff_keccak.vpatch.phf.sig
curl -v http://btcbase.org/data/vtools/keccak.vpatch.phf.sig > keccak.vpatch.phf.sig
curl -v http://btcbase.org/data/vtools/vdiff_fixes_newline_gcc.vpatch.phf.sig > vdiff_fixes

Itams got!


./v.pl p vtoolsp1 vtools_vpatch_newline.vpatch
cd vtoolsp1/vtools
gprbuild vpatch.gpr
gprbuild vdiff.gpr

I'd thought I would hereafter need phf's updated v.py, but on reflection it wasn't clear if or why this was actually needed. Moreover, trying emerge python-gnupg as specified by said update suggested this'd be fairly gnarly to install, so I decided to skip it for now.2

At this point all looked ripe for grabbing the actual cuntoo tarball & sig at long last.


curl -v http://trinque.org/cuntoo.tar > cuntoo.tar
curl -v http://trinque.org/cuntoo.tar.sig > cuntoo.tar.sig
gpg --verify cuntoo.tar.sig cuntoo.tar
tar -xvf cuntoo.tar

Which produced a bootstrap.sh and friends exactly as promised. We read, from the source, "make sure that you have a vdiff in your $PATH".

With the exception of the exportation in the gnat installation above, I have never run into $PATH operations without ending up in some sort of shitsoup. I would dearly love to comprehend what the fuck $PATH is for; what a path variable actually is; why some instructions specify a certain path variable and others not; how a path variable name is agreed upon; what exact file must be edited in order to add a directory to one's path; and so forth. I suppose it must be intuitive to others, because every attempt at explanation I've come across seems rooted in priors I simply don't have.

I edited ~/.profile to include export PATH=$PATH:/usr/gnat/bin/vtoolsp1/vtools3. After which which vtools reported t'wasn't none, and moreover said directory wasn't listed in my path. I tried editing ~/.bash_rc, no dice. I tried eliding the export part. Nada. I went over to Eulorum to review my notes on exporting path for a Eulora install, but was at a loss for what to replace the "CRYSTAL" and "LD_LIBRARY_PATH" items with. In multiple instances of bitching and moaning about paths I drudged up online, anonymous squawkers suggested the bash session had to be restarted in order for a path exportation and/or addition of a directory to the path to take effect.

To be honest, I had a feeling that killing my terminal and reconnecting wasn't a splendid idea, but I couldn't have told you why beyond a vague sense of "what if this fucks shit up". Well, I killed it. And reconnected. And found the LiveUSB fresh as a daisy, devoid of gnat, devoid of vtools, sans keys, pretty much ignorant of me.

For reasons I utterly fail to comprehend, there *does* remain a typescript log4 I'd started on day one or two of the whole shebang. That's it.

Yes, I'd had the same session going since I originally logged in around the 8th of this month. No, I hadn't been running it in a screen session. Yes, I'm going to start over, and in screen.

But we're going to need more vodka.

* * *

  1. Somewhere in the neighborhood of ten, about eighty percent of which I'd chalk up to mental wrestling with my own noobishness. []
  2. Specifically,
    Calculating dependencies... done!
    [ebuild N ~] dev-python/python-gnupg-0.4.3 PYTHON_TARGETS="python2_7 python3_6 -pypy -pypy3 -python3_4 -python3_5 -python3_7"

    The following keyword changes are necessary to proceed:
    (see "package.accept_keywords" in the portage(5) man page for more details)
    # required by python-gnupg (argument)
    =dev-python/python-gnupg-0.4.3 ~amd64

    Use --autounmask-write to write changes to config files (honoring
    CONFIG_PROTECT). Carefully examine the list of proposed changes,
    paying special attention to mask or keyword changes that may expose
    experimental or unstable packages.
    . []

  3. Yes, that's actually where I installed it, lazy as it may've been. []
  4. 2.7MB; I'll post this if anyone actually wants to go spelunking, please write in if so. []

hanbot's Cuntoo Bake Test Notes - Part I

February 9th, 2019

This is the first of what promises to be multiple posts on my progress against MP's gentoo to cuntoo bridge testing task.

First order of business: install heathen gentoo. BingoBoingo and asciilifeform of Pizarro swiftly and graciously set me up with an appropriate box once it was discovered this experiment wouldn't work on any of the 32-bit laptops laying around these parts.

I've been working with mod6's gentoo installation guide.

As Pizarro included a Gentoo LiveUSB for me, I skipped past 0x01, "Create LiveCD", to 0x02, "Setup Disk Partition Table". This section mentions a "Part B" with partition creation instructions that is not actually included, so I referred to the Handbook's guide. Here's how my partition table ended up before saving:


Device Boot Start End Blocks Id System
/dev/sdb1 2048 6143 2048 83 Linux
/dev/sdb2 * 6144 268287 131072 83 Linux
/dev/sdb3 268288 1316863 524288 82 Linux swap / Solaris
/dev/sdb4 1316864 312477695 155580416 83 Linux

I formatted the above partitions with filesystems as per mod6's guide, and then I followed the mounting steps remaining.

Downloading the Stage3 failed unexpectedly (a pattern that repeated itself with an exasperating insistence worthy of greater glories than a goddamned OS install).

Upon painstaking examination it came to the fore that the domain failed to resolve. I tried IP addressing directly via curl but of course the gentoo mirror's too clever for anything like that. In the end I was reduced to populating my hosts file with their intricate pattern of name allotments. Adding in all other various patches I ended up forced to put on it, my hosts file now reads:


64.50.236.52 gentoo.osuosl.org
140.211.166.134 gentoo.osuosl.org
64.50.233.100 ftp.osuosl.org

192.146.137.98 pool.sks-keyservers.net

64.50.236.52 distfiles.gentoo.org
140.211.166.134 distfiles.gentoo.org

During the tarball extraction stage in 0x03 I had to change the tar command's options as our source's current tarball is in .xz rather than .bz2 format; this means using tar xJpf rather than xjpf1 .

Moving on to 0x04, I entered the chroot as instructed. Then, on first running emerge-webrsync, I got a friendly eggog:


!!! Section 'gentoo' in repos.conf has location attribute set to nonexistent directory: '/usr/portage'
!!! Invalid Repository Location (not a dir): '/usr/portage'

Which did not reappear on running said command the necessary second time once distfiles.gentoo.org was added to my hostfile. Why domain resolution should affect directory problems is beyond me. At any rate, the second run of emerge-webrsync reportedly completed successfully.

I entered the mysterious mkdir -p /etc/ld.so.conf.d command to avoid the "problems" promised without it2 , at which point I went to cat /etc/fstab and discovered it's a 0-length file, completely empty. How this is possible I've no idea given the partition setup described above. I've elected to close this three-hour session of disappointment on the heels of searching for others' rants about empty fstab files, hoping for any notion of how this could be, and watching my browser grey over and crash.

***

  1. As tar ran this it spit out "tar:Xattr support requested, but not available", which makes me suspect this set of options may not, in fact, have done all that was intended. []
  2. I can't help but think that in this case my confidence in the Republic, which allows me to "just do it" like this comes at a possibly too-high cost of having not the first clue what this step was about. If this wasn't in-WoT I'd abandon the guide right there, you know? []

Recreation

January 30th, 2019

mac-1

The spaces there; the pause between
what I can stomach, and the feast
leaves life a malleable thing now quickening
now sickening
now stagnant
now serene.

mac-5

mac-3

I've no idea where I might look to find the contradiction,
else but in your mind, or the fields stretched out before your gaze
or in my crumbling heart, here succumbing
now becoming
now belligerent
now base.

mac-4

mac-6

How could I hate the center of my life? And yet the sun is sometimes scorned
for shining forth too bright, for warming more than dainty life can suffer without singeing.
The inability to imbibe all is mine. I feel it healing
now kneeling
now knotted
now known.

mac-2

mac-7

Guts I've Lost

January 24th, 2019

Who knows, perhaps they'll be the guts someone else gains. In any case, I charmed some pix off the doctor and I find the general population lacking in gore disclosure; let's see what an emergency appendectomy looks like, mm?

When I was little I regarded the concept of surgery as so abhorrent, I resolved I'd simply off myself if a situation requiring it were ever to arise later in life. As it happens, my appendix microperforated this past December 1st and the presiding whitecoats prescribed total eviction. I didn't have such a bad time, all things considered.

appendectomy-1

Pre-op was the worst, attended as it was by the visceral agony of the insubordinate tissue's sequelae. There was also a botched visit to an initial ER that sent me home with suspected stomach infection and a basket of meds that made just about everything feel just slightly worse. The hours before surgery included a dozen or so failed IV placement attempts and administration of a high-viscosity analgesic whose effects were arguably worth the sudden desire to gnaw my arm off and throw it at the poor nurses, experienced during the infusion.

Such unpleasantries were offset by the palpable precision of my surgeon, clinician, and ultrasound doctor, who managed a clear response to a very cloudy presentation fast enough to prevent rupture. Ultimate redemption arrived with the jolly anesthesiologist, who recommended himself to my confidence convincingly and then told me I was about to love him outright for the delivery of that there hypodermic of fentanyl. He was right, and he promised to give me back to the boss later on, which he did.

Much bloody mess was probed, as you can see.

appendectomy-2

The offending tubule's mugshot.

appendectomy-3

The procedure was laparoscopic, leaving me with two half-inch scars and a very mildly rearranged bellybutton. All was secured with dermabond glue --no external stitches to fuck with.

appendectomy-4

I stayed at the hospital a few days until my doctors were happy with my bloodwork; the appendix had left a good amount of untenable disguststuffs here and there, and we had to wait a little for my immune system to prove it could handle things. Three days of ambulatory ER visits followed for the sake of supporting antibiotics.

Here's my last IV line being taken out, exactly a week after symptoms had started.

appendectomy-5

I was forbidden to lift anything for a couple of weeks, and from the gym for about a month, which in retrospect seems like the hardest hit of the affair. On returning after the new year, I found I'd lost 10kg on my barbell squat and a good 20 on seated abductions, both hard-earned over a longer course of time than my recovery. I'm still clawing them back.

Let the childish or uninitiated mind take comfort, though; a little slice and dice is, assuming one's lucky enough to have the professionals and endlessly patient, doting visitors I had, not such a big deal as all that.

The Roadblock

January 23rd, 2019

Via the bimbo we find:

Since the holidays are over, its now time for construction in Costa Rica. The locals decided to block one of the only major highways in the country for going on over thirty five minutes. Lucky for us, we ended up at the beginning of the line and had Master in the car. It took him only around a minute with the workers before the cones went up and they quickly got out of the way. Of course, this was after a few nervous looking men walked over to the workers and bailed out of any confrontation by getting on their phones and taking the walk of shame back to their cars without saying a word.

To which we offer a smattering of amendments, having conducted said journey through the tropical wilds at the wheel of a particularly shining silver steed.

Firstly, it's always time for construction in Costa Rica. It's not so much a matter of "growing development", this, but a necessary consequence of the brutal facts of ekeing out a civilization of sorts amongst the verdant exuberance of the land. Potholes. Sinkholes. Collapsed bridges, fallen switchbacks, obliterated pipes, all "repaired" inexpertly but with great enthusiasm, all contributing to a constant critical mass of catastrophe.

This time, the problem was mild enough: the yellow median had fallen just this side of invisible, and the poks1 had gathered up their very best paint in their very best mini-pokmog, eager to make the road safe again for the 40kph natives and the 140kph foreigners who weave around them. Except they decided to close down the entire road for the proceedings. As in, with roadblocks. Both directions. Whether this was an honest if inept attempt at safety or the effects of sheer wonderment at their own technology I couldn't tell you, but it was certainly several shades of ridiculous.

Valiant Prince MP ventured forth to the bevestacled2 roadslave and demanded an ETA. Thirty minutes. Which is an insane askance on the one and only road to the nation's northeast at ten in the morning on a thursday, but patience is well-coddled by comfort, something our horse has in spades. Ever play "I spy" in the rainforest?3 We didn't, but anyway. Thirty-five minutes went by, according to the bimbo's ever-faithful watch. A motley stream of family heads, some in characteristic pastel plaid button-downs and flip-flops, others in JC Penny-diaspora slacks and stacked heels, shuffled awkwardly towards the workers to lodge complaints throughout.

Here's how Costa Rican complaints go:

"Hey buddy, how's it going?"
"Oh fuck me dude, everything's so great, I'm so happy to see you!"
"Back atcha, friend. I thought, mayhap, there was, possibly, a thing not entirely great afoot?"
"I'm sure it's possible, but whatever, shit's great in general and mostly in particular!"
"I couldn't agree with you more. May all your days be glorious."
"May yours be better! Remember, I've two kidneys, should you need one!"

Fifty-fifty shot a hug goes here. Mind you, as the bimbo pointed out, actual confrontation was rare; for the most part these exemplars of effectuality merely approached the worker at not-quite shouting distance and tapped plaintively at their electronic rectangles4, only to walk back to their cars moments later, as though their subtle show of guarded inquiry were sufficient for anything at all.

But as I was saying, thirty-five minutes went by. At which point MP left his leathery cushioning and motored himself towards his municipal amigo again. I wasn't within earshot, but here's how (this) MP complaint went, from my perch:

MP approaches road worker at breakneck speed. Worker visibly if ever so slightly receeds from his post.
MP's arms rise to either side in exasperated parentheses.
Worker points in the general direction of the painting aparatus, shrugs.
MP's frame straightens, despite the impression it was already perfectly straight.
The handful of road workers previously lolling about in the adjacent vines chewing plantain chips get on their feet and move in to reinforce their colleague, meanwhile grown shorter and blown further back from his original stand.
The Blue-Red-and-White disco-dance, a possible misunderstanding of further pointing, squatting, and shrugging.
The ...5 aggressor delivers his fatal blow; left hand held slightly underneath, his right makes three decisive chopping motions --one to the left, one at center, one at right. This catalyzes the workers' retreat; they regroup a meter or so back.
A walkie-talkie is produced and passed frantically from one worker to the next. MP is stone-still.
After a beat, the workers run to the assembled cones comprising the road block and lift them.

So swift was the demolition that MP was obliged to run back to the car, lest he encourage 40kphers to overtake us. And that's how we almost lost half an hour on the ride in.

* * *

  1. Pok, noun, that species of Orc which proves lovable through its earnestness and innocuous nature despite its Orcdom. []
  2. It's my blog and I'll be a pompous foff if I wanna! []
  3. Hint: it's something green. You wouldn't shoot a gal, wouldja? []
  4. The pretense that these are "devices" chafes me. An abacus is a device --a "smartphone" is a travesty. []
  5. What colors are the Republican flag, anyway? Buttplug? []

Perambulating MP: Pretense vs. Pretense

January 17th, 2019

spyvsspy

The only potential "winner" is you.

So it happened this morning, as it fairly often does, that my reading of a Trilema article1 set off what I can only call The Churning, a distinct psychophysical sensation involving more or less every organ which threatens to culminate in a nervous fit if the inspiring material is not further examined and personally atypical considerations are not ingested.2 That sentence aside, allow me to specify3 two precursors:

I.

The "for women" part is provided by weakass sauce like some minor plot token pointing out to the hero that since his lordship, who knows quite a lot about male antecessors older than his greatfather, nevertheless knows exactly nothing about any women in the same line, even should they be younger than his grandmother, therefore it (the plot token) could in fact very well be the very grandmother in question.

The pretense involved, if it wasn't thickly laid out enough and it could take further belabouring, being that women are equally important to men, and equally meaningful and therefore notable, but "unfair arrangements" make men remembered and women forgotten.

II.

Pro tip : just because whichever god is stuck fucking the same Geea to make people, dun mean neither that people are all god's children, nor that there is or can be such a thing as "the goddess". The gods are all different, and earth is no goddess.

I brought these to breakfast, intent on using without abusing my unfathomably fabulous access to the very font of such allergens and their alleviations: the author. What follows is my distillation; inadequate as it may be for severe or obscure cases, I hope it offers some degree of support where it may.

I.

The emboldened passage led me on first pass to wonder whence and wherefore came the notion that women aren't equally important, meaningful, or notable to men. I suspected retreat into the concept of "non-equality", as in "no two things are equal" or such. Not the case; analysis of the problem here begins with the quantitative, hinted at in the preceding paragraph: "who knows quite a lot about male antecessors older than his greatfather." The set of this (or any given spring chicken's) antecessors is easily brushed aside as "big", or even "very big", but these are unexamined and unspecific.

If we take a loose approximation of man's time on this earth, say 100,000 years, and suppose every generation is about 20, we're left with 5,000 generations. In terms of individuals, then, we're left with no less than 25000, as every one was borne of two, one man and one woman, without exception. To get an idea of the size of the number of individuals, we'll move from base two to base ten and notice4 that 25000 ~= 101500, a number with 1500 digits. Divide it by two and you'll have, quantitatively anyway, two exact halves with fifteen hundred digits each. Exactly as many men as women, a minor miracle existing nearly nowhere, certainly rarely amongst things touched by the hand of man. Two particularly well made cups might be identical to three or maybe four digits; two CPUs perhaps twelve, at the cost of billions in fixed capital. There is no such thing known to man's industry or artifice as fifteen hundred digit equality, perfect and unyielding, exactly exact forever. In any case, the war was won by barely similar machinery.

The statement of fact that foremothers and forefathers are exactly equally sized, despite their incredible abundance, passes unremarked upon by the friendly fiend. The problem rather raises from MacDonald's proposal those two groups be equally important, meaningful, or notable. Yet why is it Anondos "knows quite a lot about male antecessors"? I proposed it was because those male antecessors did something. What else is there to know about someone, anyway? MacDonald might've countered, as I did (indeed, myself!), that it is inherent in feminine nature to keep quiet about doing, and to just do, whereas men are inclined to fabulate, to insist they've done what they've not, or to make the knowledge that they'd done something the focal point of the doing. This may even be true, yet what difference does it make? If indeed that's the female nature, then that's the female nature --nature no doubt is naturally happy in its nature. If it isn't, someone's lying, but in any case, there is not nor can there be such a thing as objective meaning. That, after all, is the one lesson of human inquiry.

What, then, is meaningful? What does MP's "...and equally meaningful and therefore notable" actually say? I proposed that if the trumpeting of deeds trumps the deeds themselves for meaning, let us all retire from doing and join for instance the Power Rangers or whoever else. At which point I was ready to receive the crux, staring out at me from the very beginning of the sentence I'd objected to5!

The pretense. MP describes the author's pretense. Of course the Power Rangers are the meaningful party to them, and of course MacDonald proposes some unknown females are nevertheless meaningful to his character, as part of the traperdition of placating the talkers and dreamers of the world by idly pretending that they're just as much a part of that world as the doers. I asked MP why he thought MacDonald dunnit. "He thinks that's how you write fantasy. But it's cheap fantasy, cardboard fantasy." Don't you find?

II.

What then of goddesses? Why would gods be talked about as though their possibility were unquestionable, and goddesses rejected as a very conceptual possibility? I was asked to produce a god. I chose Zeus6, and when asked "what is the thing about Zeus?", offered a beard and lightning bolts. Yet it turns out the ancient Greeks codified mythology as a tool, just as well-oiled and ready to be used as the fractions I'd been fumbling over in I. above, and there's a lot more to it than aesthetic tokens and mundane symbology.

The correct answer is: Zeus said "...and if you don't like it you can all grab a ring and I will grab the other side and throw you all across the sky." Cronos ate his children. Athena struck at her father's skull with her lance from inside 'til he had her birthed just to stop the pain. Diana kept her ass hidden from they who wanted to see it. Gods do, and the doing defines the godhead; Gaia7 "just is".

"So are there goddesses or not?" I asked. "What about Athena, what about Thetis, Diana?" "They did. They have tits, they're still male."

At this point it might occur to you, as it did to me, that MP's use of language --"goddess" vs "do-nothing", "men" vs "the only parties to actual activity"-- can only be fairly described as a pretense of its own. Why not state it plainly, the lazy and idiotic are therefore not as good?

It's pretense vs. pretense, and even if you don't favor the method, I doubt you can argue it's not wildly instructive for the audience.

* * *

  1. MP proposes said article's title is incomprehensible, but I have the answer key. Neener. []
  2. It is, to be sure, a blessed illness, and I know of no better, and certainly no swifter, way to learn or grow than by tending to it; text that never makes one feel sick is as so much government cheese, irradiated of culture and shelf-stabilizing unto one's death. []
  3. Specifying is, woefully, rather personally atypical. []
  4. I'd like to note for my own self-immolation that none of the reasoning herein contained blossomed forth from my own brainpan. Part of the The Churning's cure is the revelation of the number and size of one's holes in knowledge and dams to facility. Never ever believe anyone who proposes you "don't need" or "just aren't meant for" or etc, math. Innumeracy will suck your life away, guaranteed. []
  5. No shit, actually intelligent people order what they say by importance; imagining an opener is decorative is bound to fuck you up. []
  6. And quickly regretted it, asking to change to "a less complex? one" for the sake of lower outlier example potential. My request was denied. []
  7. Geea in MP's original. []

Chimichurri and the Meaning of Life

November 24th, 2018

BingoBoingo: re: http://btcbase.org/log/2018-11-15#1872387 How is Chimichurri Raptorson doing these days?

There is a time in the flow of duckitude ripe with thought and reflection, ever eager for an answer to that nagging void: when shall the next trocito of premium yellowtail materialize?

cml1

Yes, his is a philosophical adolescence, a blooming of quill-topped q-tips o'er the wings, a chortling curiosity towards twins.

cml2

The great horizons call, full of wonderment and hermit crabs. A duck cannot but wonder: why is he here?

cml3

Who invented the lambada?

cml4

If a feather grows in the forest and there's no one around to scratch it, does it make an itch?

cml5

No matter the conundrum, the conclusion tends the same. A sunny disposition's the thing, whether doing laps in the sea or in wild bewilderment.