Content about dev

Responsive image

This seems as good a photo as any to be the first posted through the Shortcuts app on iOS. I remember taking it at a gas station on a drive home from Florida. In southern Georgia, I think. The grammar police are everywhere...thankfully!

I struggled a bit with photo uploads through the iOS Shortcuts all. The interface for creating scripts is a little janky...still. After struggling with the logic of the photos script, I realized that it was a problem with the interface that was borking things for me.

Basically, the script calls a Get Contents of URL action to send a POST request to the API. The photo is included as a file in the form data. When you add a field to the form data in Shortcuts, it defaults to a text field, but allows you to change it to "file" when tapping on it. This doesn't actually change the field to a file, though. Rather, it allows you to pick text attributes of a file to send as text. I had changed it to File, and thought, for hours, that I was in fact sending a file.

I finally reconstructed the action from scratch, adding each field one by one. When initially adding fields, a separate text v. file option appears. Setting that to File actually sets the field as a file. In the list of fields, the file fields are right-aligned while the text fields are left aligned. I wish I would have known that a couple hours ago!

Anyways, the Shortcut is now working. First photo posted through the Drafts-Shortcuts-API conduit coming next!

I'm finally getting around to updating some of the scripts I have for Daystream in the iOS Shortcuts app. Shortcuts is still somewhat limited but has surprised me with what it can accomplish.

I've now got it working essentially as a conduit between Drafts and the Daystream API for posts. This allows me to publish to Daystream directly from my favorite iOS text editor, with tags and everything. My post earlier today about last night's football games was the first to use this setup. It should enable faster, and more frequent, posting.

I plan to create similar Shortcuts for links and photos, too. For those, I'll use drafts to write the main text elements for the content (the body and tags), and then use Shortcuts to get the other content (url for links and a photo for photos).

Then on to the watch.

Putting finishing touches on the first version of a new project. Hoping to launch it soon.

Fixed an API issue this morning. Posting through iOS Shortcuts again!

updating to the latest Amazon linux 2 platform, including a ruby update. Blue/green, here we go!

We added [markdown](https://daringfireball.net/projects/markdown/) support to posts tonight.

Articles and posts are different types of content on Daystream. Articles have titles; posts don't. Articles are composed with a rich text editor, while posts have always been plain text entries.

I've always liked this distinction, and felt it was useful because it seemed to help me write more (omitting the need for a title was surprisingly freeing). But, I've always felt like something was missing with posts.

*Emphasis* and [links](https://en.wikipedia.org/wiki/Hyperlink) are important aspects of web writing, whether the piece has a title or not. Markdown allows us to use these elements in posts without abandoning their plain text simplicity.

So take a review of the [markdown style guide](https://daringfireball.net/projects/markdown/syntax) and start marking down your posts!

I added audio capabilities to Daystream today. You can now upload mp3's to your journals. This is something I've wanted to do for awhile, and I have some bigger plans for the feature in the future. Should be fun.

So where's the first recording? I used our Post to the Past feature to add a recording of water draining into a sewer to my journal for last Saturday.

I've been experimenting with displaying images for links on Daystream. I though they would provide meaningful information alongside the title and any lede that the user adds. It was fairly easy to code, so I didn't think much of it.

After seeing them for a few days, though, I have to say I'm not a fan. I don't think they add much as far as context goes, especially when you consider we've got no control over the actual image associated with the link. They increase load time, too.

And, perhaps most importantly, the lessen the visual impact of images added by the user. Visually, these images should be the most prominent content on any given journal, not uncontrolled images associated with links shared by the user.

So, the experiment is over - images will no longer be displayed for links on Daystream.

Daystream has been a pet project for more than ten years. It's time to take it beyond that. It's time to change social media by implementing all the things behind the Daystream concept. It's time.

Responsive image

I found an old iPod of Jonathan's as I was going through our electronics graveyard. It still had copies of the Chip Trading and Daystream apps he created! Non-functional, but boy did this bring back some wonderful memories. And look how small that iPod is!

Testing post entry from the web again.

Working on the API tonight...looking forward to that!

Making some good progress on Daystream. Looking to write a manifesto of sorts, soon.

responsive image Tutorial to install, configure, and secure a WordPress blog on your EC2 instance.

Starting a new side project. Details soon.