Keeping a Record

Reiterate works by having you identify issues with your own play and recording clips to help you focus on each one. As a by-product of this process, you have a record of every skill you feel is important to focus on.

When you’re away from the game for an extended period, it can be easy to forget what you were working on in the first place. Reiterate can act as a bookmark for you, keeping your place, so you can pick up your routine where you left off.

If you don’t follow a regular routine, it’s easy to get lost. Recording your skills and motivations should be a part of that routine. A training session should be more than “I played the game for an hour every day.” If that’s all that you do, and you take a break, then when you pick the game up again you’ll find yourself making the same mistakes all over again, and worse, you won’t even know which mistakes you’re repeating.

Review

My own personal Reiterate session currently has 30 clips in it. That’s a lot, but keep in mind that I also use the Focus Limit and Repeat Limit settings. Those settings ensure that in any one particular session, I’m only focusing on a small subset of my entire session clip group.

I took a break from League recently, and when I came back it was very nice to be able to scroll through the titles of my session clips. Just reading the titles, not even playing the clips, was enough to make me think, ah, yes, that’s what I was working on. It’s like a bookmark into your own personal development. Without those clips, I probably would have stumbled through my first few games, remembering the skills I needed to work on only after failing them in an actual game. And even then, I probably wouldn’t have been able to remember all thirty of the skills that I’m currently developing. Something would have inevitably been lost.

Learned Skills

One technique I like to tell people about is the Learned Skills session. If you make a session called Learned Skills then you can move clips there once you feel you don’t need them any more. It’s satisfying to hear a clip during a session and you think, I don’t need to hear that any more. You’ve successfully internalized the skill. You can simply mute the clip, and it won’t play in that session any more. That’s fine. But then you can also add it to the Learned Skills session. That session will act as a repository for all the skills that Reiterate has helped you improve on. As that session list grows, it becomes concrete evidence of how much you’ve grown.

It can also serve as a useful review tool. Every so often, you can scroll through the titles just to remind yourself of how far you’ve come. And you can also play that session in an actual game. You’ll probably not need to hear most of what is played, but perhaps there’s some skill that’s atrophied and you’ll find you need to work on it some more. This way, you can keep all your skills in top condition.

At the start of 2022 the Guardian ran an article titled New Year, Same Old You!. This is one of many self-improvements essays that all tend to come out around New Year’s, but I felt this one had some nice points, and in particular I felt it tied in with Reiterate in some important ways. I don’t think it’s become at all irrelevant in the two years its spent sitting in my ideas pile.

New Year’s is a time when people traditionally look to improve themselves. Much of the advice that is given in regards to lists of resolutions is also applicable to people trying to improve at esports. Some people want to quit smoking; other people want to quit throwing away winning games. New Year’s resolutions can fail for the same reasons people improve to climb, and the main reason is that the person who is trying to improve is the same person who is devising the plan to improve. Let’s face it: if you’re hardstuck silver, why would you follow the advice of someone who is hardstuck silver to get out?

No one awakens in the morning, looks in the mirror and says, ‘I think I will repeat my mistakes today… but frequently, this replication of history is precisely what we do.

This is a way to get trapped in a perpetuating cycle of self-loathing. If you start by imagining yourself at your new rank, you inevitably feel bad about your current rank. This makes it even harder to change your playstyle, and when you inevitably fail to climb, you feel even worse about yourself.

Acceptance

The way out of this spiral is to embrace who you are at this moment. Accept your current rank, accept all the mistakes and misplays you make, accept your flaws. There’s nothing bad about making mistakes, everyone makes mistakes. Making a poor play does not make you a bad person.

Many people dream about achieving their goals. How good it will feel when they finally have that Diamond border. But here’s an experiment. Instead of imagining how you’ll feel when you achieve the rank you desire, try something else. Imagine a future where you never climb any higher than where you are right now. You will be hardstuck at this rank for the rest of your life. Really try to imagine that scenario. How does it make you feel? Does it feel awful? Make you depressed? Stick with that. Keep exploring that feeling, because that’s what’s holding you back.

