IOS on yozy//NET

Journaling on iOS With Shortcuts

Wed, 25 Mar 2026 00:00:00 +0000

I want to keep a journal, I have three requirements:

The data must be stored as plain text and plain images on disk, that I own.
The entries must be labelled with their creation timestamp, location, and ideally weather information.
I want to be able to create a journal entry from an image. The above metadata should be loaded from the image.

I started journaling with Day One¹. After it got sold I have lost faith in its future. They also use a proprietary database with limited export options which fails my condition 1.

Apple’s Journal looked interesting, but it does not satisfy my conditions 1 and 3.

I looked into self-hosted options:

Journiv² — has a terrible frontend, uses a database instead of markdown, has asinine features like “reflect now” that can not be turned off.
Obsidian — would be great but does not support 3 and requires their paid sync service on iOS.

Diar - iOS shortcuts for authoring journal entries

When I squinted at my requirements I realized that what I need is a Hugo³ blog with a login and different syntax + some goodies, and a couple of iOS shortcuts.

I always start programming by defining my data structures. First, I’ve decided on the syntax of my entries:

Since the only mandatory metadata is the timestamp, the obvious format is a markdown file with the timestamp as filename and the entry in the text.

For the other metadata I wanted something human readable and editable. I didn’t want to use a preamble like Hugo does.

My solution is to add a footer using the --- markdown syntax for a horizontal rule. Then use hashtags for tags, lines starting with /images/ for images, location prefixed by @ and a simply parsed weather. If there is a line that matches neither, it is interpreted as plain text location.

E.g.: in a file named 2006-01-02T150405.md:

This is an entry inside my journal, as you can observe it just starts as a plain text.

You can use markdown. I only really use emphasis and blockquotes.

---
/images/a-nice-illustration.jpg
#rhea #journaling
Home, France
@48.8687162,2.2219584
17°C, Cloudy

All of the footer entries are optional.

It was easy to create two shortcuts in iOS to:

Grab the current location, weather and address and write a new note with current timestamp as filename with this information. Then open the file immediately with iA Writer.
Receive an image, use it’s exif to get the time and location. If the date is today, grab the weather. Copy the image into the desired location, create the note and open it in iA Writer.

The advantage of handling images this way is that iA Writer supports displaying them in preview mode.

For the first use case the shortcut looks like this:

Rhea - Go server to render the journal in a nice way

Since I knew Hugo was almost what I wanted, I decided to learn Go and write my server.

My design goes roughly this way:

Fully server-rendered html page.
No static rendering, live-running server only.
Single user, the login credentials are passed through environment.

The program should do the following.

On startup look into the directory that contains the entries.
Iterate over the entries.
1. If the entry contains an image, generate a thumbnail for it if it hasn’t been done and store it in a cache directory.
2. If the entry contains a location, use MapBox to fetch the map, and store it.
Start watching the entries directory and update the in-memory representation if anything is added or changed.
Start a web server that serves:
1. / - At root show list of the first page of entries, show the location map if the location changed from previous entry by more than 50km. Show images as thumbnails.
2. /after/TIMESTAMP and /before/TIMESTAMP to serve a next/previous page.
3. /memories/TIMESTAMP - Show a detailed entry with full size images and a more detailed location map.
4. /images, /thumbails, /tiles-ZOOM, static - Just serve the files.
5. /login - Render this page if there is no valid session cookie set.

And that’s about it. Cook this with some nice templates and a bit of CSS and we have a journaling app.

If you would like the source code feel free to ask, I am no longer publishing my repositories publicly.

https://dayoneapp.com/ ↩︎
https://www.journiv.com/ - looked promising but the setup is too cumbersome. ↩︎
https://gohugo.io ↩︎

Creating Sf Symbols with Affinity Designer

Sat, 18 Jul 2020 19:54:10 +0200

Creating SF Symbols is supposed to be easy. Create a template using SFSymbols app. Modify the SVG and import in Xcode. It is all documented here.

SFSymbols template requires you to manually create and adjust images for all weights and sizes. This is fine if your image has lines that need to follow the weight. Many of them don’t or could auto scale.

Nevertheless I’ve made this Affinity Designer template that you can use. Open it, edit the one symbol it contains (called Template) and you are all set.

⬇ sfsymbol-template.afdesign

