Phil Howard, of Michigan State University, casually let slip in our conversation about concentration in the food industry that a brewery in Australia had been fined for faux craft beer. I had to investigate. Its quite an interesting story.
After a frustrating afternoon pursuing deep geekiness (with some progress, and which I may write more about) I decided to cheer myself up by continuing the endless, thankless and probably pointless task of bringing old posts over here. Three of the five aroused intense memories.
Phil Howard, of Michigan State University, casually let slip in our conversation about concentration in the food industry that a brewery in Australia had been fined for faux craft beer. I had to investigate. Its quite an interesting story.
After patting myself on the back for adding an h-card to my page of latest posts, friends pointed out that I could use the <data> element rather than choosing not to display the h-card information. One good reason to do this is that screen readers ignore this information, which must be a bonus for anyone who accesses my stuff that way.
The Partial template now reads:
<div class="h-card">
<data class="u-url" value="https://jeremycherfas.net"></data>
<data class="p-name" value="Jeremy Cherfas"></data>
<data class="u-photo" value ="https://www.jeremycherfas.net/user/plugins/aboutme/assets/avatars/zoot.jpg"></data>
</div>And all the other logic remains exactly the same as before.
Another little tweak: because all my bookmarks from reading.am are now automatically brought back to my stream, I am removing them from the sidebar here.
I spent a little time fixing up the way this site presents my h-card on the summary of blog posts. In case you're wondering, an h-card is a way of presenting information about yourself or your organisation on your website that makes it easy for other websites to identify you with your work, for example in webmentions.
One of the difficulties of trying to be IndieWeb is that because there is no One True Way, only a set of useful building blocks, lovingly assembled, when something isn't working well it can be hard to know which bit is responsible for what. I had that problem recently with micro.blog waiting a long time before a post here appeared there. Then today, a post I published this morning popped up on micro.blog, and I had time to think about fixing things.
It was trivial, but I fixed it. Here's how.
