Blog

  • Eat, Drink, and … Be

    It’s not easy being drunk all the time; 
    Everyone would do it if it were easy.

    S03E10

    There’s a wide gap between a “social” drinker and an “alcoholic”.   It’s a regrettably coarse span of choices found on personality inventories.   Most who do imbibe can honestly choose the first.  Some might convince themselves that because they drink to be social, they are social drinkers.  Few wish to admit to the latter, which is more a medical diagnosis than a choice or a description of a lifestyle.

    In casual parlance, “being drunk all the time” would be a fair definition of an alcoholic, even if it discounted the hours of work and sleep or required vigilance wherein the being was just the hope of an eventual scratch of an angry itch behind the throat.

    During most of my term in the jail of marriage, my drinks consisted of beer and wine, which are the metals of the medals of lesser ranks on the drunkard ladder.

    In the end years, when coming home from the office meant an hour of cold misery with my gaoler before a few of genuine love from angels plucked from peace into life– during those times, the beer was relegated to a pastime during grilling, and the wine poured in greater quantities as the sun set.   However, after the girls were asleep and before their mother came home to sleep in her hammock, the mainstay was a good Scotch whisky redolent of peat.

    Once, their mother asked what I’d do if she left me.  I said I’d likely get a small apartment and get drunk every night.  She broke a bit there, and cried.  It was near dusk, and my eldest peeked outside to see what was happening.  I hushed her back inside.  It was over by then.

    The marriage, that is.  The drinking was just beginning.

    Enough of the back-story.  Today, I buy more alcohol than I do milk.  I probably drink more alcohol than water.  Indeed, besides the bubbly that issues from my SodaStream, there is rarely any other beverage in my apartment but vodka.

    A few months ago, I began infrequently joking about being an alcoholic.  When a chuckled bit of occasional self-deprecation becomes a daily statement of wearily wry fact– well, it’s not a joke anymore.

    A fierce disclaimer before I go any further: My girls are my reason for living, and their safety and happiness will always dry up any thirst for alcohol.  I will not risk any lapse of vigilance when they are in my care.  Let that be noted and acknowledged as an overriding clause for any future statements.

    Most nights, I’m drunk within an hour of leaving work and arriving “home”.   That is, I’m well on my way toward an inebriation that will eventually erode my impulse control and sway my physical balance.  It’ll be a few hours more until I’m near slipping and/or slurring on my spelling, my grammar, or over my own feet– but I’m drunk in at least the sense of being legally bound as either passenger or pedestrian for any travel.

    It’s Easter morning as I write this.  I’ve finished re-watching Game of Thrones, and the scene that leads this post prompted me to start writing … something.  I’m not drunk now, and won’t be for at least another six hours or so.   Friday, I started at noon.  In any case, I’ve forgotten my point.  Was there a point?  What good reason could there be for my public admission of “alcoholism” when doing so could result in losing access to my girls?  Nothing else matters, but that’s a very dear and important matter.

    Let’s put this one to sleep for now.

     

     

     

  • Rabbit-hole: From DNS To Hacker Wisdom

    Waiting for a DNS change today, using <tt>dig</tt> to check the propagation, did a `man dig`, found mention of Chaosnet and Hesiod classes,

    the latter having been developed within the Athena Project, which also gave us the X Window System:

    In 1984, Bob Scheifler and Jim Gettys set out the early principles of X:[2]

    • Do not add new functionality unless an implementor cannot complete a real application without it.

    • It is as important to decide what a system is not as to decide what it is. Do not serve all the world’s needs; rather, make the system extensible so that additional needs can be met in an upwardly compatible fashion.

    • The only thing worse than generalizing from one example is generalizing from no examples at all.

    • If a problem is not completely understood, it is probably best to provide no solution at all.

    • If you can get 90 percent of the desired effect for 10 percent of the work, use the simpler solution. (See also Worse is better.)

    • Isolate complexity as much as possible.

     

    Wisdom for the aging.

     

  • Thunderturd! or: How I Learned To Stop Griping and Allow Remote Content

    I’m working from home, and our company’s outsourced webmail leaves much to be desired.  My desktop is Windows 7, since it offers the compatibility necessary in the corporate world, while most of my work is done through an xterm launched from my Linux box over CAT6.

    Rather than keeping up multiple webmail windows or collecting them all through one service (which usually leaves me with duplicate synchronizations across devices), I decided to choose an email client.  First, it was Windows Live Mail, and I liked it– for the most part.  Then, we were asked to standardize on a signature with images, and Live Mail didn’t seem to allow that.  It also didn’t have much flexibility in quoting replied messages.

    I tried Outlook 2007 for a while, but it began hanging on IMAP more frequently than my blood pressure would comfortably allow.  I’d given Mozilla’s Thunderbird a whirl, but something about it really pissed me off at the time.  I tried it again.

    Decent.  Open Source, so there are updates, and I could hack the goddamned code if I wanted to fix something real hard.  The most annoying quirk was the “Allow remote content?” pop-in panel.  It seemed to have an all-or-one idea of what should be allowed, where one could show all remote content, or approve single email addresses.  This was a nuisance with, for example, notifications from Google+, which are “From” a generated email address.  Thus, adding that address to your contents did nothing but bloat your contact list.

    A bit more digging found that Thunderbird had the same “about:config” back-door to its internal configuration properties as its brother-father-cousin Firefox and Mozilla and Netscape, and within there was a mail.trusteddomains setting.  One opens this menu through the “Tools” option in the menu-bar, under “Options…”, and then:

    thunderturdOptionsWindow

    According to the arcane documentation available, opening this dialog and setting this property to a comma-delimited list of domain names would instruct Thunderbird to automatically load content (n.b.) from those domains.  Each entry should be a single base domain name– not a subdomain.  That is, “google.com” rather than “plus.google.com”.

    Adding “google.com” didn’t work.  I searched some more, then this morning came across a question on a Thunderbird support site — posted almost a year ago and without a resolution.  So, I went to semi-angrily post my response, then realized– “Hey, me.  It surely isn’t just white-listing domains based on an email address.  If it were, anyone using a gmail account could just plop in an externally-hosted image in an HTML message and have it trusted.”  So, I viewed the source of this particular Google+ notification.

    Two images: one from googleusercontent.com and another from gstatic.com.

    Short answer?

    Set mail.trusteddomains to google.com,googleusercontent.com,gstatic.com 

    thunderturdAboutConfigWindow

    And now, they will load.  This won’t help much if images are loaded from a CDN, and it’s a bit of a nuisance to “View Source” on a message, search and record each “img” tag’s domain, then add them all to the property, but– it works.

    One final commentary which would be a sidebar if I knew how to do it in WordPress: Why not just allow all remote content?  At first, even though I’m a hacker and a cracker and I think I always will, I almost just said “fuck it, it’s just cookies!”  A second later, I realized that any image being loaded involves a hit to where that image is hosted, and while that URL might indicate it’s just plucking a .jpg, it could be doing anything.  It probably isn’t running a script on your mail client (I doubt Thunderbird would allow that), but it could certainly be recording that the message was read, and where it was read from, and all manner of other invasive maneuvers.  At its most innocuous, it could serve as a reasonably accurate “Read Receipt” for mail sent to anyone who trusts you– although they probably won’t trust you as much if/when they realize you’re doing that.

    Enjoy.