Paradoxically, accepting that you’re just not a confident [player] and you’re always going to [lose games] will begin to make you feel more comfortable and less anxious [about your play].

Only by accepting who you are can you find the foundation upon which you can build your new skills.

Reiterate

As I’ve worked with Reiterate to improve my own play, I’ve accumulated a long list of flaws. Reiterate forces you to examine your own play and put into words (and voice) what your problems are. Every clip that I’ve recorded into Reiterate is an admission of a flaw. Some of those flaws I’ve managed to eradicate. There are clips that will play and I think, I don’t need that anymore, and I remove it from my active session.

There are also clips that have been there for months. And that’s okay too. Maybe there are issues with my gameplay that I will never be able to fix. Perhaps my efforts would be better spent focusing on other issues, then. I’ll have to accept that there are some skills that are beyond my reach.

My current session has thirty clips. Scrolling through it, it’s laughable to think that I’ll ever run out of clips to record or work on. Pruning down the list, taking a clip and saying “I think I’ll retire this one,” is not a failure. It’s a way of being more productive, of focusing my efforts onto areas where I will see the most improvement.

Read the original article

I only managed to write twelve posts this year (not counting this one). That’s less than half of 2022’s total of 30. Partly that’s due to all the technical work I’ve been doing. I haven’t abandoned this blog by any means. There’s two ways I can “work on my blog”. The first is by writing new content, and the second is technical work. I did a lot of technical work last year, but that means I didn’t have time to create a lot of new content

Technical Improvements

The biggest technical improvement is the conversion to Tailwind CSS. That’s something I’ve wanted to do for a long time and I’m glad I got it done. The old blog theme was basically one of the default themes that came with Jekyll and it didn’t match the rest of the site. This new theme is… well, it’s not much of a theme, but it shouldn’t be too hard to add some nice styling bit by bit. I look at it as a fresh starting place.

The Tailwind system I integrated is nice and clean. I was able to get rid of several css files from the old theme, so the site should be more efficient and load faster.

Another big change was moving to Mastodon. I got rid of the Twitter links and set up a system to automatically post to Mastodon whenever I posted here on the blog. I actually had someone contact me with a couple suggestions, and I think they might be using my plugin on their own blog. It always feels nice to have someone find your work to be useful.

This year I also upgraded to Debian Bookworm. That gave me a chance to test out my Ansible migration system.

Gaming and Philosophy Posts

Keeping with the trend from previous years, about half my posts were on my gaming and self-improvement philosophies. I wrote about how you need to rest your communions skills as much as your wrists. Incremental improvement is an important focus, and sometimes trying to be less bad can be a good approach. Finally, I looked at how important hearing a coach’s voice can be for professional athletes, something I feel justifies Reiterate’s approach for esports.

Elon Musk

One of my most populat posts this year was the one where I explained why I’m leaving Twitter. I’m not sure how I feel about that. It didn’t exactly go viral, but it did get boosted and favorited on Mastodon, something that hasn’t happened with any of my other posts. For someone like myself who has basically no audience, it was startling to see complete strangers clicking that boost button.

That post is my rant-iest post yet, and I’m not exactly proud of that. It’s easy to get a reaction by being incindiary. That’s not something I want to be known for, though. I’m not going to take that post’s popularity as a sign that I should be more extreme in my views. Quite the opposite. This is a personal blog; it’s a place for me to expand on my own thoughts, and if other people want to follow along that’s fine. I can rant sometimes, but in the end I feel this palce is better off with more measured discourse.

Looking Forward

Reiterate is in a pretty good place right now. This year I upgraded it to use all the modern Swift concurrency affordances. It’s still written in AppKit, not SwiftUI, so I suppose that’s the last major upgrade it will need to be a fully “modern” app. Feature-wise, I’d say it’s complete. I use it every day in my own gameplay, and I think it’s useful.

