Please FIX YOUR DAMN BUFFERING on audio samples.
P.S. Or, maybe I can start buying all tracks from Amazon.com? Now there’s an idea.
Lately I’ve been working on a plan for stepping up my creative activities, which includes making some adjustments to my online presence. I’ll spare you the tedious details, and only mention that one step of the plan involved creating a new Yahoo Mail account that I could associate with an already existing Flickr account.
Well, my plan has been foiled, thanks to a new and very stupid Yahoo account creation policy: It turns out that, as of recently, Yahoo will no longer allow someone to set up a mail account without providing a mobile phone number. I don’t have one of those damned things, nor do I want one. Even if I could get one and keep it running for a reasonable price, having it would make it easier for people to bother me, which I don’t want. And (seriously people) – text messages??!?! No way.
I may be able to work around this problem some other way, involving using an existing, unused Yahoo Mail account instead of creating a new one. That is assuming there is no further demand for cell phone information when I set up the association with the already-existing Flickr account—an assumption which, as of today, I no longer consider safe.
An additional, worrisome question is whether Yahoo plans to extend their Nazi-esque mobile phone policy to existing users in general. As of today, they have not done that—I just successfully logged out of my primary Yahoo Mail account and then logged back in. They do pester with the “what’s your mobile phone number” thing at every single login now, though. If they make that mandatory, I’d be faced with the very unwelcome choice of abandoning my old accounts entirely, or shelling out the damn money to buy one of these goddamned phones. (I notice WordPress is getting pretty pushy about mobile phone authentication as well, although I don’t believe they require a number just to create an account.)
It actually makes me wonder if Yahoo! is getting a kickback from the phone companies to do this. It wouldn’t be at all surprising, would it? I can certainly believe that the large phone companies, all of whom are scum, would stoop to this sort of strategy.
As mentioned in previous posts I’ve been having recurring issues with Apple’s Time Machine backup software over the years. The latest issue proved to be the final straw. The internal drive in my iMac crashed, the local Apple dealer replaced it with a new drive and also did me the “favor” of installing Snow Leopard on it. I then restored my previously saved files using Time Machine, when prompted to by Setup Assistant.
Time Machine never worked right after that. It would typically try to back up tens of thousands of files every single time, often taking more than a half hour, which resulted in Time Machine being active more than 50% of the time, and that just doesn’t work. There are too many things that can go wrong when Time Machine is running—having it run more than half of the time is just asking for trouble. I tried and tried to get this fixed, going through every damned solution on pondini.org, including reinstalling Snow Leopard myself, and NOTHING worked.
So now I’m going to give up. Arrived via FedEx today is a brand new Synology DS1513+, with four 4-terabyte hard drives loaded into it. The setup routine recommends having a complete backup prior to proceeding, so I am doing one last Time Machine backup prior to formatting those four drives into a RAID array which will then be used to back up this system. 12 terabytes of space ought to be enough to last me for a while, but if I run short I can always add another drive to the array and bring it up to 16. WΩΩt!
Getting the thing put together and hooked up was pretty easy. My only complaint is that the little fastening bars on the side of each disk slider doohickey are made of plastic, which suggests a high likelihood of breakage over the long-term. It also seems that the locking procedure for the individual slider doohickeys are not quite idiot-proof, although once you figure out what can go wrong it’s easy enough to avoid (i.e., it’s the sort of mistake that can only be made once).
Anyway. Time Machine is about halfway through what’s recently been roughly a 20-minute process. I’ve been keeping it turned off most of the time and just running one backup manually each evening. Moving forward I’ll be using Carbon Copy Cloner to handle the backups onto the array. Who knows if I’ll run into any issues. Hopefully this will work out ok.
One question that pops into my mind…am I going to get to name the volume? If so, I’m leaning towards “Utopia”. Then again, that sort of optimism may be tempting fate. Maybe I’d be better off with a nice, pessimistic name like “Purgatory.” ;)
It’s been a long time since I was there last, but when I attempted today to pull up the classic website annoyances.org, all I got was the message “Annoyances.org is temporarily down for maintainance [sic] and will return shortly.” But, based on accounts posted here in early 2013, it appears that the temporariness of that maintenance is getting pretty non-temporary.
One poster at that Majorgeeks link very helpfully posted the link to the Annoyances website via the Internet Wayback Machine: http://wayback.archive.org/web/*/annoyances.org
Using that, we can determine that the issue started right around the beginning of the year, 2013, and has been going on ever since. To access an actual archive of the site, you’ll need to go back to late 2012 or earlier.
I wonder what other cool, 1990’s-era websites I always used to like have quietly disappeared like that.
Back a few years ago, I idly wondered how long it would take to securely erase a 1 terabyte hard drive. I had no idea at the time. More recently, I gained some real-world experience with something similar to this.
Due to having (surprise surprise) Time Machine problems, I at one point decided it was necessary to zero out my Time Machine drive. Why? Because I’d heard somewhere that zeroing a drive will “map out” any bad sectors on the drive, preventing them from being used once the format is complete. An ordinary format supposedly won’t do that.
The drive in question was a four terabyte drive. It took about four days for Disk Utility to zero that sucker.
A 7-pass wipe should take about 7 times as long, which would be about 28 days. And the most secure option, which I believe uses a 35-pass wipe (don’t take my word for it, though), well…that would take about 140 days. Dividing that by four, you’d end up with about 35 days for a most-secure wipe of a terabyte drive, or about a week for a less obsessive 7-pass wipe. This is assuming that it always takes the same amount of time to do a single pass over any drive of a given volume. I imagine that is not true in reality–some drives would go faster than others, due to inherent differences in drive performance and the amount of bad sectors encountered during the process.
This effectively disproves the, “Quick! The cops are here, wipe that drive before they grab the computer 5 seconds from now!” bulltweet that we used to see in the movies.
(As for that four terabyte drive that I zeroed out: Opinions differ as to whether that process will actually map out bad sectors on the drive. I was unable to tell if it had any significant effect at all, and suspect the entire exercise may have been a waste of time. And I’m still having Time Machine problems.)
Sick of the way Firefox updates itself every month or two?
A while ago, I gave in and decided to just let it do its thing—resisting the constant onslaught of upgrades was getting to be a bit of a pain. And, for a while, it worked out ok.
Then this morning my work computer upgraded itself to Firefox 29, which…well. I’m considering going back to 28. I haven’t decided yet. However, if I do, the following link will end up being useful:
That contains downloadable copies of what appear to be ALL Firefox versions. They are organized by version, then subdivided into platform, and subdivided further by language. Myself, I’d be wanting the “en-US” version. The final folder contains either a DMG for Mac version, a couple of EXE files on the Windows versions, or a compressed TAR for Linux.
Happy downgrading! :)