Tag: api

Posted on
by

I just paid my annual Flickr pro fee. Very happy to do it. I like taking pictures although I don’t think of myself as a photographer. I am not really interested in the technical aspects. I use photos in the same way as blogging. To think about something, or note it, remember it, share it, or collect it for later. A diary or commonplace if you like.

I was also really pleased to see Flickr’s blog around it’s continuing support for Creative Commons and the announcement of the Flickr Foundation.

We believe the establishment of a non-profit Flickr Foundation will combine with Flickr to properly preserve and care for the Flickr Commons archive, support Commons members to collaborate in a true 21st-century Commons, and plan for the very long-term health and longevity of the entire Flickr collection. We’re also in the early stages of imagining other educational and curatorial initiatives to highlight and share the power of photography for decades to come.

The other thing I love about Flickr is it’s API. I am no more a programmer than I am a photographer. But I have had a lot of fun with the Flickr api.

One of the reasons I’ve managed to play with this API is its consistency. Other APIs I’ve used with have gone away, changed or added authentication too difficult for me to grasp. Given that I use them occasionally I am often flummoxed by changes. I only notice then when something that worked stops working.

What I love about Flickr is then threefold: a solid and consistent service that I pay for, the api(solid & constant too) and Creative Commons I get for free.

Flickr’s future has been in doubt a few times since I started in 2004, Interface changes caused some consternation. Flickr has managed to continue when other services have gone. I hope I’ll be paying for it for a good few more years.

 

Posted on
by
Replied to

The sky is grey here today so I took a trip through my flickr. Modified a script to pull down my photos flickr thinks is blue.

There is nothing I could see in the flickr api to filter colours as there is in the search but I noticed the url for the search contains text=&color_codes=7 so I added that in. Sees to have worked.

Posted on
by

Not because my photos are in anyway professional, but because of the wonderful things Flickr does. Flickr allows me to store and organise my photos. I can look at pictures by friends, acquaintances and all sorts of groups.

Most importantly Flickr curates and organises creative commons licensed and public domain photos. These are searchable and Flickr give access to them via an API that is useful and usable by non-professionals. I’ve had an amazing amount of fun and use (professionally as a teacher). To me Flickr is an important part of the web, I have a pro account to support that.

If you use Flickr and don’t have a pro account you can get 25% off with the code 25in2019 or use this link.

Posted on
by

It’s also example of doing something that only I would want to do and yet having that thing echo into eternity without any additional effort.

from: API Nirvana – The Content – Bionic Teaching

Tom Woodward writing about his love of APIs, one of a series of posts. I love the idea of playing with things that do something that only I would want to do.

If you have a slightly geeky interest in technology & edu tech Bionic Teaching is a great blog to read.

I’ve a long term casual interest in playing with APIs, and love trying out some of the stuff Tom blogs about. In a timely fashion wordPress 4.7 came out today, including:

WordPress 4.7 comes with REST API endpoints for posts, comments, terms, users, meta, and settings.

from: WordPress 4.7 “Vaughan”.

This is the same API that Tom blogged about (I guess he was using a plugin). The opening up of WordPress sites via an API that an amateur like myself can use it welcome. Over the past few years several sites with interesting APIs move to make them harder to access with out a deeper knowledge than I have (twitter, instagram…).

I had a quick play with the WordPress api making a page that lists recent posts on 3 of my blogs, including this one. 1

wp-json-render

I guess this sort of thing is a minority interest, but I find it enjoyable and although I am never going to be a programmer, helpful in getting a better understanding of how technology can work.

Featured image on this post, one of my own turned up in a search for echo. test1-echo.tif | Using Image Bending in Audacity – CogDogBlo… | John Johnston | Flickr

 

  1. I added the Better REST API Featured Images WordPress Plugin to et the images following a hint on Tom’s post. ↩

Posted on
by

I’ve got a few IFTTT recipes on the go. IFTT is a useful service from linking up and pushing information around online services.