I see more and more pieces with people asking Is League Dying?, usually followed by lots of statistics to make the case that it isn’t. But it all feels kind of forced. Reiterate is not tied to League. I use it for League, mostly, but there’s nothing in the app that says it can’t be used for any other game. So if League does retire, Reiterate can continue on in some other form. I’m not worried about that.

I spent quite a bit of time integrating this site with Twitter. I tried working with Bridgy to handle backlinks, and set up Jekyll plugins to automate the POSSE process so it would post links to my Twitter account. But I’ve taken all that down now. The reason, of course, is Elon Musk.

The Enshittification of Twitter

There have been so many articles written on Twitter’s decline. I don’t feel I need to recap them all here. But aside from all the hate speech, anti-semitic remarks, and garbage posts, the sheer fact that Elon is now running things is enough to make me want to quit.

I’m not under any delusion that my quitting Twitter will somehow be the spark that turns things around. Elon Musk is not going to browse this site and have some sort of revelation that he either needs to vacate the site, or turn things over to someone who knows how to run it. And my leaving Twitter is not going to engender some sort of mass exodus (not that that isn’t happening already).

(As an aside, I find it amusing how every news article that mentions Twitter is still calling it “X, formerly known as Twitter”. This has to be the worst corporate renaming ever. How long is it going to be referred to as the social media site “formerly known as Twitter”? Every day that continues get a chuckle out of me. I’m just going to call it Twitter.)

Mastodon

I’ve linked this account to Mastodon. I made a Jekyll plugin that handles posting for me, so everything is as automated as it was before with Twitter. It’s even better, in fact, since I’m calling the Mastodon APIs directly and I don’t have to go through a third party site like Bridgy.

It looks like Bridgy no longer works with Twitter anyway.

Dump Elon

As I said, I’m not leaving Twitter to start some kind of movement. I’m leaving Twitter for myself. I don’t want to be associated with anything to do with Elon Musk, and now that includes Twitter.

I’ll never by a Tesla, either. I don’t think you can separate Telsa from Elon Musk. If you own a Tesla, you’re basically saying, “I agree with everything Elon Musk says, and I support him.”

Elon Musk is a bigot, a racist, a homophobe, and an anti-Semite.

I don’t think he’s that smart, either. Some people believe he’s some sort of suer-genius, but that doesn’t square with all the stories showing him to be a grade-A moron.

He’s not even a good businessman. He’s made some of the worst business decisions in the history of capitalism.

Elon Musk seems to be good at one thing: he works hard, and he has the ability to drive the people who work under him to commit to insane work schedules. That’s it. He’s basically a slave driver.

Narcissist

Have you heard of Impostor Syndrome? That’s when people think they’re not as good as they actually are, and they don’t deserve the praise they get for the work they do. Musk is basically the opposite of that. He’s a narcissist. He believes he’s the center of everything, that he can do and understand everything, and he deserves recognition for everything he does.

This chart comes from German General Kurt Von Hammerstein-Equord.

I divide my officers into four classes as follows: the clever, the industrious, the lazy, and the stupid. Each officer always possesses two of these qualities. Those who are clever and industrious I appoint to the General Staff. Use can, under certain circumstances, be made of those who are stupid and lazy. The man who is clever and lazy qualifies for the highest leadership posts. He has the requisite nerves and the mental clarity for difficult decisions. But whoever is stupid and industrious must be got rid of, for he is too dangerous. (Von Hammerstein, 1933)

You can use the brilliant but lazy man as a strategist, a brilliant but energetic man as a Chief of Staff, but God help you with a dumb but energetic man. (Douglas MacArthur)

Musk clearly belongs to the “Stupid but Industrious” category. The fact that he has a lot of money means he’s a danger to society. Our best hope is that he someday attempts something so stupid that he kills himself. He’s come close already, but he didn’t get called out (unlike how he was forced to go through on his purchase with Twitter).

Anyway, that’s enough armchair psychology on Elon Musk. I don’t think I’ve said anything that hasn’t already been said about him, but it feels good to get off my chest.

