Well, at least no human had to demean themselves and read this crappy robocaller’s crappy script.
From the headquarters which will get expired in next 24 working hours. And once it get expired after that, you will be taken under custody by the local cops as there are four serious allegations pressed on your name at this moment. We would request you to get back to us so that we can discuss about this case before taking any legal action against you. The number to reach us is 425-382-5691. I repeat 425-382-5691. Thank you.
Oh, MoviePass! You were such a dream service for movie professors… until you implemented a policy requiring photographs of ticket stubs and then introduced bugs into your app so that it would not accept said photographs.
So, now your Android app has 5,495 one-star reviews–fully 47% of all submitted reviews.
You even provoked me to write a review and that’s only about the third time I’ve done so.
Here’s the transcript of what I wrote:
App crashed when I tried to take a photo of a ticket stub–a new, hinky method to limit abuse of subscriptions. Now I’m prompted to submit a photo (which the app won’t accept) and effectively blocked from accessing my PAID subscription because the app won’t go beyond the photo screen. Extremely poor implementation of a dumb policy.
Still another item from the “In Order to Serve You Better, We Are Now Going to Fuck You Over” file:
Today we’re launching some changes on Google Images to help connect users and useful websites. This will include removing the View Image button. The Visit button remains, so users can see images in the context of the webpages they’re on. pic.twitter.com/n76KUj4ioD
Really, Google? You’re really making this change to “help” users? The motivation for making your image search less useful is to help us?
Oh, wait, maybe the change is not to help us:
For those asking, yes, these changes came about in part due to our settlement with Getty Images this week (see also https://t.co/a5uFldOcih). They are designed to strike a balance between serving user needs and publisher concerns, both stakeholders we value.
I’ve railed on this blog before about the extortion fee that Adobe charges for the Creative Cloud subscription. Supposedly, one of the “advantages” of this subscription is that one gets all of CC’s latest updates. Alas, this often backfires.
After updating to Adobe Audition 2018 I began getting a weird echo when monitoring my voice to create a radio show.
I spent over an hour trying to figure out why a system that had been rock-solid suddenly was giving me issues. Then I happened to check that sneaky “smart monitoring” setting, which Adobe turned on by default. Once I killed that, all was back to normal.
Sigh. Don’t you hate it when an “upgrade” screws up your workflow? Why on earth would Adobe change a default behavior like this?
Turns out, I am not alone in this crappy situation. SteveG posted a note about it on the Adobe Forum, with this helpful screenshot:
Brand loyalty to a cell phone company is probably stupid, but I do kinda endorse Google Fi–Google’s mobile service. It charges a flat $10 per gigabyte of data and, if you don’t use all you’ve allotted for a particular month, you get a credit for the next month.
It’s not the cheapest plan I’ve had (on a per-gig basis), but it’s the most transparent. And its data plan works the same abroad as it does in the US.
The Google Fi’s biggest drawback is that it only works with a limited number of phones (sorry, no Apple devices).
When I moved into my first home in 1987, I partially did so to have my own clothes washer and dryer and escape the monotony and tyranny of the laundromat. I bought what would now be considered a “low efficiency,” top-loading washer that worked flawlessly for me for 14 years.
Then, my wife and I bought our first washer together–a “high efficiency” (what a load of crap), front-loading machine, by Frigidaire (the Affinity model). Since then it’s been one problem after another. (See my previous post about it.)
The washer soon developed a mildew stain on the rubber gasket on the front-loading door–despite our care with drying it out after each load and running its cleaning cycles. Turns out, this is a known issue that has affected hundreds of thousands of front-loading HE machines. There was even a class-action lawsuit about it.
To repair it is a major, expensive proposition. If you hire a pro to do it, it costs more than a new washer.
So, we bit the bullet and bought a new washer, donating the old one to a friend. We stuck with HE (big mistake), but got a top loader. Specifically, we spent about $600 at Lowe’s on a Maytag 5.3-cu ft high-efficiency top-load washer (model # MVWB835DW0). It had thousands of positive reviews and an average of 4.5 stars.
What a mistake.
From the start, my wife had trouble with lint gathering on her clothes if she hung them up to dry and did not run them through the dryer.
Then, after about a year, it began having a rotten-eggs smell after washing a load. No number of cleaning cycles would get rid of it. Online message boards are filled with complaints about this.
Final straw: This week, 14 months into our ownership of it, the machine began getting stuck in the rinse mode. Won’t go from there to spin without pausing the machine, raising the lid, and re-starting it.
And we’ve never felt that it effectively cleaned our clothes either.
All in all, a piece of crap, and an expensive piece of crap, too.
In a perfect world, I would never have to deal with Microsoft Office. With the notable exception of Excel, I can’t stand every application in that suite–especially Word and PowerPoint. I still persist in using WordPerfect for my everyday word-processing tasks. It remains a far superior piece of software.
That’s a dream world and so today I tried to install MS Office on a Windows 10 machine I recently “reset”. (Incidentally, Windows 10’s ability to reset to a clean, bloatware-free, pristine original state might be my favorite feature of the new release!) I own a licensed copy of Office Professional Plus 2013 and when I fired up the installation file, this is what I was told:
Internet connection working? Check? Enough free space? Is 1.71 TB sufficient? I know that Office is a notoriously bloated piece of crap, but it seems like even it could fit itself into 1.7 TERABYTES of free space.
So, off I go to search The Google for answers to his very generic error message. MS support pages have a “troubleshooting” tool, which was, of course, useless.
And now I’m stuck trying to cope with a crappy installer for a piece-of-crap office suite that I don’t really want on my computer.
Several years ago, we bought a high-efficiency, front-loading washer—a Frigidaire Affinity.
I have regretted it ever since.
The three main reasons that it is a crappy appliance are:
It’s impossible to keep its door seal (the rubber gasket that fits around the door to keep water from leaking out) clean. It inevitably becomes mildewy and moldy if you neglect to assiduously dry it out with a towel after each and every wash load. And once it becomes moldy, no amount of bleach or vinegar will clean it—resulting in a very expensive repair bill to replace it.
It vibrates like a sumbitch. I’ve worked on leveling it and put anti-vibration pads under it, but it still vibrates the floor so badly that you can feel it on the other side of our house. I shudder to think what it is doing to our foundation. If you don’t have a concrete floor on which to put a front-loader, I would strongly advise against installing one.
It’s inconvenient to load clothes into it. Each wash day I am literally down on my knees, feeding laundry into it.
If new washers weren’t so ding-dang expensive, I’ve had junked this one long ago.
On August 24, 2005 I created the Crappy Software blog to chronicle all the malfeasance in the world of software. I happily ran it on Blogger software running on one of my own Web servers. Then, in 2010 Google—which had bought Blogger in 2003—decreed that all Blogger blogs must run on blogspot.com.
I didn’t like entrusting control of my data to Google/Blogger, but I complied and moved Crappy Software and a couple other blogs over there. There were a few bumps in the transition, but I was basically satisfied with Blogger even as I began to use WordPress for more and more of my blogging and basic Website design needs. It’s gotten to the point now that whenever I need a quick-n-dirty Website, I slap together a WordPress installation in, like, 20 minutes.
Until the day (and I don’t even know exactly when) when Blogger decided to delete all of the images I’d uploaded between 2010 (when I moved to blogspot.com) and 2014. Dozens of images were suddenly missing. I still don’t know exactly why beyond some sort of weird clusterfuck among Blogger, Google+, and Picasa (and PicasaWeb). You see, Blogger, unbeknownst to me, was storing my new, uploaded images in PicasaWeb. Best I can guess, there was some shift in my Google account—perhaps when I activated Google plus—that disconnected Crappy Software from its PicasaWeb album.
I spent an hour or so yesterday trying to figure out exactly how it happened—following leads suggested here—but I was not able to track down Blogger’s crap move.
So, Good-Bye Blogger
And so that motivates me to bid adieu to Blogger. WordPress is a superior blogging platform. Why stick with Blogger when it’s going to do crappy stuff like this?
Many of my images are permanently lost, best I can tell. I still had all my pre-2010 images, from back when Blogger was good software. And several of the post-2010 images were still on my hard drive. It’s taken me the better part of the day to move all the text and re-upload images, but I think I’m going to be happier with WordPress as Crappy Software‘s new home.
In related news, I’ve taken advantage of the new top-level domain names (TLDs) and nabbed crappy.software for this blog. Ain’t that cool?