Copyright Notice and Notice

This is a reply to this tweet and the comments in the linked article.

@RessyM @TSI_Marc The idea to check bandwidth usage is noble but in December my movie purchases resulted in 100’s of GB of down/up data. As a cord-cutter I rely on Netflix, Apple TV, video podcasts, and streaming media direct from web sites. That means I’m a heavy user and am not likely to notice a few extra GB.

As for securing my router, how is anything truly secure these days? My firewall is constantly recording probes for known Linksys router vulnerabilities. What about the unknown ones? I’m not a security guru so I don’t monitor the latest exploits out there. My router could be compromised and I would likely not even notice it. My main concern is that they get into my network and compromise my computers. If the router or computers are used as a proxy to retrieve copyrighted content but falls within the noise level of my normal bandwidth usage, I’m just not going to know.

Continue reading “Copyright Notice and Notice”

Finally, the tech press is willing to talk about Apple’s software quality

Anybody who follows me on Twitter knows I document many of my problems with Apple software and occasionally hardware. But I don’t mention every little problem because that would be too time consuming and I’d have 0 followers in a short time. That means that seldom a day goes by that I’m not fighting a problem on one of my computers. It’s exhausting.

It was so bad last year that I actually wrote a polite challenge to Tim Cook, with the same hope of winning the lottery, that he would listen and do something. Apple’s response was to block my email address. I took that as a “no.”

Continue reading “Finally, the tech press is willing to talk about Apple’s software quality”

Oh Yosemite…

BBEdit could no longer open Perl documentation inline. The Unix perldoc command, that BBEdit depends on, had no execute permissions. How permissions keep getting broken in OS X is one of Apple’s “endearing” mysteries.

No problemo…I’ll just run Disk Utility’s Repair Permissions command. It doesn’t indicate anything relevant has been updated but, sure enough, the execute permissions for perldoc and other commands have been fixed. Is Apple too embarrassed to list all the broken permissions it’s fixing?