I’ve been wanting to update the blog for some time, and it’s finally complete. There’s a few little details that need to be fixed, but it looks good enough to publish at this point.

The old blog was styled with an old Jekyll theme which was serviceable enough but looked dated when compared to the main site, which I had redone with Tailwind CSS. Now the blog matches with some clean Tailwind of its own. Perhaps it’s a little too stark at this point. Brutalilst, you might say. But I can spice it up at my leisure.

How to integrate Tailwind CSS and Jekyll

The blog is a complete system on its own, which is why it kept its own styling when I updated the main site. The blog is a static website built by Jekyll. I liked Tailwind when I used it to update the main site, so I wanted to use it again on the blog. When I researched how to integrate Tailwind and Jekyll, most of the solutions pointed to PostCSS. That’s a Node wrapper around a process to automate buiding CSS. You need the jekyll-postcss gem to integrate PostCSS into Jekyll, and for that you need to install npm.

npm is the Node Package Manger. It’s how most JavaSceipt-written pacakges are managed, but it’s had quite a few security issues recently. And it’s huge and unwieldly. And I thought, why do I want to infect my whole blog system, which is designed to be as simple as possible, with npm? So I wanted to do better.

I felt it should be possible to run Tailwind without adding a dependency to npm. As it turns out, you can do that.

Tailwind Standalone

First, we need to get rid of npm in Tailwind. Tailwind is JavaScript, and normally installed through npm, but they have a special standalone package you can use without having to go through npm. It’s pretty easy to install. It’s just one file you can download anywhere.

Jekyll Integration

Next, I needed a plugin that would call Tailwind to render my CSS every time I rebuilt the site. That wasn’t too hard either. I’ve posted the code here on my GitHub. To use it, put that code in your _plugins directory.

Next, create tailwind.config.js in your blog root directory that should look something like this:

/** @type {import('tailwindcss').Config} */
module.exports = {
  content: ["./*.{html,js}",
    "./_includes/**/*.{html,js}",
    "./_layouts/**/*.{html,js}",
    "./_posts/**/*.md",
    "./_drafts/*.md",
    "./public/js/*.js",
    "./_plugins/*.rb"
  ],
  theme: {
    extend: {},
  },
  plugins: [
    require('@tailwindcss/forms'),
    require('@tailwindcss/typography'),
    ],
}

Depending on your blog layout, you might want to adjust your content specification. These are all the directories where Tailwind will look for you using its utility classes to build the css file.

Next, I created a jekyll plugin to call Tailwind whenever it generates the blog. It’s pretty simple, one short file which I have here as a gist: Jekyll Tailind Plugin. Place that file in your _plugins directory.

To configure it, all you need to do is tell it where you downloaded the Tailwind binary that you downloaded. In your _config, add a section like so:

tailwind:
  script: /usr/local/bin/tailwindcss

Of course you should substitute in the actual path of where your tailwindcss binary is.

That should do it! You can now use Tailwind to style your Jekyll blog, and you don’t need npm, yarn, or PostCSS. Of course, now you have the real hard work ahead of you: having to strip out all of your old css styling and replacing it with Tailwind utility classes. Have fun!

Reiterate 1.6.0 has the following updates:

• fixed The Tag Board did not resize properly if you had more than one line of tags.
• new Changing tags mid-session immediately updates the play list. (see below)
• improved Cleaned up some alignment issues in the Settings Tab
• improved Changes to the speech recognition to make Acknowledgement better
• new Acknowledgement transcripts. Reiterate will display your speech as you acknowledge clips.
• fixed Muting/unmuting clips background display
• fixed Keyboard autohides when tapping other controls in Clip Details

Mid-session tag updates

The new tag feature enables a way to use Reiterate I find particularly useful. Imagine you have a problem remembering to do one particular thing, but it doesn’t come up in every game. For example, say you have trouble remembering to use item actives. You don’t buy an item with an active ability in every game, so you don’t want Reiterate to bug you about it all the time, but when you do buy an item with an active it would be nice if Reiterate focused on that one issue.

