Whilst browsing the Google Search Console for this site I noticed that some of my older image galleries were returning errors. This gallery is run by 15 year old PHP code that I occasionally have to hack to keep running on newer versions of PHP so it was not a complete surprise that it might need some fixing. I should pay more attention to webserver upgrade notices though as the logs indicate it has been broken since 1st October.
The error was a bit puzzling at first:
PHP Parse error: syntax error, unexpected end of file
but eventually a helpful StackOverflow page made me realise that I needed to replace all instances of
<?php and the problem was solved.
During testing of the fix I found a more serious problem. All my links to picasaweb albums where I had hosted my photos from 2008 and 2009 were dead. This was unexpected since Picasa was run by Google and even though they replaced the service with Google Plus/Photos, I knew all my photos and albums were still online at the latest incarnation of Google’s service and I had trusted that Google, a company who place high importance on links for generating their search results, would not break links. It turns out that my trust was mis-placed as Google had broken some links but not others. Any link containing a username was broken but a userid would still work. So, if I could find my user id I could restore the links. Fortunately my Picasa user id turned out to be the same as my Google Plus user id, and because this was only a small number of posts over a 2 year period I could work through each one and replace the user name with that id to repair the link. There were a few direct links to photos that I was unable to repair because the URL did not contain my username.
These problems make me want to reconsider whether my current photo hosting solution with Flickr is the right one. While WordPress has improved since 2015, and has add-on features to make photograph-heavy websites go faster, those add-ons are still third-party integrations so these potential problems of what is known as “link rot” remain. I have recently been thinking about some of the other disadvantages of using WordPress, but I shall leave those for another post.
Fortune smiled on me in the tennis club ballot this year and despite life being quite busy around the beginning of July, I was able to spend a very enjoyable day at The All-England Club watching some tremendous tennis.
Continue reading “The Championships, Wimbledon”
Despite being an overcast day, the clouds cleared late afternoon and treated us to a spectacular Cornish sunset. The rest of the week featured plenty of different weathers, from glorious sunshine to driving rain.
As of last week, the toobusyto.org.uk domain is now configured with a Sender Policy Framework (SPF) DNS record. This is a special type of DNS record which identifies which mail servers are allowed to send mail on behalf of toobusyto.org.uk users.
The aim of SPF is to prevent the unauthorised impersonation of users, a tactic frequently used by spammers. In practice it is not reliable because it can cause problems for a number of legitimate use cases related to mail forwarding, including mailing lists. In fact, Google explicitly recommends configuring an SPF record for “soft” failure rather than hard failure because of these issues.
The record was easy to setup once I realised which servers I needed to include. I send mail from toobusyto.org.uk directly via mail.toobusyto.org.uk, which is a CNAME to another system, and occasionally from Gmail’s web interface. Google have clear instructions on how to permission the latter but use of CNAMEs in SPF is discouraged to prevent receiving servers needing to perform an excessive number of DNS lookups so it is necessary to hardcode the name of the target of the CNAME. There is a risk the two can become out of sync but hopefully this is mitigated by the proximity of the two records in the BIND file. You can query the current record using your favourite DNS client but for the record the initial setup is:
; SPF record
toobusyto.org.uk. IN TXT "v=spf1 a:saturn.retrosnub.co.uk mx include:_spf.google.com ~all"
The result is that Gmail can now successfully authenticate me as a sender and for many users no longer shows a red question mark next to my name. Some experimentation has shown that the red question mark can still be present where I have emailed firstname.lastname@example.org and he or she forwards to a Gmail account because their.domain.com is not authorised to send mail on behalf of toobusyto.org.uk. This is actually the no worse than those users experienced prior to the configuration of the SPF record and some quick research turned up some forum posts that indicate there are potentially steps email forwarding services can do to mitigate this, although it was not clear whether the mitigation was feasible and/or effective.
One of the power features lacking in Apple’s Photos application is the ability to tweak the built-in conversion from RAW to JPEG. The now-discontinued Aperture application allowed manual control of these RAW conversion settings giving the photographer the ability work with more of the captured data to unlock hidden detail without needing a separate specialist application.
RAW Power is a Photos extension that enables this fine-tuning from within Photos. I learned from a YouTube interview with the Developer that he is the former dev lead for Aperture, having left Apple over a year ago, which suggests to me that Apple will likely cede advanced editing functionality to third party developers as I previously speculated.
As a tool with a very specific purpose, its focus makes it simple and effective to use. The interface is clearly laid out and performance nimble, and if it becomes apparent that RAW modifications are not able to improve the photo then you can cancel your edits and return to Photos with one-click.
RAW Power currently costs £9.99, and although this is labelled as promotional pricing, it is my opinion this represents very good value.
The first four days there were constant blue skies ensuring fantastic views of the beautiful Alpine scenery, including the iconic Matterhorn. This was my second ski holiday in the Italian Alps and once again the pistes were quiet, the lift queues non-existent, the food delicious and the coffee excellent. The connection to Zermatt also provided a huge ski area and diversity of slopes.
When the weather was slightly less good, we also enjoyed warm and friendly mountain hospitality.
It has been almost six months since our visit to Wellington. After travelling through the beautiful vistas of the South Island it was great to finish our holiday with some hip cocktail bars and late night espresso.
In moving to my fifth iPhone I decided it was time to try a fresh install instead of transferring state from my previous one. Apple’s transfer process has always worked works seamlessly but that Star Trek-like transportation of your old phone to the new makes the new one seem, well a little less new somehow. Previously I would have feared losing something small but vital by not using the transfer process but with so much now synchronised between devices by iCloud, it seemed that the most painful and important items were covered. My willingness to experiment was also mitigated by the knowledge that if it all went wrong I could still re-install the new phone from my old backup.
Without the need to wait for a gigabyte of data to be transferred to the new phone, I was up and running very quickly and enjoyed seeing what differences there are between an out-of-the box configuration and my own. With the exception of turning off the sound and vibration notifications for new email, I have customised very little to start with: I want to see if there are any settings or features I have previously overlooked because of some decision I made 7 years ago. Working through my list of apps and choosing to only reinstall those I know I have used recently was also enlightening—there were applications I had forgotten existed buried in never-opened folders, and including some that now crash on startup. I noticed others that are no longer being updated but the developers have instead issued a whole new app instead. I learned that the telltale sign for this is when you tap on the application in your “purchased” list and it fails to display anything about it.
Having chosen which apps would survive the migration and downloaded them all, the main pain point was having to re-authenticate in all of them. The reduced number of apps kept this manageable and I would guess about 50% enabled the use of iCloud Keychain which made it a two-tap process. Given the tedious and error prone nature of typing in a complex password onto a phone keyboard I am shocked that the other 50% do not enable this. Those apps which forced me to lookup and retype my password are certainly strong candidates for deletion if there is an alternative.
By not restoring from backup, any applications that store state locally and not in the cloud would lose their data. I was a little worried about my Angry Birds progress but then realised I had not played the game in a very long time anyway, and so far I have discovered only one application which stores data I would like to keep. It is a free app and its paid for version supports data export, which seems fair enough. WhatsApp messages were restored from its own iCloud backup (which it performs nightly) but I did lose my SMS and iMessage history (going back to 2008). Recent iMessages are on my mac anyway and after reviewing the older messages they were all very temporally contextual—“I am here / outside, where are you?”—type stuff. It is noticeable how much longer messages have become recently, perhaps an inevitable consequence of removing the 160 character limit of SMS.
In conclusion, unless you have apps or games that depend on local data, setting up from scratch was not at all painful and it felt really good to have a spring clean. Deleting something always requires metal energy to assess its value, or downside of its loss, and with storage so cheap it is rarely worth the effort. Consequently we accumulate bits and bytes rather too easily, and sometimes a platform migration is a good moment to assess what is no longer required, and start afresh.
Subscribing to a blog via RSS remains a niche and decidedly geeky activity. Having said that, Apple devices now come with a built-in News.app which, for all the usual Apple gloss, does use RSS. To view this blog in Apple News, visit this link on your iPhone or iPad and tap the + sign in the top right hand corner to subscribe.
If you do not use News.app, Safari’s shared links feature (the @ tab in the bookmarks pane) also allows you to subscribe to this and many other blogs.
In my post, A macOS Photo Editing Workflow, I admitted to taking the somewhat unorthodox position of capturing both RAW and JPEG versions in-camera and normally working with only the JPEG version. The conventional wisdom in photography is that RAW is the more flexible option, providing greater opportunity for correcting and improving the image in post-processing than when the camera is allowed to make all the decisions on your behalf. There are traditional reasons for not using RAW files such as the increased file size, but these are normally only relevant in specific situations—there seems to be few generic reasons not to use RAW unless you are operating under specific constraints.
I was therefore intrigued to see a recent article entitled, Is RAW Dead? in Photography Week. In addition to examining all the usual issues, it points out that in-camera JPEGs are now so good that in the majority of situations the camera will probably do a better, or at least no-worse, job of rendering the final image than you. This makes sense: unless you actively tweak the settings in your RAW processor then you are simply handing the conversion over from one algorithm (your camera) to another (your RAW processor), and while in the past the processing ability of a camera was limited compared to that of a PC, the advances in mobile chips and image processing have removed the PC’s previous advantage. Moreover, since the JPEG output is the version seen by potential buyers and new owners of their products, the camera companies themselves are highly incentivised to make the JPEG output as attractive as possible. The article does list a specific benefit of RAW as being able to recover an additional 1-2 stops of highlights and shadow detail compared to JPEG, although it also points out that a wider range can be obtained using the camera’s automatic exposure bracketing or even built-in HDR.
For the moment I will be having my cake and eating it by using RAW+JPEG: JPEG for convenience but with the RAW available as an option should the trade-offs and technology change in the future.
The Lonely Planet guided us to a fantastic morning coffee stop en route from Motueka to Nelson, the Jester House Café. Despite being a popular tourist spot, the car park was not large and I was very glad we were the only camper van attempting to use it! In addition to three varieties of dairy-free cake they had excellent coffee and some impressively large native eels in the stream outside.
Our stop in Picton was only long enough to enjoy its relaxed ambience and take a short hike around the awesomely beautiful harbour. Our early morning sail out of the harbour was also blessed with fine weather and the crossing to Wellington allowed for some more fine views.
This is part of a series of posts describing my move from Apple’s Aperture to Photos.app for managing and editing digital photographs. Previous entries include a feature comparison, third party applications and extensions.
Although Aperture has not received a significant update in three years, I did not feel it was deficient in any way. Having now used a number of recently released other applications in the last few months I have now become aware that Aperture does lag behind the state of the art and it is time to update my toolbox. Another consequence of using different tools is that I now recognise that Aperture is in fact three products in one: RAW converter, photo manager and editor. Given the convenience and advantages of using Apple’s built-in image management, including the iCloud library for device synchronisation, it seems obvious that Apple’s Photos.app should be the starting point for a replacement solution.
When editing, for many photographs I found I could produce the same or better results in Photos.app compared to Aperture, unless I needed to tweak the RAW conversion. Photos’ superior plugin implementation also means that when it cannot get the job done alone it only takes one click to call out to another application. Consequently while Aperture has more built-in tools than Photos.app, the high quality of external applications means that Photos.app plus plugins can get better overall results with no loss of efficiency.
Photos.app handles RAW files but offers no editing abilities above and beyond what is offered for JPEGs. Given the additional time and bandwidth required to upload them to iCloud, along with the greater space consumption on iCloud storage, there seems to be no benefit to offset those costs and I have decided not to store RAW files in Photos.app. Storing my RAW files in a standard folder hierarchy without the obfuscation of a management application also makes it very easy to move these files between tools and platforms in the future.
I have been using Nikon’s Capture NX-D software to convert the RAW files into JPEGs. This is free from Nikon and produces lovely JPEGs which match what is shown on the camera screen, but I found too slow and too difficult to use to make even the most basic edits. I tried a 30 day demo of DxO Optics Pro 10 which produced reasonable JPEGs and was very good at improving certain aspects of a photo (noise removal and some lighting scenarios) but for the average photo is no improvement on the built-in Apple RAW conversion, and not as aesthetically pleasing as Capture NX-D.
In light of these findings, on recent shoots when SD card space has not been an issue, I have set my camera to store RAW+JPEG rather than RAW-only. I have then imported the camera JPEGs directly into Photos.app and reserved RAW edits for only those where the in-camera JPEG is not good enough. In that situation I do then import the RAW into Photos.app and use the excellent DxO Optics Pro for Photos plugin if I think that will solve the problem, or resign myself to fiddle with Capture NX-D if necessary.