same old bleh: government shut down because democrats won’t agree to fund the wall, or some such horseshit. it’s going to take a generation to fix all the things #drumpf has screwed up. although, it appears, that, with the government shut down, it’s actually impeding #SCROTUS’s ability to vacation in mar-a-lago, AGAIN, and it may also affect betsy devos’ trip to sweden, so it may not be all bad.
got into an accident with monique’s car a week ago. i pulled out of a parking lot into what i thought was a clear street, only to discover that there were two cars on a collision course with my left side. i sped up, to try to avoid colliding with them and succeeded in having only one of them clip my left rear corner, but speeding up caused me to go out of control, and i zipped across the street and ran into a rock in the driveway across the street… and, of course, it’s more than likely 100% my fault.
the weird part is what happened afterwards. the collision didn’t injure anybody, a cop came and took a statement from everyone, but issued no tickets. monique’s car is pretty banged up, it may or may not be a total write off, but they may be able to fix it… but because of the fact that we’ve got insurance, our total out-of-pocket will be $500, plus $4 a day for the rental car, which showed up less than 24 hours after the accident. and, if the car, which is a few months away from the end of its warrantee anyway, is a total write-off, we can use the settlement to buy a new car from monique’s best friend lora’s husband, who owns a car dealership.
there are a number of things that would have happened if i had this kind of accident and were still living in bellingham, which DID NOT happen this time. these things are REALLY freaking me out: significantly, nobody got upset with me, including monique, whose car got munched. she said that’s why we have insurance. then, we went to the beach for 4 days, three days after the accident. if things were as they were when i lived in bellingham, we WOULD NOT have been able to go on “vacation” after an accident as serious as that, even though nobody got injured. and there are a few other things: i’m having my trombone slide rebuilt(!), and it’s costing me around $800. that project would have suddenly been put on hold. also, we’re planning on going to hawai’i(!) for our 20th anniversary, in june, and, after the accident, that would have been out of the question, if this were bellingham.
on the other hand, when i lived in bellingham, most of the time i didn’t actually own a car, and when i did, i only had minimal insurance, and that only part of the time… and in all the time i lived in bellingham, i don’t think i took what i now consider to be a “vacation” even once, despite the fact that i “camped out” in various places a number of times.
upshot of the whole thing is that i’m still thinking i should be in orders of magnitude more trouble than i, apparently, am, currently… and i’m waiting for the axe, which may not actually be there, to fall… which is seriously affecting my ability to enjoy anything else that may be enjoyable. 😕
to continue the post started here, it appears that #drumpf “leaked” code-word-protected intelligence about the current US fight against #daesh to russians, and the media is all up in arms about it. the washington post (a decidedly UN-“fake news” source) reported about it in detail yesterday…
but drumpf and his surrogates have stated that this is 100% false — however, after saying that it’s 100% false, drumpf actually tweeted an admission that he had, indeed leaked classified information — but they are bolstering this claim by saying that he has the right to do so, because he’s the president.
furthermore, there have been several other “legitimate” news sources that say that drumpf is a “shoe-in” for the 2020 election, in spite of the democretins gearing up to regain the majority in the 2018 election.
i’m not sure how the world is going to survive eight years of oprobrious orange “leadership”, but if this goes on much longer, it’s looking as though I won’t survive that long. 😡
it seems incredible, as in “un-believable”, but #drumpf keeps on getting worse… and, at this point, it’s a lot more likely that we will experience nuclear armageddon within the next six months than it has ever been in my life… and, as noah mickens says, it’s difficult to get motivated to do anything when the news is that there’s going to be nuclear war within the week. 😠
and it’s going to be at least 2018 before we can legally vote the crap out. at this point, it’s my very strong impression that we will either annihilate ourselves, or experience a violent revolution before then, and, while i hope that neither one happens, it appears that either option may be better than allowing #drumpf to run roughshod over what is left of america until november of next year.
the only thing that keeps me going, at this point, is the vague realisation that what i hear in the news is deliberately made to sound as dire as possible, in order to provide that extra “thrill” required to make people want to know more, for as many people as possible, and that, in reality, things aren’t anywhere near as bad as they’re making it out to be…
but when they’re talking in serious tones about nuclear war between donald trump and kim jong-un — the two most childish leaders on the face of the planet — there’s an awful lot of leeway that still includes a large swath of the entire population of the world before we get anywhere close to “reasonable”. 😐
in other news, snake suspenderz has two gigs coming up this weekend. an hour at the opening of a new winery in woodinville, on saturday, and at the blue moon on sunday. woo… if #drumpf doesn’t blow us up before then…
the computer industry has been a-twitter for the past few days, concerning a zero-day “bug” in micro$lop word, which gives an attacker full execution control of the victim’s machine — a Very Bad Thing®.
this reminds me of a couple of things that i experienced, more-or-less first-hand, while i was working at micro$lop, and is the PRIMARY REASON why i’m really glad i don’t run machines with their software on them.
there’s this, which outlines what the “bug” is, and how it allows an attacker to take control of a victim’s machine (i put the word “bug” in quotation marks because bugs are usually things that appear in the code by mistake, but it is my impression that micro$lop put this in deliberately, without realising the potential damage it could do)… which brings up the fact that they have known, particularly, about security problems with OLE (which went through a stage where they were referring to it as “ActiveX”), at least since my friend, and computer-god fred debuted The Exploder Control in 1995, which did a clean shut-down of any machine unfortunate enough to be running Windows95 — PLEASE NOTE: the Exploder Control is not harmful, and will not run correctly unless you’re running Windows95 and Internet Explorer version 3, which, by this time, presumably, you’re not. fred’s premise was, and still is, that if you have a method of excersising THAT MUCH control over a machine, it better well be FULLY AND COMPLETELY SECURE, otherwise people WILL take advantage of it.
i worked at micro$lop when the first Word Concept Virus was discovered. it was unique (at the time) because it allowed an attacker to infect a victim’s machine over email, without actually having to have physical contact with the target machine. it worked by utilising micro$lop word’s “normal.dot” template, and required the victim to have macros enabled by default. the new, most recent word problem doesn’t require macros to be enabled, and doesn’t work if the application is running in “Protected View”. so, the solution micro$lop has come up with is to recommend that you run word in “Protected View” in order to avoid this particular vulnerability.
it is significant, to me, that the primary reason we have things like active antivirus software on our computers today is because of actions taken by the micro$lop corporation when i worked there. when i was working there, they were the largest manufacturer of computer software in the world.
and it reminds me of the solution micro$lop came up with to avoid another “bug” in another one of their “excellent” programs, internet explorer: version 3 exhibited a flaw in the way that it displays URIs in the address bar, and by opening a specially crafted URI an attacker could open a page that appears to be from a different domain from the current location. the solution? “Do not click any hyperlinks that you do not trust. Type them into the address bar yourself“… despite the fact that one of the features of all web browsers is that you can get from one source of information to the next, easily, without having to type in long, unintelligible strings of code.
Rule of thumb — Every time Microsoft uses the word “smart,” be on the lookout for something dumb.
— John Walker
A little detective work revealed that, as is usually the case when you encounter something shoddy in the vicinity of a computer, Microsoft incompetence and gratuitous incompatibility were to blame.
— John Walker