Here is how you can use tags to accomplish this. Record a clip, name it “Item actives”, with an audio reminder that says something like, “Remember to use your item active!” Next, create a new tag, call it “item”, and assign that tag to your new clip. That clip is the only clip with the “item” tag.

In your Session view, you’ll see the item tag in the Tag Board. Tap it twice to disable it (so it displays a red slash through the tag). That way, by default your “Item actives” clip will never play.

Now, while a session is playing, let’s imagine you buy an item with an active ability and you want to be reminded about that. Tap the item tag in the Play tab Tag Board to enable it (so it’s colored). This will change your play list so that only clips with that tag will play, and since that clip is the only one with that tag, Reiterate will play that one clip over and over. Tap the tag again to resume your normal play list.

New Acknowledgement UI

The interface for Acknowledgement has been reworked. Now, when Reiterate is waiting for you to acknowledge a clip, you’ll see a pulsing blue bar below the clip title. As you speak words, they will appear in the bar. This way you’ll know that Reiterate is listening to you (or why it might not be acknowledging a clip).

Also, under Settings, there is a new Vocabulary section. Here you can add a list of words like “gank” that Reiterate might not recognize because they’re too jargony.

Download Reiterate on the App Store today!

Overall, Debian 12 is a fantastic release, the latest in a string of excellent updates. I’ve been running this server on Debian since Day One, and I’ve never regretted it.

As I’ve written before, I’m now using Ansible to configure and document my server setup. One of the reasons for that was so that I could upgrade my server cleanly. Typically, if you have a desktop running Debian, you’ll upgrade it using apt-get dist-upgrade which does the upgrade “in place,” that is, you keep everything else in your system that isn’t part of the OS. That’s convenient and it’s the option most people choose, but I like starting from scratch, for three reasons.

1. It avoids the accumulation of cruft. When you keep upgrading in place over and over, it’s like painting your house a different color every year, just slapping a new coat on top. It works for a while but eventually you need to strip everything down to the bare wood and start fresh.

2. It keeps me in touch with every part of my server. If I simply upgraded in place every could years, I’d forget some of the details and wind up in a situation where I had certain files in the system and I didn’t know why. By rebuilding from scratch I force myself to examine each and every part of the system.

3. It documents my system setup. My Ansible playbook serves as a document of everything my system needs to run. I know it is a complete and sufficient recipe because I can use it to rebuild the server from scratch.

However, upgrading is not as simple as replacing “debian11” with “debian12” in my playbook. There’s always a few details that need to be fixed up, some things that don’t quite work the same way and need to be adjusted. Here’s a report of everything I needed to clean up after my Debian 12 upgrade.

Python interpreters are now externally-managed

In Debian 12, you can no longer use pip to install packages system-wide. You have to create a virtual environment, and install the packages there. This makes sense from a system management viewpoint, since you can easily break your system by installing packages into the global library space.

I was using pip to install isso, which manages my blog comments. I already had an isso user account, which I was using to keep things nice and neat, putting the comments database and config files in that user directory. I didn’t really need to do that but I felt it was “best practice.” Now that I needed to install the python modules outside of the system directories, having the account already set up seemed perspicacious.

First, I needed to get the proper packages installed to do the virtual environment installed. On the old Debian 11 install I was using python-dev but that failed with:

Package python-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  python-dev-is-python3

That’s a very odd name for a package. I guess starting with Debian 12, python2 is officially deprecated and everything is forced to be python3. This package just makes a link so that any script referring to /usr/bin/python gets python3.

The next error was

The virtual environment was not created successfully because ensurepip is not
available.  On Debian/Ubuntu systems, you need to install the python3-venv
package using the following command.

    apt install python3.11-venv

Which is the new package I needed to actually do the virtual environment install.

Next, I had issues with Ansible. Ansible is finicky about privilege escalation. I wanted to install this in my isso directory as the isso user, but Ansible doesn’t like becoming users other than root. I tried every combination of become_user, become, ansible_become_user, but I was unable to get Ansible to do this directly. I ended up doing the venv install as root, and then chown-ing everything over to isso. It’s kind of hacky but it works and I was too frustrated to try and find a cleaner solution.