In the last week or so I’ve seen a couple of posts about the service, received an email and had an interesting incident so though it worth a post.

First I read this:

Kin Lane mentioned that IFTTT, a service entirely built on APIs, doesn’t have an API. That bothered Kin and the more I thought about it it bothered me. So I figured I’d start disentangling myself from IFTTT.

from: Shifting out of IFTTT – Bionic Teaching

I then had the problem illustrated by the screenshot at the side of the post. I have a recipe that posts my instagram photos to a blog. The blog then tweets them out and another recipe posts the images on to Flickr. This seemed to go a bit off the wall posted multiple times for a couple of photos and therefore my twitter timeline was filled with repeats.

I would rather this did not happen.

Next this:

Imagine if your sewer pipe started demanding that you make major changes in your diet.

Now imagine that it got a lawyer and started asking you to sign things.

from: My Heroic and Lazy Stand Against IFTTT (Pinboard Blog).

Pinboard is one of my favourite online services. I got an email from IFTTT saying that they would no longer be supporting pinboard unless pinboard made changes to their service.

All this got me thinking that there might be a way to do this without IFTTT. Most of my recipes are for pinboard, but I though to start with something that might be simpler.

Photo Flow

A while back I blogged Make you own SPLOT about a flow powered by IFTTT from instagram to blog to flickr. I like the system, but wonderd if I could DIY without IFTTT.

A while back I’d made a page to grab my instagram photos so I thought I could reuse that to create an RSS feed and then pull that into the photo blog using the FeedWordPress plugin. It was not too hard.

The feed is produced with php file and basically is this( I’ve taken out some caching code):

echo '<?xml version="1.0" encoding="UTF-8" ?> <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> <channel>  <title>Insta john</title>  <description>some instagrams</description>  <link>https://www.instagram.com/troutcolor/</link> <atom:link href="http://johnjohnston.info/oddsandends/instarss/" rel="self" type="application/rss+xml" />';    
$url="https://api.instagram.com/v1/users/7835090/media/recent/?client_id_=CLIENT-ID-HERE&count=2"
$json =file_get_contents($url);
$jsonA=json_decode($json, TRUE);
foreach ($jsonA['data'] as $post) {
 echo '<item>';
    echo '<title>'.($post['caption']['text']).'</title>';
    echo'<description><![CDATA[ <img src="'.($post['images']['standard_resolution']['url']).'"> from <a href="'.$post['link'].'">instagram</a> ]]> </description>';
    echo '<link>'.$post['link'].'</link> <guid>'.$post['link'].'</guid>  </item>';
}
echo ' </channel> </rss>';

I’d guess this is not the prettiest piece of code but it produces a short (2 items) RSS feed that FeedWordPress can use.

I’ve also installed the FeedWordPress Advanced FiltersPlugin after reading about it here: Field Botany WordPress Site Breakdown – Bionic Teaching. This allows me to copy the image onto the WordPress site as opposed to keeping it in instagram. It also lets me add it as the featured image which works well with the theme on that blog. Until I am sure it is all working I am posting the photos as pending review, but if it all looks good after a few more pictures I’ll flick the switch and let it run.

There may be trouble ahead

I had just grabbed the code from my old page, including the info needed to connect to instagram’s api which I had set up before. So I checked out the Instagram API page where I read:

Any app created before Nov 17, 2015 will continue to function until June 2016. After June 2016, the app will automatically be moved to Sandbox Mode if it wasn’t approved through the review process.

from: Instagram Developer Documentation

Which sort of sounds like the API will be for more professional sorts than myself. I guess I’ll find out in June.

The other news was that IFTTT has backtracked allowing users to continue to use pinboard recipes without asking pinboard change its system. Hello Pinboard Customers, From Linden Tibbets, the CEO of IFTTT a blog post by Kin Lane, has the details. The post also repeats the waring that IFTTT, by not having an API itself IFTTT might not be something to depend on.

All of this change reminds me of how shaky a foundation we are building our online worlds on. This makes IndieWeb idea even more attractive.