Post work outing drink
An Englishman abroad - Been working with the web since the 90's, main focus now is UX/UI. Moved to Cleveland, Ohio in 2001.
Oh crap. Now I only seem to be able to buy Newcastle Brown Ale, brewed by Lagunitas!
UK beers are really hard to find now :-(
#drink #beer #british
2 min read
My utopian dream of owning all my content would be to post it on my blog first. Syndicating to whatever social media silo's I choose afterwards.
This isn't a reality as some of these silos (Instagram) don't allow posting apart through their apps.
This forces me to accept their context for my content if I consume it into my site, from them.
On my blog I like to capture what I ate or drank. In that post I can have a photo of what I consumed along with a description. It's a thing, don't 'at' me.
On my blog it has context. You can see all the other eat/drink posts on thier own or mixed in with everything else. I can include links to the place where I bought it, who makes it, or related posts.
Instagram's context is its a photo with an optional description. It doesn't matter what it's of. It won't contain links to anything.
So when I get something from Instagram on my blog it has to have the context of 'photo'.
I jump through hoops changing content to fit my context. Swapping from a 'photo' post to a 'food' post, adding links, reformatting text.
I'm not the only one who goes through this
there are a handful of photos of food I've posted *on* Instagram that i later want to go and add to the actual food post
Going forward I'm going to try something else. Displace the friction to the silo. I'm going to try to enforce the habit of posting content first on my blog.
From there I'll syndicate where I can (Twitter, Flickr), create a new post using the silo's app where I can't (Instagram).
That way the only edits I have to do my end is add a
u-syndication link to the post from Instagram. This does mean I have to add a spot to do that in the Known Food plugin - but's that a different post.