Posting with Wordpress feels so clunky. So many buttons and check boxes when all I want is to just click a button and type. I'm really looking forward to getting my blog over to my own system so I can move from a generic cms/blogging system to something streamlined specifically for blogging, and most importantly, how I want to blog.

I'm already full of ideas for fun pages I'll able to make once my data is in a proper relational format and in a database that supports geographic queries. But first I need to finish porting my data. So close I can taste it.

The magic of web 2.0 were the open apis. Developers could use these apis to mashup services how they wanted. Sometimes these developer's tools and mashups became so popular that they would come to define the entire service of which they were building atop. Both hashtags and the term "tweet" originated outside of Twitter, Inc.

But when these services grew they morphed into platforms. Their apis were closed off and the developers that helped these companies find their success either kicked off or severely limited in what they could do. This became a pattern, not just with Twitter, but many services that found success in thanks part to their open api followed the same playbook.

Existing players making unpopular changes to their policies is usually a boon for the upstart. Each time this happens a vocal group of users becomes dissatisfied with the platform who then attempt to migrate to an alternative. However each migration causes some kind of loss. Data doesn't transfer or communities fracture because not everybody moves. Not to mention the energy that could have been spent doing something else.

Contrast this with something like email. You can email anyone you'd like, even if they don't use the same provider as you. If your mail provider changes a policy you don't like, you're free to change providers without losing your identity on the internet. People can still contact you the way they always had and you can still contact them. Your data can move from platform-to-platform seamlessly. There's nothing re-organizing or hiding emails from your inbox unless you setup the rules (or use gmail).

The difference in experience between twitter and email is night and day. One keeps you locked in and subject to their whims, while the other gives you the choice to use it however you see fit. The difference is that twitter is a platform and email is a protocol. Pick protocols.

As part of of the "team UX" at work we're doing a bookclub to make sure we all have good foundations in UX before making it a company offering. We're starting with two books: The Design of Everyday Things by Don Norman, and UXデザインの教科書 (The UX Design Textbook) by Masaya Andou.