Unfortunately although Affinity Designer produces a perfectly valid SVG—and it will get validated by SFSymbols—Xcode does not like it.

This is what Affinity exports:

<g transform="matrix(1.22074,0,0,1.22074,498.674,600.389)">
   <g id="Ultralight-S">

This is what Xcode wants:

<g id="Ultralight-S" transform="matrix(1.22074,0,0,1.22074,498.674,600.389)">

Alright, let’s do Perl:

#!/usr/bin/perl
my $file = $ARGV[0];
open FILE, $file or die "Failed to open file: $!";
$/ = undef;
my $xml = <FILE>;
close FILE;
my @weight = (
  "Ultralight", "Thin", "Light", "Regular", "Medium",
  "Semibold", "Bold", "Heavy", "Black",
);
my @size = ("S", "M", "L");
for my $w (@weight) {
  for my $s (@size) {
    $xml =~ s/<g (transform=[^>]+?)>\s+<g (id="$w-$s")>(.*?)<\/g>/<g \2 \1> \3/s;
  }
}
print($xml, "\n");

This will finally transform the SVG into a format that Xcode will swallow.

⬇ fix-sfsymbol.perl

My take on 3D Touch

Tue, 14 Aug 2018 19:30:00 +0000

As the release of new iPhones is approaching, it is time to speculate on new features, or the removal of the old ones. There are rumors that one of the new iPhones will lack 3D Touch capability. To me, this is disturbing as I think that the biggest hindrance in 3D Touch adoption is that it is not omnipresent. Contrary to the opinion that it is broken, I believe that discoverability is a minor issue.

On a desktop interface there are no indicators to show that a particular element can be right-clicked. This is so because:

There are few actions that are only doable by right clicking, mainly thanks to of toolbars and menu bars.
Users intuitively know which elements can be right-clicked.

First point can be resolved by software: I leave it to designers to design a replacement for menus or toolbars that enable advanced functionality which can be then used with 3D Touch. The second point can be solved with users being exposed to 3D Touch all the time. With the current lineup this is a non-starter as it is available on high end phones only—not on the SE, and not on the iPad.

Now is the time for Apple to show if they are invested in 3D Touch or whether it is just a nice-to-have feature.

Eventail 2.2

Thu, 12 Apr 2018 16:00:00 +0200

After two months of coding I am pleased to announce a new version of Eventail.

This release brings some new features and a lot of polish into the settings screen.

The app now has some more personality, the preview is more prominent and looks like a preview too!

Colors

iPhone X users will be, hopefully, delighted by the new Black theme, which gives you a pure black background.

There are some good news for people who organize their life by colors too. A new Vivid color scheme puts accent on the calendar color and makes it easy to navigate through the day if you do a lot of context switching.

Weekends can get their own color too! A subtle background color indicates where the week ends.

Tweaks

The events now have a bold-colored stripe on the left, to highlight the calendar they are in.

Event invitations have distinct icons, it is easy to distinguish between invitations and own events; and also to see the RSVP status at a glance.

And more

I have squashed a number of bugs, and worked on the pestering memory issues. In most cases the widget should no longer fail to load, and the troubleshooting options will resolve the rest.

Without further ado, find Eventail on the App Store

Eventail 2.0

Sun, 28 Jan 2018 18:00:00 +0100

After a few months of development, I am proud to announce a new version of my iOS Calendar Widget App Eventail.

I am really happy how it turned out and invite you to try it, it is free.

Find Eventail on the App Store

Zoom out any page on mobile Safari

Fri, 26 Jan 2018 10:20:00 +0100

Just now I wanted to publish a new version of my app to testers. This is to be done on the iTunes connect website. I only had my phone, but according to Steve “iOS has full web experience” so this should not be a problem.

However, iTunes connect does not work exactly well on mobile. This is because the zoom level of the page is fixed on the “background” while the dialogs are in front. The result is that the button Submit is inaccessible.

After some amount of looking for a solution I have found several bookmarklets that should unlock the zoom. None of them worked. So I made my own solution.

Bookmark this page in Safari and change its URL to this:

javascript:(function(){document.getElementsByTagName("body")[0].style.zoom =0.5;})()

Then, on a page which has elements outside of the viewport, launch the bookmark from the bookmark menu. The page will be twice as small, but more of it will fit!

How I discovered how iOS calendar app chooses colors by digging into the icloud.com JavaScript code

