2018.08.24.

I’ve installed Mastodon yesterday, although I’ve said that I’ll try to skip it. It is an interesting concept and has almost everything that can make it successful for a group of people. I just don’t want to invest my time in another social service.

It seemed like a cool idea for a couple of hours, then I was back in reality: I was using Twitter and Mastodon simultaneously. That’s a warning sign. I don’t want to use multiple social networks. I like to keep things simple and social networking doesn’t deserve that much attention.

I deleted my instance and I’m back to using Twitter as my only social network. I don’t like it, but there are more people on Twitter who write about things which interests me. Maybe Twitter is the first and the last social network I’ll ever use.

2018.08.20.

I was thinking about installing an instance of Mastodon for myself, but I resisted for now. Correct me if I’m wrong, but Mastodon is decentralized, which means my own install should be able to communicate with other ones. This eliminates the hurry of getting my username on one of the popular instances—which is mastodon.social and mastodon.cc at the moment.

I’m just waiting for now. Twitter still operates and I’m trying using it from Feedbin which has a really nice Twitter integration. This way my Twitter feeds are getting mixed with other existing RSS sources. One less app to maintain. Maybe I can even subscribe this way to users on Mastodon so I can follow them, at least in read-only mode.

Regarding signing up for Mastodon: I don’t want to maintain another app for status updates and conversations just because it’s getting popular. I still have friends on Twitter, but maybe this signals something way more important. Maybe one day I’ll simply stop using social media altogether (for social media I mean Twitter, I don’t have anything else other than that).

For writing and status updates I’m keeping my blog, and I’m sure I’ll getting way less formal here which means I’ll post more status updates here or quick stuff like this.

2018.06.28.

To be honest, I still question whether using RSS and Twitter is beneficial for me in the long term. I feel the excitement that dopamine causes, when I refresh these timeline based apps—it feels similar to craving sugar, which I’m also trying to get rid off. If there is no new content, I feel a little bit of disappointment.

Also, this constant scrolling of Twitter really hurts my ability to read. I don’t read anymore, I scan things. That’s pretty fucked up and I think it’s because I don’t read longer stuff that needs me to slow down and immerse myself in the story.

I really like the redesign of Apple Books (iBooks) in iOS 12 and I want to get back reading more books. And not non-fictional stuff about how to get better at GTD or pretend you work 4 hours a week, but stories about fictional worlds. I really like sci-fi, and there is awesomeness hidden in those books.

Here’s what I’m going to do:

  • Delete Tweetbot and Reeder (at least for now).
  • Pick my favorite sites from my RSS subscriptions and add them to the Favorites screen in Safari. I’ll try to check them once a day manually as Jason Fried does.
  • Buy a couple of sci-fi books (I’m especially interested in Aliens) and read a bit every morning or evening.

2018.01.31.

There are new apps starting to pop up in the App Store which are truly nerdy, like OpenTerm and iVim. They’re still feel like a mobile demo of their desktop counterparts, but it’s nice to see something like that on iOS finally. I’m not sure where this’ll lead but I would be really grateful if I could replace my remote server setup running in Blink with something that I can use locally for web development someday.

Check out what OpenTerm can do.

Having said that, I still love using Blink, you should checkout the app, it’s open source on GitHub. Also, the new beta version is very stable, and fixes a lot of annoying UI bugs I had with the app.

After years of posting stuff to this site alone, today I’ve turned comments back on. It feels like the old days of blogging again when there was always a great discussion after almost each blogpost.

Nowadays those discussions moved over to social networks, swept away in threads which are siloed into closed websites. I want them to get back here, right below my content. So from now on, every reply or like or retweet of a tweet of mine that contains a URL to my blog should also show up here, like this.

Also, I support webmentions, and let’s not forget about those plain old WordPress replies. I hope these updates will get the discussion back where it should belong, right below after each post.

2018.01.22.

I’m giving Twitter another shot. I’ve scrolled through my timeline and unfollowed a bunch of accounts that doesn’t interests me anymore. I miss discovering small things that doesn’t reach me via RSS, like new iOS app betas, interesting links etc. But I’m also trying to be more aware when I’m using the service. Here are my rules:

  • Posts, links and statuses will be still posted to Decoding then cross posted to Twitter via Micro.blog. I don’t want to change that since I like to own my content and I can also write longer stuff here than 280 characters. Also there are people who follow this blog via RSS.
  • I’ll reply and interact with people on Twitter as I did before — I don’t care that much about where threads and comments are made anyway.
  • I’m keeping Tweetbot on my iPhone and my iPad, but I’ll avoid using the official Twitter app. I don’t care about polls and ads, the timeline usability of that app is a piece of crap anyway.

So, I hope these rules will make Twitter fun again.

2018.01.06.

The Weekly Review is the hardest to implement from GTD, but it’s the most important routine to get myself familiar with. Here’s why:

  • I have a basic anchor once a week, when I became mindful with my commitments and that gives me a relief so I can trust in my system. Nothing slips.
  • Reviewing my waiting fors then pinging people keeps that loop alive. People start to feel I demand stuff from them and they can’t escape from their responsibilities. At least from those that involve me.
  • Reviewing my stuff feels like mindfulness meditation. I pay attention what’s on my mind, then I make proactive decisions about them. This way I can relax.

Panic has announced the “suspending” of Transmit for iOS:

My optimistic take: we hope that as iOS matures, and more and more pro users begin to seriously consider the iPad as a legitimate part of their daily work routines, Transmit iOS can one day return and triumph like it does on the Mac.

Getting enough revenue from an app that you’ve developed is hard, but as a user of every Panic software on macOS and iOS, I’m angry. I’ve already made my comment regarding this change, so I’m not going to repeat it, just quote:

I know iOS is hard, but why not charge more or add subscription or something? This is not the first time you guys complaining about developing iOS apps, but I’ve never seen any new business model tried from Panic, so can’t really feel sorry yet. Paid up front and thats it. I mean there is Omni Group, they’ve transformed every Omni app to “try for free then pay a reasonable price” model last year. They also delivering reasonable upgrades constantly. On the other hand Coda for iOS still missing a lot of basic features, like Open in Place support and a simple Quick Open. And don’t get me started on the “still in the works, but it’s coming in the next 100 years” version of Coda for Mac or Panic Sync which is still buggy and way more annoying than the old iCloud Sync, which you’ve dumped…

Transmit on the other hand works fine, I use it daily, but sunsetting an app which I rely on that much is just annoying. Coda’s file management isn’t the same. For example there is no share extension which I use a lot, especially with Workflow. So instead of complaining about iOS app business models all the time, you guys should put more effort into developing iOS. I’m a customer, I’m using and loving all of Panic’s products. I would even pay for the Panic Creative Cloud monthly, but apps needs to be kept updated with new APIs and usable features know from the desktop, not treating them like “baby software” as Steve said.

2018.01.05.

I love Workflow and Working Copy together! I’ve just migrated my blog over to Jekyll, and created a workflow which grabs a piece of text like this, creates a file in my git repository with Working Copy, commits it automatically, then pushes the code to the server. All this from Today view or a Share sheet in Ulysses.