Ruby

The main website is Rails-based, which requires Ruby of course. I happened to be on ruby version 3.1.3, which is no longer supported anywhere, so I decided to upgrade to the current stable version 3.2.2. I use rvm to manage my ruby installs, which… it works, but it seems like there hasn’t been a lot of development work on it lately? I checked around and it doesn’t seem like there’s any good, well-supported ruby version managers out there right now.

Rvm doesn’t have any binaries pre-compiled (they’re behind on this, there’s some support for Debian 11. I offered to help compile some binaries but never got a response back). I had to compile ruby from source, and that meant I had to install some additional packages: libyaml, libreadline, and libffi. After all that, I successfully got the latest ruby installed.

Puma

Puma is the application server that sits between nginx and my Rails app. Trying to start up puma gave me an error:

libssl.so.1.1: cannot open shared object file: No such file or directory - /home/deploy/production/vendor/bundle/ruby/3.2.0/gems/puma-6.0.2/lib/puma/puma_http11.so

It took me a while to figure out, puma-6.0 has a dependency on libssl-1.1, which is no longer in Debian 12. The current libssl is 3.0, so I needed up upgrade to puma-6.3 which has the proper libssl dependency.

Goaccess

Goaccess is a small utility I use to parse my web logs and give me statistics. I was calling it with an ignore-referer flag, but the version of goaccess in bookworm changed that to ignore-referrer. I had to update my wrapper script which was erroring becuase of that.

That original misspelling should be a warning to every standard developer that details matter.

Fail2ban

I use [fail2ban] to block script kiddies. The new version in Debian 12 was now logging warnings:

WARNING 'allowipv6' not defined in 'Definition'. Using default one: 'auto'

I fixed that by adding a section in /etc/fail2ban/fail2ban.d/local/conf

[DEFAULT]
allowipv6 = auto

PAM sshd user_readenv

There’s a bug in the sshd PAM config that was spamming warnings in my log files that look like:

pam_env(sshd:session): deprecated reading of user environment enabled

Reading through the bug report, it seems harmless to fix it by removing the user_readenv flag in /etc/pam.d/sshd so I did that.

sudo flag file

Sudo is now adding a file .sudo_as_admin_successful in my home dir. Dotfile litter is one of my pet peeves, so I disabled this by adding a block into my sudoers.d config file:

# Disable ~/.sudo_as_admin_successful file
Defaults !admin_flag

And that was everything! Well, everything Debian-related. The server has been up and running on Debian 12 for several days now and I’m not seeing any new errors or warnings. Thanks again to everyone on the Debian team for putting out quality releases!

In my previous articles, I delved into how some of the most common debates in the League of Legends community can be reframed through the lens of communion skills:

• Should you mute chat or not? The question of whether to mute chat or not can be seen as a test of your ability to manage your teammates’ morale, a highly advanced communion skill that requires exceptional effort.
• When should you surrender? Instead of trying to evaluate the game state and looking at this as a winnability question, look at it in terms of the communion skills you need to get your team’s mentality to a place where they can play optimally.

Playing effective League of Legends involves executing your communion skills to the best of your ability. You can’t do this if you’ve exhaused your resilience reserves. Every time a teammates question mark-pings you, or rages in all chat, or makes a poor play off tilt, it drains your emotional energy and depletes your mental resources. Once your reserves are completely exhausted, your mental state suffers a catastrophic blow. This is what is commonly referred to as “mental boom”.

Resilience levels vary from person to person. I believe that fortitude can be developed and expanded through practice, allowing you to shoulder greater emotional burdens. However, there’s no shame in acknowledging when your emotional reserves are running low. In fact, recognizing this is a valuable skill in itself. When you sense that you can no longer tolerate the disruptive behavior of your teammates, it’s time to take a break. Allow yourself to recharge and refresh, so that you can return to the game stronger and more focused in the next session.

