Facebook stopped using XMPP awhile ago. Get FB chat back in Pidgin with the purple-facebook plugin.
I moved from a super humid place – Atlanta – to two super dry places – first Tempe, AZ and then Bend, OR. The other day I pulled down my Martin, who is neglected over my Taylor parlor guitar, to practice slide and discovered that the back was splitting:
After first getting over my freakout about my precious (read: expensive) guitar cracking, I did what I always do and took to the intertoobs for answers. I found a luthier discussion board and read about how they’d try to fix cracks by hydrating the instrument by bagging it with a wet sponge. This, hopefully, would close the crack and allow for a surgical glue repair. Guitar, bagged.
4 days later, this is the status of the crack:
Excellent news. I’m going to keep it bagged for another week or so to see if the crack will close altogether. Then I’ll remove the strings and see if I can reach into the soundhole to apply a bit of superglue from the inside, so I’m not potentially marring the outer finish.
For years now, perhaps even more than a decade, I’ve had problems with my stomach. Bubbles, cramps, swelling, pain, unpleasant bathroom issues ranging far beyond mere urgency. At best it was distracting. At worst, actually debilitating. It cast a shadow on everyday life, and ruined what should have been good times. Eating out made it worse. Eating not-great food made it terrible. Thus some of my worst bouts occurred while traveling, ultimately making vacations unpleasant. Traveling across Europe should be fun, not uncomfortable and stressful.
Along the way I had a myriad of diagnosis. IBS. Nervous stomach. I had a variety of procedures to no avail, from ultrasounds to, eventually – when I finally became frightened enough to start wondering if I had cancer or Crohn’s – a colonoscopy (which cost an arm and a leg since my insurance is terrible and I had it done prior to the recommended age of 50). Nothing. “You must have some sort of food allergy,” said the gastroenterologist.
Sure. But it must be an allergy to food in general then, because it doesn’t matter what I eat.
Despite supposedly having no data caps, the other day my provider interrupted my surfing with a message stating that I’d downloaded an “excessive amount” and should contact them to upgrade my plan. Interestingly, their website also doesn’t show any data caps or, for that matter, any plans for me to upgrade to.
I’m not real worried about it, but at the same time since I work full time remote I really need my intertoobs to work all the time. Then I remembered that the vacation rental we manage next door to me has internet that rarely gets used. Time to slap a wireless NIC on the server and push internet traffic through that router!
Doing so was easy. I had a halfway decent USB wireless laying around. I slapped it in, joined the next door wireless network, and then ran a route print:
The highlighted bit is the new NIC. Above it is the wired NIC connecting the server to my local network. You want the Metric on the NIC you want internet traffic flowing through to be the lowest. Luckily mine defaulted to that. If yours doesn’t do that you can manually set the Metric by navigating to the Advanced properties of the Network Adapters:
After that I simply removed the Gateway address from the properties of my wired LAN access NIC and voila – all my intertoobs were coming from next door while my LAN still had full access to my server. In order to double check I logged into my router and disabled internet traffic for the server IP address.
I also installed a groovy little tool called Network Manager so I can watch the traffic:
For reasons I won’t get into here, the EFF has decided for now not to support Pale Moon, which is my current browser of choice (sideplug: Like Firefox but tired of it gobbling all your resources and crashing? Pale Moon my friend). The inability to install HTTPS Everywhere nearly had me leaving Pale Moon until I discovered that there’s a fork of it out there that works! So use Pale Moon, and install Encrypted Web (and uBlock Origin).
I’ve read some pro-capitalist (anti-socialist?) rants lately, some penned by people roughly half my age, that have disappointed me in their shortsightedness. I’ve also read some writings by people like Stephen Hawking – who recently said we should not fear artificial intelligence, but rather capitalism – and a raft of economists, technologists and anthropologists – who are predicting a near future of technologically driven job scarcity – that lend credence to my disappointment. You don’t have to like it, but you’d be a fool to ignore it: we’re on the precipice of a future with a very different economic landscape, and more likely than not – especially if you’re young – you’re going to be in big fucking trouble if your value system doesn’t change, and fast.
Trust me. I know. Because, on a very small scale, I’m one of those people making you obsolete. Continue reading
Surely you’ve already read that Windows 10 includes some pretty disappointing user tracking baked into it. Microsoft is also pushing this tracking down to its Windows 7 and 8 operating systems.
Aside: I get the Win 10 thing. It’s free. Do what you want with your free operating system. But quietly inserting anti-privacy shit into operating systems that people have already paid for? Ludicrous. Offensive. Ridiculous. It’s prompted me to finally get off my ass and move all the machines I can off of Windows and onto Linux, for good.
Anyway, yeah, MS is pushing this stuff into your operating system without really giving you any indication. The current list of updates that should trouble you are as follows:
You can remove these updates via command line thusly:
wusa /uninstall /KB:2952664 /norestart /quiet
wusa /uninstall /KB:2990214 /norestart /quiet
wusa /uninstall /KB:3021917 /norestart /quiet
wusa /uninstall /KB:3022345 /norestart /quiet
wusa /uninstall /KB:3035583 /norestart /quiet
wusa /uninstall /KB:3044374 /norestart /quiet
wusa /uninstall /KB:3068708 /norestart /quiet
wusa /uninstall /KB:3075249 /norestart /quiet
wusa /uninstall /KB:3080149 /norestart /quiet
In fact, you can save the above to a .bat file and run it. This takes them off, but unfortunately doesn’t prevent them from presenting themselves for install in the future. To fix that you’ll have to head to Windows Update, let it scan what you’re missing, and then go through that list hunting for each of these. When you come across one, right click it and choose to hide it.
This is the list for now… I sincerely doubt this is where it will end, however. Have you tried Linux lately?
My Sickbeard doesn’t like it, and doesn’t find it when it’s out there. Turns out the problem is how it’s being named out there in usenet land, and Sickie can’t figure it out. It also turns out Sickie has an exceptions database just for handling these sorts of situations. Problem is, this database doesn’t get updated very often. Good news is, you can update it yourself!
The database is cache.db, found in the program directory for Sickbeard. To add to this file you need to use a SQLite shell interface. You can see basic information on obtaining and using the shell interface on a previous post here.
Once you’re ready to go, fire up your interface from a command line:
Open the database (Pay attention to pathing. In this example I’m already working from within the directory containing cache.db) :
And use the following to insert “Stephen Colbert” as a general search term:
Breaking down this line a bit: 9999 is the exception ID you’re assigning to this exception. We’re just looking to get past all the existing exceptions without conflict. As of this writing my scene_exceptions table has 777 legit autofilled exceptions defined in it. 289574 is the TVDB.com ID for the Late Show, the next field is a the search term to be used for the show name (Stephen Colbert), and the final field is the provider, which is the tvdb.
That’s the error that seemingly randomly popped up on my screen.
The cache has no package named “wine1.7-i386”
I’m using Wine because there are some Windows specific things I need to be able to run. It seems that the updater may just not like Wine too much, because when I manually ran updates with a simple sudo apt-get update it upgraded without a problem and the error disappeared.