Skip to main content

David Mead

Context challenges between #indieweb and social media silos

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.

Example

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

Aaron Parecki

A different approach

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.

David Mead

Thanks to @vasiljevski's post I have a plugin select pulling back the value saved when editing a post on my blog.
http://www.vasiljevski.com/blog/php/how-to-set-the-selected-option-of-select-tag-from-the-php/

David Mead

Changing a plugin for Known (coding) #indieweb

2 min read

I wanted to change up how a plugin worked on my blog. Namely the Listen one.

Out-of-the-box

Looking at it after install if allowed me to capture someting I had listened too. I could link to somewhere that'd let others here it, and put in "cover art" and some notes.  All fantastic.

screenshot of Listen post

Couple of things I wanted to change:

  • artist closer to the title, and not after my notes
  • icon indicating song, podcast, etc.
  • definition between my notes and what I had listened to

Breaking stuff

So I "forked the repo" and basically spent today pulling apart and putting back togther PHP code that I had no idea did what.

I found that the 'listen types' weren't being pulled through to assign an icon to, so I commented out a large section and replaced it with a simple <select> element.  This seems to have worked, though I don't know (yet) how to retain what I selected if I edit the post.

I've now got it looking a lot more how I wanted and it sees the listen type and shows the matching icon.

screenshot of new Listen posts

Also did some more changes while I was feeling brave:

  • I added a lot more types including soundtrack and audio book
  • Changed the titles to past tense
  • Updated the edit page by matching labels to fields, wrapping fields in <p>, and changed some of the language used there too

Going forward

I've posted on the IRC that I've made the changes, so I'll see if, and how, anyone wants to merge these into the plugin.

I'd love to get Last.FM and Huffduffer integrated so they post automagically.