Skip to main content

David Mead

OMG @TheDivisionGame. The complete change to how the chem launcher works has made the heal variant completely unusable in combat for me. Did anyone test this during actual gameplay?

David Mead

Be aware of false positives when using #a11y contrast ratio plugins...

2 min read

I know you everyone knows this, but just in case you don't here's a pro-tip.

When using a contrast ratio plugin with Sketch (or other design tools) make sure the text layer is set to 100% opacity. Why? Because if you don't, you may get a false positive result.

screenshot showing 14px black text on gray background passing AAA level from WCAG

Here's some 14px Rubik type using #000000 (black) on a background of #D8D8D8 (gray). We get a nice 'AAA' pass when testing against the WCAG.

But if I take the text layers opacity down to 20%, what do you think happens?

screenshot showing 14px light gray text on gray background passing AAA level from WCAG

I still get the same passing grade. I assume this is because the checker still knows this is solid black text, but has no insight to the opacity of the layer.

Visually the text is the same color as #ACACAC (light gray) which would fail the contrast check.

screenshot showing 14px light gray text on gray background failing WCAG contrast check

When running your design through a checker, just make sure someone (because of course you wouldn't) has not changed the text color by adjusting a layers opacity instad of choosing a specific color.

The two plugins I use for Sketch are:

and they both seem to bring back these passes when the layers opacity are changed. 

David Mead

Unable to make The IA Conference this year, so following remotely. Thx to @resmini for tweeting about @The_IAStudio - Looks to be a great selection of interviews.
/cc @theiaconf

David Mead

Spent a great day at on Friday, learning from @rachelandrew about CSS grid & flexbox layout. Now to pour over the forked codepen examples Rachel provided.

Thanks to everyone at @rustbeltrefresh for organizing. It was enjoyable catching up and meeting some new faces too.

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

Really enjoyable long-form conversation between Stewart Lee and @jamalimaddix
https://youtu.be/AHfnCpH4-Oo

David Mead

That's what I thought @kylesoucy & @bibinex were talking about Andrew. Geez, I'm old :-) Guess 5-6 years is the shelf-life for an internet brand now

David Mead

Though it has it flaws, I still really enjoy Neverwhere.

David Mead

Looking forward to it :-)