Sat, 13 Jan 2018 19:50:00 +0100

While making an iOS calendar app, I needed to find out how Apple calculates background and text colors when displaying events in the Calendar app. I wanted to use the same algorithm for my display, in order to integrate well with the OS.

I was hoping for some displayBacgkroundColor property on EKCalendar object or something similar, but it does not seem to exist. I almost decided to start approximating their algorithm while I realized one thing—the icloud.com site has a calendar “application”. The event colors there seem to follow the same logic as those in the Calendar app. They are not strictly the same but it could provide some insight into how the color switching works.

iCloud.com being a modern web application, it runs a bunch of client side JavaScript. Since it is possible to add events, change calendar colors and so on, I assumed that the code which calculates the text and background colors for events must be somewhere in the publicly available JavaScript. There was a small possibility that they pre-computed the colors on the server but this seemed unlikely.

Homing in on the function

I decided to use Safari for this. It seems kind of appropriate and I am quite familiar with its web developer tools. I open the iCloud website, open the calendar page and look into what kind of JavaScript files are loaded.

Among others, this page loads mainly two big JavaScript files, both called javascript-packed.js. The other files are all called javascript-strings so I assume these load the localization files or something like that.

My first hypothesis was that the function is called when a color of an already present event is changed. This might happen when, for example, the calendar to which the event belongs is changed.

Luckily Safari can display minified JavaScript files in indented mode. However searching for functions for strings like “update” gave me too many results.

Looking at the HTML code of an event, I can observe that its color is inside an inline style attribute and that it changes when I change the calendar. This is good news, as the inspector lets me to put a breakpoint on that.

In the inspector I find the event element, right click on the div in the tree structure and set a breakpoint on Attribute Modified

Now I click on the event in the app, change the calendar… and voilà.

Walking up the call stack

At the very end of the call stack I can see that a property is assigned a value of #a66110. This is actually the text color for this calendar (I checked this in the inspector). My hope is that it will be calculated somewhere up the stack.

1 style: Assign #a66110 as as the color property of a CSS declaration

2 anonymous: Function that that applies the CSS style when called

3 access: This function is a sort of trampoline

4 css: This function generates the anonymous function in step 2, it does get the #a66110 as a parameter 'n'

5 updateProperty: calls the css function, and also gets the #a66110 as a parameter 'r'

When I get to the 6th level I finally hit something interesting. This is where the value #a66110 is created (inside a function called _update:

6 _update: This function seems to update the whole event, its title, state and most importantly, colors

p = t.get("textColor")

The get method seems to be doing something akin to the following (I did not really dig into this):

object.prototype.get = function(propName) {
	return call(this, this.properties[propName]);
}

I any case, the color value is derived from object t and its property textColor.

Finding the ‘Event’ object

I look into the t object’s properties and see this:

A cursory glance at the properties confirms to me that this is an ‘Event’ object. It has the usual ones such as owner, isAccepted and so on.

Intuitively this line then, in the _update function, does what we were searching for: Get the text color for an event and change the elements css representation to reflect that.

p = t.get("textColor"), this.updateProperty(n, o, ".text", p, "color")

I dig into this textColor property. I search the JavaScript file for it and look over the few results I get.

