Skip to main content

David Mead

Updating Known to Version: 0.12.2

2 min read

With the IndieWeb Summit going on, I thought it a good time to update this blog to the latest version.

Steps

  • backed up the MySQL database for the site
  • copied the site, via FTP, to my local machine
  • downloaded latest zipped file from https://withknown.marcus-povey.co.uk/
  • unzipped and FTP’d new files over to server, apart from the Uploads and Configuration folders
  • refreshed in browser and voila! content is still there
  • revoked all IndiePub account access (not needed but wanted a fresh start on this build) and logged back in to:
  • added back in Food and Listen plugins from my local backup

Going forward

So far so good. OwnYourGram still doesn't want to work with my server for some reason. Nothing is being pulled in to Together so maybe that needs a little time.

The most notable changes are tidying up of the settings and configuration sections which looks great. There's also a new (updated?) editor which is cleaner and works well.

My existing Twitter plugin broke the site, so I pulled down a new version from GitHub.

 

David Mead

"I’m sure the arcane masters of handrolled Indieweb, who remain incapable of communicating in colloquial English, are having a good laugh at all this." - LOL. No @warrenellis, we're just as frustrated sometimes :-)

David Mead

Watching @t's presentation, 'Take Back Your Web', at @btconf
https://vimeo.com/336343886

David Mead

That's what I was concerned about Stephen. I've found myself in similar situations over the years of having a blog :-)

David Mead

Thx @mapkyca - I'll wait then :-)

David Mead

@mapkyca - Using SSH to install something on a server, before I can update @WithKnown, adds a level of complexity I'm not prepared to undertake. Any hope of one of the "unofficial" builds coming out soon so I don't have to do this?

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

Random Known and OwnYourGram issues still abound with my #indieweb setup

2 min read

I'm still having issues syndicating photo I post on Instagram, to my website. It's very weird and random.

The setup (simply) is this - A service called OwnYourGram "watches" my Instagram  account. When I post a photo there it takes it and creates a post on my website with a link back to the Instagram post.

A service called Brid.gy takes any comments/likes/etc. on that Instagram post and adds them to the post on my website. This can happen as my site has the link back to Instagram with a class of u-syndication on it.

This way I keep, not only a copy of my content but, a copy of any interactions with it.

In the Indieweb we call this PESOS.

The problem

When I first set up this Known blog it worked fine, and imported the last few entries from Instagram. After updating Known the OwnYourGram service returned errors posting to my site.

Once in a while I can log in to OwnYourGram and get a stuck photo to resend without an error.

Yesterday I posted a photo to Instagram and the whole process worked as it should! Going in to try and get the other "trapped" photos out, I got errors again.

OwnYourGram interface showing a photo went through and one erroring

Nothing had changed with my site or any of the services as far as I know.

I live in hope that an update to the core of Known may fix this. It doesn't seem to be an issue on the OwnYourGram side of things as the error is a result of something my site is doing.

But after a couple of conversations at the recent RustbeltRefresh, I may be changing things.

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.

 

David Mead

That's a great write-up @bridgetstewart. Have you hopped on the Slack/IRC yet? Good resource if you have questions.