## What I Did Mar 18th - Mar 24th

• Watched Pi
• Got kicked in the face
• Played catch-up in writing up notes from crafting
• Ugraded my site to Bootstrap4 and made some nice tweaks to the layout
• Added mathematical typesetting to my site so that I can add maths to posts

$$v(s) \gets v(s) + \alpha \delta z$$

• Played Inside
• Drafted a sweater pattern

Most irritating matplotlib error:

AttributeError: Unknown property colour

## Software Rots: SCUBA Edition

I'm going back through my dive logbook after a three year diving hiatus. The software I use to track my dives has become an ungodly mess of company acquisitions and poor software support. Turns out the company that made my dive-computer was bought out by scuba-pro.

To even get my hands on the software to open my dive-log file, I had to scour old forums looking for a hidden link that would take me to the SmartTrak site. That wasn't even enough alone, I had to engage in browser witchcraft to coerce the site to not redirect me to scuba-pro's main site. The file is nowhere else, at least by my searching. Interesting that no one liked SmartTrak enough to keep a mirror of it.

Of course, finding the software didn't solve my problems. oh no. The dates were incorrect on some of my dives. An example malady of poor software support: I could turn the background of dive profiles gradient olive green, but I could not edit basic dive info---e.g., the date and location of a dive. For the first-time in my life, I'm actually experiencing the effects of deprecation in software that I depend on. It's not like I can just give up the logs for dives I've done; It's important that I keep the data I collect when I'm diving to keep track of dive habits and share with dive-shops.

After going through old dev-forums and dive-forums, I found a converter which takes shameful SmartTrack files and converts them into a modified XML for use with SubSurface. At least I can coerce the file into being read as XML, rather than proprietary nonsense. More than that, not only does sub-surface allow me to edit the date of a dive in increments greater than 7, I can edit multiple dives at the same time.

It's the future.

I can't help but feel that this is a sort of digital vagrancy. SubSurface seems great now, but what about in 3 years? 10 years? I know there's a trend of web-based dive-logs, but I don't want to have to shuffle around, converting what has no business being anything but XML or a CSV to bunch of proprietary, uninterpretable file formats.

Having been burnt by SmartTrack, I'm looking for robust export functionality in my next electronic dive-log. Lucky for me, it seems sub-surface is able to export as CSVs. This seems like a clear candidate to make a stand and own my own data.

The whole thing is just screaming to be added to the blog. Time for #indieweb scuba logs. Then if something breaks, it's my own damn fault.

Today I bit the data management bullet and started reviewing old photos. Geeze, I've forgotten how tedious it can be reviewing photos en masse: selecting them, editing them, exporting them, properly arranging them into albums..,

## Indie WYSIWYG: How I Fixed My Instagram Problem

I talk about what-you-see-is-what-you-get posting system for my #indieweb site and how it improved my post quality.

## What I did Sep1 - Sep7

### Indieweb-stuff:

• Tried to federate my indiewebsite so that I could interact with mastodon through it (unsuccessfully)

• Hacked together a websub hub which passes all of the websub.rocks tests.

• Rebuilt large chunks of my site---particularly the back-end---so that the posting interface is nicer and easier to test.

• Factored out my markdown albums, webmentioning, and hashtag extensions into separate repos which I can independently maintain.

• Hooked up webmentions again so that I can see webmentions as part of an ongoing effort to improve usability of federation.

• Hooked up in_reply_to again, so that I can send webmentions. This also lets me reply-tweet using brid.gy

• Started posting albums and articles I'd held off on posting.

• Research proposals from different disciplines to figure out how I want to structure my candidacy document.

• Bickhard's interactivism and process metaphysics

• Anthony Chemero's take on representationalism

### Other stuff

• Karaoke 🎤
• Symphony under the sky
• Knitting an aran sweater I designed
• Yoga 🧘

Test for tooting.

I really need to invest in better unit testing

## Reflections on Two Years of #Indieweb

Today marks two years of #indieweb for me. I've been reflecting on my experience joining the community and my plans for the future.

Today we had our first HWC in Edmonton. We had four people in attendance; everyone was either building their own personal sites on the university server, or helping people navigate the basics of building a site.

The plan is to have a weekly to bi-weekly meeting where we provide people with the tools to build their own sites. I'm starting with University pages, as it's something people should just have in general, but I'm going to write up some tutorials to motivate and guide people through the hurdles of getting involved in the indieweb community.

I think I'm going to make a #yeg news aggregation site for #opendataday .

Refactoring my post-parsing was a nightmare, but my code is so much cleaner now. #indieweb

