I’ve been working a bit on PhpFlickr CLI lately, which is my little tool for interacting with Flickr. So far, it only adds checksums to photos (as machine tags), as a precursor to making a duplicate-finder for Flickr. I also want to use the checksums for adding links to and from Wikimedia Commons (so that photos I’ve uploaded there are linked to their versions on Flickr, and on Flickr they’re linked to Commons).
I’m pleased to see Flickr is going do away with their massive free storage:
Beginning January 8, 2019, Free accounts will be limited to 1,000 photos and videos. If you need unlimited storage, you’ll need to upgrade to Flickr Pro.
This is annoying for people who rely on it, but if a service is good then it’s worth paying for.
That said, and even though I do have a paid Flickr account, I think I’m going to stick to using my own Piwigo installation from now on.
I thought I’d help out and try to update the Flickr2Piwigo plugin to support OAuth, but having done so I now seem to have become a maintainer of the thing. So that’s good. I’ve just released version 1.3.0.
I’ll try to see to all the outstanding bug reports (well, there’s only one at the moment). And then perhaps add some extra features (support for approximate dates? automatic downloading? download of other people’s photos?).
I’ve decided to try to bring the Flickr2Piwigo plugin up to date in order to support OAuth (Flickr’s old system of authentication was turned off in the middle of last year). I’ve been tinkering with getting the PhpFlickr library working properly lately (which is what Flickr2Piwigo uses to talk to Flickr), and although there’s lots more to do to it I’ve at least got the OAuth parts working (thanks to the lusitanian/oauth package). So now I’m going to add this to the Flickr2Piwigo.
There’s no support for Composer in Piwigo, so I’m not really sure how this is going to work. Probably some custom distribution-generation process; I’ll worry about that later. Hopefully we’ll not resort to committing
Once this is working, I’ll go back to PhpFlickr and write some better documentation (probably Read The Docs) and fix up the caching system (it’s a bespoke oddity at the moment, that I think should be replaced with simple PSR-6 support).
I’ve just tagged version 4.1.0 of my new fork of the PhpFlickr package. It introduces oauth support, and hopefully improves the documentation of the user authentication process. This release deprecates some old behaviour, but I hope it doesn’t break any. Bug reports are welcome!
There are some parts that are still not converted to the new request flow, but I’ll get to them next.
I’ve been moving all my photos to Flickr lately. It’s been a long process, one complicated by the fact that it seems silly to run my own WordPress installation (and things like ArchivesWiki) if I’m not going to bother hosting everything myself. Of course, that’s not really very logical, and so I’ve decided that it’s perfectly okay to host photos on Flickr, videos on YouTube, and all the text (and miscellaneous) stuff here on my own server.
This week is the first time for seven years that I’ve not had a job to go to (and not been on holiday). So of course I’m sitting at a computer working on some code, drinking a coffee. The location (Parlapa) is better than the office, and more importantly my mind is not full of thoughts of work-code; it’s time to focus on projects that make me feel good.
Which is a tricky proposition, of course, because there are so many that I’d like to put time into, and it’s hard to prioritise. This morning I’ve been attempting to figure out why a cronjob I’ve got running on Tool Labs isn’t sending me emails. Yesterday I was scanning a small stack of photos that my dad took in Spain in 1975. Next I shall continue with a little website I’ve been working on to make it easier to search and browse books on Wikisource (almost all of the data for which is coming from Wikidata). But then there’s this little tool that I wrote a while ago for producing HTML and LaTeX albums from Flickr groups; it needs expanding and improving. Not to mention my desire to explore AtoM some more, especially in relation to how we might be able to use it while working on the Maps for Lost Towns Geogeeks project.
See? Too many things. That’s why jobs are good: one need just turn up every morning and have a ready-made list of what’s-to-be-done.