Re: Suck Shit
... for good measure.
223 posts • joined 18 Nov 2016
Why all the hate for 8(.1)? I can understand the people's outright contempt for MetroUI, but the system can be whipped into shape with a few third-party applications, some update avoidance, and disabling of a few anti-features. Last usable MS OS to me. I therefore argue that the pattern still follows, with 8.1 being the "good" (relatively speaking) release (if we'll allow, as Microsoft does, that 8 and 8.1 are distinct enough to consider different OSs).
Reminds me vaguely of a time someone was trying to scam a friend of mine out of some money (it was fairly obvious to both of us, but we wanted to be able to shove evidence in their face); joined the group chat, and dropped a "hey cool lol look at this guys" sort of link to a no-ip/dyndns name that pointed to a small webserver, and noted their IPs were coming out of Nigeria. IIRC they claimed they were from Boston.
"In response, I wrote a letter to the editor raising concerns regarding their publication's approach and arguing it should notify the local FCC office of illegal activities rather than romanticize these 'broadcasts' or provide the 'station' with some type of legitimacy,"
I can't help but feel that the 'sentences' he writes 'read' sort of like a drudgereport 'headline'. You know, since we're clearly free to 'quote' things to delegitimize them, or imply that the word is being used in a way that is not 'coherent' with its dictionary 'definition'.
Same here, 8.1 was where I kind of jumped off the Windows train. Bought Win 8 Pro shortly after the Win10 RTM proved to be pretty much everything we feared it might be (unending "development", forced updates, even-more-questionable privacy practices, etc.). Just add ClassicShell, and it'll do most anything I need it to do. Though somewhat more difficult than Win7, I have yet to run into any major compatibility issues with old software such as early-2000s directx games, VB6, and older office variants; what problems I did encounter were easily resolved with the body of reference that has accumulated trough people's trials and errors to date. That last part is something Win10 seemed to try to throw out the window(s); fortunately, a lot of Win7/Win8 compatibility tricks are still relevant.
It has gotten so bad that I've resorted to just wildcard blocking whole area codes and local exchanges if I do not know anyone from them. I also block numbers from my own exchange so that I can shrug off any of this "neighbor spoofing" crap. I've also had to block a few exchanges that had their first two digits (instead of the usual three) spoofed to me.
I was actually going to comment about this; though also a native of the left side, and having no significant background in chemistry, I have a strong inclination towards IUPAC names, including aluminium (it just sounds better to my ear). Sulfur over sulphur doesn't feel natural though, even though it was an established spelling well before I went to school.
Once, In the midst of a rather bad case of morning grogginess, I spaced out and ran dhclient on a shared web hosting server. Instant network deconfiguration, and for lack of IPMI or similar on the box, a reboot ticket to the datacenter... fortunately, no major consequences for anyone involved.
Why would this even possibly happen? I've been using Linux for many years, but I'm often two lazy to set up my networking stuff statically or make sure it happens automatically, so running dhclient after a reboot had become a part of my personal routine.
The best part was the response from a higher level systems administrator to a trouble ticket I submitted, which detailed the situation thoroughly, and suggested to remove dhclient from our many servers, as it is yet another 'big red button' waiting to happen. The response was basically a whiny remark along the lines of "just don't run the command!", despite that having been the entire subject and general tone of my ticket. This apparently resulted in them getting "talked to".
I'll contest the notion (that they would attempt to attack it, provided the current regulatory environment on burning tobaccos, also not trying to suggest that this was specifically your own sentiment) by noting that they're actually making decent inroads in the vaping department themselves. There's money to be made, especially with increasing constraints on the burning-tobacco market. Most gas stations in my general area have at least one brand, and most of those have several to choose from, both one-time-use and with replaceable, pre-filled cartridges. I do not mind such competition, provided they don't make any overly hostile moves towards the more DIY markets, but I don't hold much hope for that overall. R.J. Reynolds even pulled a full recall on their own Vuse Vibe pens in the past couple of months, after some reports of overheating batteries came to light... not even any injuries or property destruction. It seems to me that they wish to at least appear to be on the side of good.
I quite enjoy shitting down the gullet of the "it's just water!" crowd. Unless they're legitimately into e.g. ultrasonic water misters. I'm well aware of the hazards and effects, both first party and otherwise (as far as they can be known). The amount of nicotine being exhaled is still noteworthy, and the water content negligible, so folks need to exercise discretion when vaping indoors and especially around others. Inconsiderate loljustwaterbrovapers need to take it down a peg. There are ~4 vapers in my office of ~20 folks, and not one of them billows clouds of stinky funk.
I was actually thinking about making one myself, but there were a few design points that might move it out from under that definition: fuses (both a quick-blow for shorts, and a lower rated slow-blow for stuck-on conditions), a VRM/MOSFET tuned by a pot (optional, possibly as a selectable module, and the thing that makes the definition questionable), and a self-resetting thermal breaker. I'm totally willing to forego the fun little project if it meant other people knocking off the silliness entirely. I also suspect that at least mandating basic thermal/short protection would go a long way in preventing this sort of thing.
Had a battery short out in a mod (I guess people call them mods, but I had always assumed 'mod' referred explicitly to the unregulated 'mechanical' kind, but this was a regulated device), but this was exclusively due to my own neglect of the battery condition.
Inspecting the failed battery's sibling, it looks like the plastic wrap got chafed, split apart, and allowed the insulator ring to get pushed aside, resulting in the contact in the battery holder completing the circuit. Had it been pointing towards my face, I might've seen the spark/glowing metal before it was too late, but i'm generally glad I did not. The thing vented, sputtering caustic fun juices and flecks of burning material (which i assume were a combination of both the battery casing being melted from the short, as well as the now degenerating innards of the cell) in a show that was not unlike a standard bottle rocket motor in visuals, intensity, and duration.
In retrospect, I should've immediately exited the room and pitched it on the tile hallway, as there was nowhere safe to place the thing, so I wound up holding onto it in order to avoid a mattress/paper heap fire. My hands were burned fairly badly (all healed up just one month later, save for some dryness and sensitivity), as the gas jet was basically going through my index and middle fingers for the first ~2 seconds, and I eventually dropped it on the carpeted floor after having switched hands (only minor burns on that side). The battery popped out and rapidly melted its way into the carpet padding (cement foundation, fortunately), and ignited a sheet of paper that was nearby. Had to open a window with a handful of fingers looking not unlike barbecue sausage links, but in < 2 minutes, fire extinguished and room ventilating. Then off to the ER for a good looking over.
All told, damage entailed 7 fingers burned, 2 were fairly bad (and a third got a bandage stuck in it due to falling asleep with it pinned), ~1 sq ft of carpet ruined, near a corner, burnt people grease all over the smoke detectors and doors (since cleaned), a discharged dry chem extinguisher, and ~550 USD in medical (I wonder if anyone's health insurance in this country has *ever* covered any entire ER visit... base total was ~$850, with no ambulance ride or drugs). Plus whatever my landlord is going to charge when I get around to telling him about it. Which will happen at some point after he deals with a god damned raccoon (a family of them, I now suspect) that lives in the crawl space between the floors.
At any rate, the moral of the story is: don't neglect your battery condition, especially if you frequently swap the batteries in and out of a charger. This one was entirely my own fault, and even in America, I think it'd be difficult to sue myself. Also still cheaper than (treating) lung cancer.
Might just be a Debian thing as I haven't looked into it, but I have enough suspicion towards systemd that I find it worth mentioning. Until fairly recently (in terms of Debian releases), the default configuration was to murder a user's processes when they log out. This includes things such as screen and tmux, and I seem to recall it also murdering disowned and NOHUPed processes as well.
You're thinking of Dell, I think (hopefully). Unless something has changed, Dell uses a serial EPROM on the center pin, whereas HP uses a voltage output on that pin to inform the laptop of the wattage. I've hacked together functional adapters from an older adapter, a couple resistors in a divider network, and a severed power output cord. That being said, that center pin loves getting bent. Then your laptop won't charge, and you can only straighten it a few times before it breaks.
Biting the hand that feeds IT © 1998–2019