Finally got around to adding geocoding to all my #indieweb posts.

I've just added an approval queue to my activitystreams inbox. Now I can receive notifications from anyone!

I've added an activitystreams inbox to my indieweb blog. Only rhiaro can send me notifications though. :)

@ChrisAldrich I'm glad you enjoyed it! Coming up with something that's easy enough to use consistently is kind of tricky. #indieweb

It worked though! I recently used it to put up two weeks of photos!

My favourite part of the indieweb: when you make a post outline the neat thing you made, breaking it in the process. 😬

## On Posting images

I talk about albums, photo management, and the sleek way I now post collections of photos.

Successfully scraping articles off of news sites. Time to work on crawling. wzxhzdk:0 .

Design For Informatics is wrapping up. Seeing the diversity of people's presentations makes me appreciate the value of a project-based course.

Procrasticoding: for when you really don't want to work on that essay

test tweeting with bridgy

yeah, my Micropub endpoint was the first thing I built so that I could just use quill instead of making my own forms. I feel like I could personalize my own one to do some leg-work to get hash-tags, summarize text, and the like.

I should probably get brid.gy integrated at some point. It looks pretty cool.

Also, I feel like I need a better minimal interface for adding posts. Right now it's a chore to add anything but text to the site. It's especially frustrating on mobile devices.

It's happened, I've turned into a robot. Or, rhiaro was nice and gave me a tele-presence so I could pretend to be in Edinburgh.

Things I did:

• Did some refactoring
• Added a mention-counter on my stream
• Broke self-webmentioning...
• Forgot I was still on-camera when I started a lab discussion on Asimov.

I hope we have more HWC when I'm back in Edinburgh for the winter...

I added a nice little counter at the corner of each post on my stream.

It gives a heads-up as to how many people have responded and whether or not it's in response to another post.

Woo, I now have linear navigation. In other words, the older posts button now actually displays older posts!

Okay, I didn't realize how messed up my microformating is.

Tomorrow I'm going to:

1. go through and make sure that my site is properly microformatted

I guess I have things to do for the EDI HWC

I'm a bit stumped right now, I'm trying to figure out what to work on next for my site.

I've got:

• A micropub endpoint for Own Your Gram and Quill
• Webmentions

I guess cleaning up my ui and working on refactoring would be the responsible thing to do...

## HWC Edinburgh

I'm going to try and make it remotely, but I'm still in Edmonton.

## First Rule of Usability? Don't Listen to Users

The article starts with a humorous note which happens to mirror fields including criminal investigation. It's even touched upon by Malcolm Gladwell in his spaghetti talk.

To design the best UX, pay attention to what users do, not what they say. Self-reported claims are unreliable, as are user speculations about future behavior. Users do not know what they want.

Don't listen to people.

If the users have not actually tried to use the designs, they'll base their comments on surface features. Such input often contrasts strongly with feedback based on real use.

Actions speak louder than words.

## UX is Not UI

I've just moved to a public repository so that I can share my project with a couple of other. The project's pretty rough around the edges, but I'm pleased with the way everything's flowing now.

especiallly given how hacked together this is

I've now got support for:

• micropubbing
• webmentions
• albums (albiet in a hacked together way)

But, I need to add testing. That, and there are a lot of little things that would make the project overall nicer. For instance, simply displaying the link if we can't find any indieweb formatting on an in-reply-to page.

Also, I'm running critically low on storage space on my server. I'll need to start working on some self-image-hosting soon. That would also enable me to throw some albums up.

That being said I'm going to take a little dev sabbatical for now.

I guess I have the mechanical aspects of webmentions in place. I just need to do some more testing and make sure that the formatting is readable.

Another test note for webmentions.

This is a test note to use as a source for sending web-mentions.

I'm spending more time thinking about UX and how to make things easier to visually parse. Design is hard.

## 9 Weeks of Indieweb

A discussion of my first nine weeks in the indieweb community.

I like how you can see the clear delineation between exams and not exams in my github commit graphs.

That, and the increased density from term-time to free time.

## Albums!

Here's an example of a collection of images, or an album. So I've started this as a means of collating a group of related items.

I wanted the extension to be as minimal as possible. As a result, I treat a collection post the same way as any other post: there's no additional information or details associated with a collection. I manage this by making albums that are simply 'responses' to other posts on the site with the in-reply-to field. This lets me give all the individual images additional information, by letting them be their own posts. It's a bit of a hack and I'm kind-of using in-reply-to fields for something other than what they were originally intended for.

It's just a mock up, really, but it does what I need it to do. I still need to figure out what the most sensible way to display all this is. :/