While I work reading and writing Japanese all day (when I'm not slinging code), I haven't read a book in Japanese in ages. This is mostly because what I'm interested in ( technology, the web etc...) is usually written about in English well before Japanese. And since I can read English natively, it's natural for me to pick those books.

Starting to read UXデザインの教科書 yesterday and the first thing that hit me is how much my Japanese has improved in the last 4 years. I used to struggle reading texts written for native-speakers as I had large gaps in my kanji recognition abilities. Gaps still exist. But now they're small enough that reading a single page doesn't take 20 minutes as I look up every 5th word. Only taken me...20 years(!) to come the far.

Inspired by Seth's Chasing the cool kids, I've made a short list of things that are cooler than Clubhouse.

• Not caring what the "cool" kids are doing and doing your own thing.


• Building and learning about the systems that make the world go around.


• Not uploading your entire contact list to some random company so you can eavesdrop on the "cool" kids.


• Fighting for an open web so that you and future generations can access the world without gatekeepers.


• Owning your content.

The urgent advice usually ends with “blogs are dead"

If you always have to mention that "blogs are dead", perhaps they aren't actually dead. They never were dead. They're just not "cool" anymore. The people who made blogging cool and fun? They're mostly still blogging.

Publish. Consistently. With patience. Own your assets. Don’t let a middleman be your landlord. Yell at Google for blocking your emails and hope it’ll work eventually. Continually push for RSS and an open web. With patience.

Yes.

You should start a blog today by Juhis struck a cord with me and I thought I'd pile on. You should start a blog today.

Like many I blogged a lot in the early 2000's. Those early blogs captured my frame of mind for that period, but they're long gone. Also like many, I stopped blogging sometime after Twitter and Facebook became popular.

Over the years I tried to start back up again. "I should blog more", I'd tell myself. I'd always try to focus on writing "evergreen" content or writing "professional" content and after a short burst, stop.

Discovering the IndieWeb helped remind me that I'm writing for me on my blog. It doesn't have to always be professional all the time. This past year or two regularly blogging again has helped me remember just how magical the internet is. That I can write something in Japan and people find it and respond to it from all over the world – all using open-standards – brings a smile to my face.

Why should you start a blog today?

• Develop better ideas. Many people develop their ideas by writing. They sit down with idea A and as the write about it, they gain some further insight and get idea B, which leads to idea C and so on. None of this would have been possible without sitting down to write. And you're not going to write unless you have a place to do so.


• Be your own reference. When you're debugging a problem at work, chances are you're not the first person to run into that issue. Writing it down on your blog will not only help you gain a better understanding of the problem and help others solve the issue, but also in a year when you run into the same issue, you've got a refresher waiting for you on your blog.


• Honest record of the past. Our memories aren't the best. Having a blog will help you remember just what you thought and felt, for better or for worse, when those events weren't so near.


• Own your data. Twitter is a micro blog. Instagram is a photoblog. But these blogs aren't yours. Yes, you provide the photos. And yes, you provide the witty content. But all of it disappear in an instant at some company's discretion. Putting your data on your own blog protects you and your memories.

It doesn't matter where you start your blog, or how cool your domain is, or how many people read it, or what programming language it's written in. What matters is that you start.

I'm not sure how much of it was "father of a toddler" and how much of it was "global pandemic", but 2020 felt hard.

While I've been fortunate enough that work hasn't changed for me – instead of going in to the office once a week (by choice), I just don't go in to the office and I haven't been to Tokyo since mid-February. We already communicated entirely with Slack with the only change being that people now hop into voice/video calls more readily than before. BeProud continues to be a fun place sling Python.

I started running regularly midway through the year with small gaps here and there. Thus far I've managed 64 runs totaling 317.6km. There's still a week left and I'm 15km away from my 50km distance goal this month, so those numbers will increase a bit.

This year I started on a path for digital independence and to control my own data. I moved my email from a gmail account made a couple of months they opened to my own domain hosted with Fastmail. If Google were to lock me out of my account for whatever reason, I should be mostly unaffected.

After many years of having no blog and no home on the internet, last year I began experimenting with blogging/tweeting with micro.blog. I slowly remembered how much fun it is to have a home on the internet – somewhere that you can call your own. And this year I moved to a self-hosted Wordpress (for now) blog. The community on micro.blog is great, so I still post there with my blog's RSS feed.

I also started to try working in public more. I haven't release anything yet, but I began collecting my notes, thoughts, and learnings here and in my notebook.

2020 also marks when I became aware of the impact of digital waste. As a web developer I've known that websites have been bloated for a while and it frustrates me to no end. But until this year (and thanks to Gerry McGovern I hadn't connected was the link between data transfer and energy consumption. This led to me writing two articles: Designing Sustainable Digital Products and a guide for migrating your Digital Ocean droplets to sustainable regions powered by renewable energy.

This new awareness also led me to try and reduce the data-transfer and requirements from my own website. I made a custom theme that uses system fonts and minimal css (though there's still too much).

Looking forward to the new year I'd like to double-down on low-energy blogging and websites. Not just for my own blog, but potentially as a service. I've started collecting my thoughts about how such a system could work to maximize privacy and minimize energy consumption in my blogging engine notebook.

Blogging makes the internet fun again and in 2021 I'd like to help people re-discover and remember that fun.

I recently mused about how my next computer should be a Thinkpad running Debian. I still half-think that, but I feel conflict on the issue. Let me explain.

My first Mac was an iBook G3 running OS X 10.1 in 2002 and I've been on Apple computers exclusively since. I came from running desktop Linux (Gentoo at the time) and a major reason why I switched to OS X was the unix environment without the fiddling.

Over the years I starting developing native apps and valuing apps that take the time and effort to be consistent with the systems. The consistently between apps made the entire system feel cohesive and easy to use. "Mac Apps Behave / Are Designed Like This". I was hooked. I am hooked.

But the world has changed since those days. We're now connected to the net with fiber rather than dialing in for a ~couple~ all hours of the night. Web browsers have become the new platform to target and Every app is cross platform and nothing is native.

Hardware is a growing concern for me as well. Apple makes some of the best laptops. I look forward to the Apple Silicon Macs. But repairing your Mac often means replacing the entire unit and paying more than purchasing a new one. They're no longer upgradable and filled with glue.

Contrasting with Thinkpads you can upgrade the ram, swap out the hard drive, add in LTE modems, and even change the display. If something breaks you can replace just that part. Expandability should allow the machine to have a longer life. I can even get them fully supported with Ubuntu or Fedora Linux.

If the software I use on a regular basis no longer native, not designed for the Mac, and everything is inconsistent, what's the advantage of using them on the Mac?

I finished watching Long Way Round while waiting for new episodes of Long Way Up. The adventure travel reminded me a lot of blogs I used to read when I was in high school¹ and college² and dreaming of studying abroad in Japan and living in Japan in general.

In those days, we'd blog, maybe post a bad photo or two, and commented on each others' sites. Nobody knew each other in real life, but, over time, you'd get a real sense of community. You were of course following the posts, but there were also a regular cast of commenters that you'd also get a sense of knowing. It felt authentic...and innocent.

Why can't we have this today - but on larger scale? How would you even find these sites on the modern web? Everything is hidden behind "the algorithms" and or paid for by a marketing campaign. Can you even find them?

¹ Sushicam.com was a great photo blog by a guy living in Japan. I used to have a few prints of his and also bought his old Canon 10D - until my parents said "If you have enough money to buy a camera, you have enough money to pay rent".
² Justin Klein was a great blog from a traveling programmer. Not just Japan, but all over the world.

One of the tasks left for me to improve the sustainability of my website is to reduce the size/transfer of the images on my site. This is actually two tasks: optimize the images themselves, two lazy load images so they only load when scrolled into view.

I'm not too interested in lazy-loading images as it would require adding more Javascript and client-side execution. So I plan to focus on optimizing images in place for now.

My blog is powered by Wordpress, so it should be as simple as installing one of the many "image optimizer" plugins. However, for a variety of reasons, including but not limited to image optimizing happens on their servers, or they want to use their CDN to delivery my images, or the plugin just kinda looks spammy, I haven't taken the next time.

My designed image processing shouldn't be too difficult - just call pngcrush and imagemagick depending on if I upload a png or jpeg file.

I've asked myself how do I address image optimization on my website: do I write my own image optimization plugin? Or do I do something else?

I haven't written PHP in a very long time I don't partially fancy developing a new Wordpress plugin. But it could be nice to make a nice, clean, no fuss plugin available for others to use.

However, I'm leaning towards "something else" and think a more generic solution might be better. i.e. What if I had a small daemon (probably Python, maybe Rust as an excuse to learn it?) to monitor a directory and automatically optimize the images when they're saved. This way no plugin is required and it could be used no matter the blogging engine.