* Posts by Mo McRoberts

12 posts • joined 26 Jun 2009

Google puts Dr Who's Tardis onto Street View - and you can get INSIDE

Mo McRoberts

Hold on, this is a couple of months old.

The most recent Street View addition is the inside of BBC Television Centre:


OS X Mavericks mail client spews INFINITE SPAM

Mo McRoberts

Given that Symphony was discontinued last year, the solution is presumably to install an up-to-date version of OpenOffice…

Yay for iOS 6.1, grey Wi-Fi iPhone bug is fix- AWW, SNAP

Mo McRoberts

I wonder of those whose WiFi doesn't work post-upgrade have considered just speaking to Apple about it? It's not like it's an intermittent thing or anything — take it into the Genius Bar, show them it greyed out, and you should get it swapped as defective pretty sharpish. IME they'll do a like-for-like swap for much less severe issues…

Apple vanishes MySQL from Mac OS X Lion Server

Mo McRoberts

Or to look at it another way…

…you no longer have to wait for Apple to provide timely updates to a piece of software which is UTTERLY trivial to install from the vendor using the provided native packages.

Apple bets on Mac-only photo land grab with Aperture 3

Mo McRoberts


Aperture isn't a competitor to Photoshop. It's a competitor to Lightroom.

Or, as Adobe wants you to call it, "Adobe Photoshop Lightroom".

So, I suppose, if you pay attention to what Adobe Marketing says, it IS a competitor to Photoshop. sigh.

Google doppelgänger casts riddle over interwebs

Mo McRoberts

It's really _really_ simple

It's the domain used in the PTR records in the rDNS of Google's many IPs.

That's why it's showing up.

Really, it's no more complicated than that.

Apple bans geo loco ads on iPhone, iPad*

Mo McRoberts

UX issue

It's a straightforward UX issue

If apps request location information, the user must confirm. This is fine if the app uses location information for useful stuff.

However, if the app JUST uses it for ads, then it makes the advertising even more obnoxious than before.

A New Year's call to Apple: publish and be damned

Mo McRoberts


A documented API is considered by Apple to be like a contract. By documenting it, they are promising that they will try their hardest not to change it in any incompatible way in the future, and any deviation from this would be considered a bug (and, depending on the impact, a showstopper).

There are lots of reasons why an undocumented API may remain in that state. Often it’s because the API as it currently exists only works properly in a limited subset of the scenarios which the parameters suggest it might. Or it might be that it’s a poor fit with the rest of the API in a given area. Or it’s because the developers intend to change it in the not hugely distant future.

Apple regularly opens up its private APIs once they release maturity if there’s a solid case for doing so, and did precisely this when Snow Leopard was released (Quick Look, for example, moved from PrivateFrameworks to being part of QuartzCore with the arrival of 10.6).

As the old adage goes… don’t make a promise you can’t keep.

Breaching Fort Apache.org - What went wrong?

This post has been deleted by a moderator

Apple sneaks malware protection into Snow Leopard

Mo McRoberts

Third-party apps

The quarantine mechanism, that this is an extension of, is quite well-documented:


(or Google “LSFileQuarantineEnabled”).

If this researcher had looked hard enough, he may or may not have spotted another .plist nearby.

Wikipedia's Gallery guy hung up to dry?

Mo McRoberts


“But such a monumental investment in digitization would be futile if the Gallery's work instantly escapes its control once it appears on their website.”

No it wouldn't.

It would, indeed, make it entirely worthwhile.

Copyfraud: Poisoning the public domain

Mo McRoberts


Is “the Complete Works of Shakespeare”, packaged in printed book form copyfraud?


What about when it's an iPhone application? Or in nicely-formatted PDF?


Actually, the only point at which it's copyfraud is if somebody takes a public domain work, republishes it in some way, and then uses that to claim copyright over the original public domain version. The author here doesn't seem too bothered by that scenario, however; more the fact that Google's system makes the assumption that if a copyrighted edition exists, then that precludes a public domain version existing, until some manual intervention tells it otherwise. This is called “making sure you don't get sued for unauthorised redistribution of copyright-protected works”. Google Books is not Project Gutenberg.

In Flickr's case, it's taken—what—4 years for this to crop up? And even then, it's an issue with ONE site with one very specific class of images—those which legally CANNOT be copyrighted at any point. That's a pretty rare occurrence in the world of Flickr, and it's good that they both recognised it and made provision for it.

Creative Commons’ stance is quite obviously about recognition more than anything. Huge numbers of people don't know what “Public domain” actually means, and this is confused even more by the use of terms like "copyleft" (which is often assumed by the layman to mean 'not copyrighted' rather than 'a license which deliberately subverts the usual protections of copyright'). In contrast, "Creative Commons" has become recognisable as "you may, possibly with some conditions depending upon who you are, do various things with this work including modification and redistribution"—with different variants of CC indicating who is permitted to do things and what they're permitted to do. CCPD, therefore, neatly fits into this with a variant that indicates “anybody” and “anything” respectively.


Biting the hand that feeds IT © 1998–2022