Within a piece of code which starts with Cal.Collection = CoreCal.Collection.extend({ I find this (among the other event properties):

textColor: function() {
    if (this.get("isBirthdayCalendar")) return "#4d5765";
    var e = this.get("_hexColor");
    return Cal.colorController.computeTextColor(e)
}.property("_hexColor").cacheable(),
backgroundColor: function() {
    if (this.get("isBirthdayCalendar")) return "#cfd3d9";
    var e = this.get("_hexColor");
    return Cal.colorController.computeBackgroundColor(e)
}.property("_hexColor").cacheable(),

Cal.colorController.computeTextColor(e) and Cal.colorController.computeBackgroundColor(e) and in both cases e is a color… finally I have struck gold!

Compute text and background color

The function iCloud uses to compute the text color is this:

computeTextColor: function(r) {
    r || CW.fatalError("Cannot provide a text color without a starting color"), r = r.toLowerCase();
    var i = this.get("specialColors"),
        s = SC.convertHexToHsv(r),
        o = s[0],
        u = s[1],
        a = s[2],
        f;
    if (i.isLight(o, u, a)) f = i.light.text;
    else if (i.isDark(o, u, a)) f = i.dark.text;
    else {
        var l = a - n,
            c = i.isGray(o, u, a),
            h = c ? 0 : Math.max(u, e);
        f = SC.convertHsvToHex(o, h, Math.max(l, t))
    }
    return f
},

By putting a breakpoint on the f = ... line I can deduce the constants n = 0.35, e = 0.5 and t = 0.3.

As for the background color:

computeBackgroundColor: function(e) {
    if (!e) {
        SC.error("Cannot provide a background color without a starting color");
        return
    }
    e = e.toLowerCase();
    var t = this.get("specialColors"),
        n = t.backgrounds[e];
    if (n) return n;
    var r = SC.convertHexToHsv(e),
        i = r[0],
        o = r[1],
        u = r[2];
    if (t.isLight(i, o, u)) n = t.light.background;
    else if (t.isDark(i, o, u)) n = t.dark.background;
    else {
        var a = t.isGray(i, o, u) ? 0 : s;
        n = SC.convertHsvToHex(i, a, t.bgBrightness(i, o, u))
    }
    return n
},

And the contents of the specialColors are here (comments are from my investigation of constants):

specialColors: {
    light: {
        main: "#dddddd",
        text: "#a8a8a8",
        background: "#f8f8f8"
    },
    dark: {
        main: "#1a1a1a",
        text: "#000000",
        background: "#bababa"
    },
    titles: {
        "#cc73e1": "#b14bc9",
        "#65db39": "#49bf1f",
        "#ffcc00": "#e0ac00",
        "#ff9500": "#ff7f00"
    },
    backgrounds: {
        "#a2845e": "#e0d3c1"
    },
    isLight: function(e, t, n) {
        var s = Cal.colorController;
        return n > r && t < i // r = 0.6, i = 0.1
    },
    isDark: function(e, n, r) {
        return r < t // t = 0.3
    },
    isGray: function(e, t, n) {
        return t < i // i = 0.1
    },
    bgBrightness: function(e, t, n) {
        return Math.min(n * 1.5, o)
    }
},

Then there is a bunch of color conversion functions that work in a pretty standard way.

convertHsvToHex takes a R, G, B triplet and returns a [H, S, V]
convertHexToHsv takes an array of three elements [H, S, V] and returns an array [R, G, B]
two regexes to check if a colors is in the HTML rgb(r, g, b) or #RRGGBB format
parseColor which converts either of the two formats and returns a #RRGGBB representation
expandColor which takes the #RRGGBB color and returns an array of [R, G, B]
toColorPart which takes a number in 0-255 range and transforms it to hex representation

I am not going to detail these functions here, but I have uploaded them here if you would like to look:

Original Apple Conversion Functions

Rewriting the functions into more human readable format

These functions were of course at least partly generated and minified. So I have rewritten them into a digestible format.

First, I have written a colorTools object which has the properties from the specialColors object on iCloud.

const colorTools = {
  light: {
    text: "#a8a8a8",
    background: "#f8f8f8"
  },
  dark: {
    text: "#000000",
    background: "#bababa"
  },
  backgrounds: {
    "#a2845e": "#e0d3c1"
  },
  isLight: function(h, s, v) {
    return v > 0.6 && s < 0.1
  },
  isDark: function(h, s, v) {
    return v < 0.3
  },
  isGray: function(h, s, v) {
    return s < 0.1
  },
  bgBrightness: function(h, s, v) {
    return Math.min(v * 1.5, 1)
  },
  /* color space conversion removed for brevity */

This object is then used as a helper for the two functions I was actually searching for in the beginning.

Text Color

If the color is too light or too dark then use a pre-computed text color. Otherwise cap the saturation to 0.5 (for grayish colors just set it at 0) and reduce the value by 0.35.

function computeTextColor(rgb) {
  const [h, s, v] = colorTools.convertHexToHsv(rgb);  
  if (colorTools.isLight(h, s, v)) {
    return colorTools.light.text;
  } else if (colorTools.isDark(h, s, v)) {
    return colorTools.dark.text;
  } else {
    const rs = colorTools.isGray(h, s, v) ? 0 : Math.max(s, 0.5);
    const rv = v - 0.35;
    return colorTools.convertHsvToHex(h, rs, Math.max(rv, 0.3))
  }
}

Background color

In a similar fashion, use a pre-computed colors if the background is too light or dark. Set the saturation to 0 for grayish colors.

function computeBackgroundColor(rgb) {
  if (colorTools.backgrounds[rgb]) {
    return colorTools.backgrounds[rgb];
  }
  const [h, s, v] = colorTools.convertHexToHsv(rgb);
  if (colorTools.isLight(h, s, v)) {
    return colorTools.light.background;
  } else if (colorTools.isDark(h, s, v)) {
    return colorTools.dark.background;
  } else {
    let rs = colorTools.isGray(h, s, v) ? 0 : s;
    return colorTools.convertHsvToHex(h, rs, colorTools.bgBrightness(h, s, v));
  } 
}

This was fun. Now, the colors on iCloud website are not strictly the same than in the iOS app, but that requires just a bit of tweaking with the constants.

You can download the complete JavaScript file I have extracted here:

Apple Calendar Colors

Some final words

There you have it. In the end I was actually surprised that it was pretty easy to extract these functions from the code. I expected the minified/obfuscated code to be quite hard to read. Interestingly, most function names did not get mangled. I suppose this is due to the fact that they are called through strings in some part of the framework Apple uses.

Of course, later I have converted these functions into Swift UIColor extensions so I can use them in my application.

I might publish them here sometime later, but if you are interested ask me on Twitter.

Thoughts about spam notifications in iOS

Tue, 09 Jan 2018 15:00:00 +0100

I try to keep my notifications minimal. Only those which are important should get through.

But when I receive notifications like this my blood boils:

Spam notification from Prime Video, for an episode I have already watched.

Amazon is not the sole culprit. When I received several notifications from The Fork I have confronted them on Twitter. They have promised to do something about it, and then a few days later I was spammed again… with the same notification.

Although this is forbidden by Apple App Store Review Guidelines, Design section 4.5.3, big firms do not care.

I think the main problem comes from the fact that these cost nothing and are invisible to apple. I think we should be able to report these to Apple, in the same way it is done for spam e-mail.

Where to put the report button?

Putting a button on each notification would be an overkill, it would be easy to hit it with a fat thumb.

It could go into the slide over or 3D touch menu in the notification center. But the problem is that if a notification pops up while the phone is unlocked, and you tap it by reflex, it gets a free pass. These are maddening.

My idea would be to put a section inside the Privacy tab. This view would display last few notifications you have received, with an option to report them to Apple and an option to ignore notifications with the same text from this application. At first, this would not have much impact, but over time Apple could use this data to pressure App publishers and maybe even start training Siri to act as a spam filter.

Centre a one line text in a UITextView

Fri, 25 Dec 2015 07:59:02 +0000

I had a problem. First I have set up an UITextView with these parameters:

view.backgroundColor = UIColor.blueColor()
view.text = "An example text"
view.textColor = UIColor.whiteColor()
view.textContainerInset.top = 0
view.textContainerInset.bottom = 0

I wanted to be able to centre the text in the view vertically. This should be easy, one just needs to position the top of the text according to the formula: top = (container.height - content.height) / 2. However, when you look at the actual look of the UITextView you will see this:

view.font = UIFont.boldSystemFontOfSize(100.0)

view.font = UIFont(name: "DINCondensed-Bold", size: 100.0)

Ouch, there is a semi-randomly placed offset at the top of the text. Turns out the point size of a font is not always the one you have demanded. However it is possible to get the actual height. An UIFont class provides a bunch of useful metrics:

view.font = UIFont.boldSystemFontOfSize(100.0)
view.font.capHeight // 70.5
view.font.pointSize // 100.0
view.font.ascender // 95.2
view.font.lineHeight // 119.3

view.font = UIFont(name: "DINCondensed-Bold", size: 100.0)
view.font.capHeight // 71.2
view.font.pointSize // 100.0
view.font.ascender // 71.2
view.font.lineHeight // 100.0

On a graph this would look like this:

Finally, the method you can now use is:

extension UITextView {
  func centerTextVertically() {
    guard let ascender = view.font?.ascender else {
      return
    }
    guard let capHeight = view.font?.capHeight else {
      return
    }
    view.textContainerInset.top = (view.bounds.height - ascender - (ascender - capHeight)) / CGFloat(2.0)
  }
}

Note that this will only for one liners and only if you know the height of the UITextView (i.e.: the height was given to it on creation)

iPhone : Connect to iTunes to Use Push Notifications

Wed, 23 Oct 2013 10:02:35 +0000

It seems that this message is randomly appearing for quite some people. It did for me when I updated to the iOS 7.0.3.

There are several solutions available on the internet including:

Backup to iTunes Do factory reset Restore from Backup Re-install applications from appstore

Although this will probably work for everybody it is not the best of the solutions.

For me disabling iCloud Keychain was sufficient, hopefully it will be fixed soon.

Redesigns for the worse

Sun, 14 Apr 2013 23:03:55 +0000

With the iPhone 5S release approaching feature wish lists and redesigns of iOS7 are legion on the Interwebz. Undoubtedly many people find that iOS in its current state lacks features, looks old and boring, and more generally “has to catch up with the competition”.

Usually the argument goes in the lines of “the home screen is just a list of icons” or “Apple must put widgets on the screen” or even “iPhone should centered around people, not apps”. Many proposed changes poke around the lock screen, many of them add a lot of eye candy, most of them are just wishful thinking.

It seems that lot of designers want to be part of the apple experience, want to show their skill by “improving” the user experience of an applauded product. The problem is that they base their designs on opinions of a minority (albeit very vocal) of geeks and tech enthusiasts. They criticize Apple’s design decisions without looking at the reason behind them.

Let us look at some examples and see what’s wrong with them:

Case: the iOS7 redesign video

A few days ago Federico Bianco has published a video of his ideas of how iOS 7 should look like. General reception, if we take comments on forums such as Mac Rumors, was positive. But it these comments were several very good remarks.

Lock screen

The first thing that comes in mind after seeing all of those lock screen features is security. Judging from several security holes that have surfaced in the past months it is apparent that the less features the lock screen has, the better. In its current state it can display time, notifications (that you have chosen to appear there), let you call emergency numbers and take a picture. For any other action you need to type in your passcode. Now, of course not all people use the passcode protection but most people do and it is a good practice that should not be discouraged.

After the redesign one can reply to texts, call arbitrary numbers, switch off wifi and my personal favorite: put the phone into airplane mode. What a joy when some random bloke can cut your phone off as a prank whenever you leave your phone out of sight for a minute. Apple has put a lot of effort so that without passcode people can not access even your photos and this dude lets everybody happily use your call minutes.

Widgets

The widgets Mr. Bianco proposes are a nice touch, in theory the allow you to peek at some of the information the application provides and in some cases take some rudimentary action. In practice the implementation is quite poor.

One very important thing to consider when using the double tap/click is the action that happens when the user is too slow. For example if we consider the selection on iOS then if the double tap is too slow one would move the cursor with the first tap and open the selection menu with the second. Once there one can select the word with a single additional tap.

In the case of double tap opening widgets, a wrong gesture would open the app. No big problem as you can get the information from inside the app as well as from the widget, as long as it does not take too long to open which would be a major frustration. Instead of earning half a second you would lose two.

The one thing I do not get with all these on-screen widgets is their utility. Why would I throw out place for apps to put some random information instead? What is the point of putting them on the main screen when in order to access it you need to close your current app?

Apple does already have a perfect place for widgets, the only missing thing is opening the API. You have guessed it: the notification center. The NC is the best place to put all kinds of widgets for several reasons:

It is already there
It is accessible from everywhere
People are already familiar with it
Jailbreak community has already shown that it works

If Apple would open the API then a lot of people would be happy.

Settings drawer

Another active corner = another hidden feature. There is clearly a huge demand for quicker access to settings. However I would see this more either as a widget (made by Apple, there is not much hope that apps will ever get access to phone settings) or inside the app switcher alongside music controls.

Mission control

Task switching was remade by a great ton of designers such as here in this video. Some of them are already available for the jailbreak community, like the much appraised Auxo.

The common point of all of this switchers are snapshots or live previews of the applications. In the case of Auxo they are completely useless as they are hardly twice as big as the app icon. The icon itself is shrunk. It is beyond me how somebody thinks this is a good idea. A snapshot preview consumes considerably more memory than an icon and it is much harder to quickly recognize.

As for live previews, they bring up the problem of real multitasking. Although background running apps could, in theory, provide a live preview, for most of them that would be impossible. Simply because the background process is not the same and the renderer for the application does not run and should not run because of performance issues.

The shelf

This is the best idea in the video in my opinion. The major issue I have with it is the fact that it sits on your dashboard as a folder. The news stand like shelf can only show 3 files on the iPhone at the same time, which is really not enough if you consider the quantity of the files that would end up there.

I really like the idea of system-wide file repository, as long as it is organized by type and searchable and not in a folder-like structure.

Case closed

Well, my rant is finished. It was largely based on comments and articles I read previously such as the piece on Unsolicited redesigns. Of course redesigning something is a boatload of fun, however it would be nice if people first asked themselves “why” has the original author done it one way or another before trying to improve on it.

Push irssi away messages to your iPhone

Sat, 14 Apr 2012 16:05:12 +0000

Using irssi for IRC is quite a must. Add some bitlbee sweetness and you have everything you need for your instant messaging needs. With a handy ssh application like iSSH you will get to a cyborg state when you are always connected. Small problem arises when compared to other IM applications, like IMO, that is that there are no notifications available and you will probably miss a lot of conversations. Fear not, however, for there is a solution for every problem.

Push notification application

First, you will need an application to get any push notification to your phone. There are several of them, I would recommend using the Push4. There is a free version if you want to test it first. Once you have installed it and created an account go to your account settings on your website and go to My Account -> Settings -> Profile to get your API key. You can also make the application send you an e-mail with the key.

Some scripting

You will need to make two scripts to send the notifications. (You could manage with less, of course, but I am too lazy). First one is a bash script which uses curl to send a notification to your phone. Here it is :

curl -d "user_credentials=YOUR_API_KEY" \
 -d "notification[message]=$1" \
 -d "notification[long_message]=$2" \
 -d "notification[title]=New irssi notification" \
 -d "notification[subtitle]=irssi message" \
 -d "notification[long_message_preview]=$1" \
 -d "notification[message_level]=2" \
 -d "notification[silent]=0" \
 -d "notification[action_loc\_key]=OK" \
 -d "notification[sound]=1" https://www.appnotifications.com/account/notifications.json

Do not forget to replace the YOUR_API_KEY by your real API key.

You can test the script immediately, although it might not work for a few hours just after your Push4 account creation. Basically this script sends you a notifications with first parameter as short text preview and second as a long text (which can use HTML markup). A second script is needed to parse the awaylog and send notifications using the first script.

#!/usr/bin/perl -n use HTML::Entities;
if (/(\d+:\d+) (?:([#&][^ ]+)+:)?.*?\/.*?\/(.*?).g.8.*?e(YOURNICK: )?(.*)/) {
    $time = $1;
    $channel = $2;
    $sender = $3;
    $message = $5;
    $message =~ s/\\/:/g;
    $message =~ s/"/\\"/g;
    $message =~ s/[;&]/:/g;
    print `./irssi_notify.sh "$sender : $message at $time" "Message from <b>$sender</b> (<i>$channel</i>) at <b>$time</b> : $message"\n`;
}

Now, to clarify things a bit. What this script does is that it takes some input, and if it is in some format, /(\d+:\d+) (?:([#&][^ ]+)+:)?.\*?\/.\*?\/(.\*?).g.8.\*?e(YOURNICK: )?(.*)/, to be precise, it will parse it and send it via a notification. Note that this works if you did not play with your irssi theme too much, as the awaylog basically copies the format of public and highlight messages. The (YOURNICK: )? part is optional, and it helps to remove the usual prefix of highlight messages. I can not help you much with the regex, you have to find one on your own or you can use this script which basically takes anything in awaylog and sends it as it is (it works well and everywhere).

#!/usr/bin/perl -n use HTML::Entities;
$message = encode_entities($_);
$message =~ s/\\/:/g; $message =~ s/"/\\"/g;
$message =~ s/[;&]/:/g; print `./irssi_notify.sh "$message" "$message"\n`;

Making it all work

Let us run the machine now. You will need to start another screen to run this (if somebody will help me with making a nohup version of the command I will gladly have it). Run a terminal on your shell and run

screen bash tailf ~/.irssi/away.log | perl irssi_notify.pl

Now detach the screen and you are on the roll.

Edit 2015-10-17

The Push4 service is no longer available. I am currently using a solution that uses Pushover. I’ll write up an article on how to use that shortly.