In the world of esports, self-improvement advice is everywhere. Gamers seeking to level up are bombarded with Reddit boards, coaches, videos, paid communities, and training camps. It’s a never-ending cascade of tips and suggestions that can easily drown out the truly useful information.

Here’s a different approach: instead of focusing on what skills and techniques to acquire, try zeroing in on your weaknesses.

Identifying what you’re doing wrong can be simpler than discovering what you need to do right. The “right” way is often unknown territory, requiring input from coaches and fellow players, followed by a daunting task of sifting through the noise.

In contrast, pinpointing your errors is more straightforward. By reviewing your own games and analyzing each time you died, you can ask yourself, “Why did that happen?”. More often than not, your mistakes will be glaringly apparent. Whether you overextended, miscounted enemy players, or missed a skill shot, closely examining your own games will reveal a treasure trove of shortcomings to address.

The next step? Stop making those mistakes.

Eliminating bad habits is akin to subtracting negatives. The fewer errors you make, the more your overall gameplay will improve. As you consistently eradicate mistakes, your skills will naturally progress.

To streamline this process, try using Reiterate. Transform each blunder into an audio clip and, if desired, turn each negative into a positive. For example, if you are dying because you don’t track the enemy numbers in a team fight, you can make a clip like, “I will always count the number of enemies before committing to a team fight.”

Once you find you are no longer exhibiting the negative behavior, you can retire the clip. And that’s how you improve by being less bad.

It’s been a while since the last official release (1.4.3). I’ve been hard at work adding new features and fixing bugs. Here’s a quick summary of all the new enhancements you’ll see.

Bug Fixes

• Crashes
  • fixed If a phone call came in while you were playing a session, it could crash.
  • fixed Trying to create a new clip while a sesion way playing would crash.
  • improved Updated all concurrency code to the modern Swift concurrency system.
  • fixed You could delete the “add new tag” row.
• Acknowledgement System
  • improved The background threading system is more robust.
  • improved Adjusted (increased) the time to acknowledge a clip.
  • improved Speech recognition is more robust.
  • fixed If you miss several clips in a row, it won’t spam buzzers at you.
  • improved Contractions are properly recognized.
  • improved The little check and x-marks are now consistent with the standard symbols font.
  • improved The animation that plays while a clip is awaiting acknowledgement is spiffier.
• Tags
  • improved The Tagboard on the Play tab will only show tags that are relevant to your current session.
  • fixed If you have no tags, the tag board will be hidden on the Play tab.
  • fixed Newly added tags would not be added to a newly added clip.
  • fixed Newly added tags appear properly on the Tag Board.
  • improved Lines of tags are center-aligned.
  • fixed You can no longer create empty (nameless) tags.
• Clip Details
  • improved Reworked how clip details are edited. Instead of in-place in the Clips view, there is a whole separate page that pops up.
  • new There’s a new icon at the left of every clip that graphically shows what kind of clip it is, and when it plays.
  • new Tap the new clip timing icon to select it (with a check mark). When multiple clips are selected you can mute, delete, and tag them in a batch.
  • improved You can cancel tag edits.
  • new Purchased content is labelled as such.
  • new All clip edits can be cancelled.
  • fixed Clips with a colon in the title couldn’t record audio.
  • improved The VU meter has a nicer animation when recording.
  • fixed Cancelling out of Clip Details while recording would crash on next attempt to record.
• Session Sidebar menu
  • new Tap the hamburger button to bring up the sidebar. From the sidebar you can switch your current session, edit and delete sessions, bring up the user guide, and more!
• Play tab
  • improved The StartSession button is now consistent with standard iOS UI.
  • improved Landscape more UI adjustments.
  • improved Starting a session no longer has a little lag at the very start.
• Settings
  • fixed Tapping the Clip Interval in Settings, without changing anything, would leave it in an inconsistent state.
  • new You can set an alert cue to fire after missing (acknowledging) a clip. This is a great way to use alert cues, because they only play when you’re starting to zone out.

Download the latest version of Reiterate on the App Store