In recent years, advances in artificial intelligence (AI) technology have promised to revolutionize many aspects of our lives. However, this has not been the case in the world of blogging. In this blog post, we will discuss why AI isn’t going to change blogging for the better.

AI apps and automation are often touted as being able to revolutionize the blogging industry. However, there are still many issues with these technologies that could prevent them from having a major impact on blogging. For example, AI apps and automation can be expensive and difficult to maintain, and the quality of the results they produce can often be far from perfect.

Bloggers rely on the human touch to create content that resonates with their readers. AI technologies are still far from being able to replicate this level of creativity and emotion, making them less useful for bloggers.

Finally, implementing AI technologies into a blogging platform can be a difficult and time-consuming process. This is due to the complexity of the technology and the time required to properly configure and maintain the systems.

In conclusion, AI is not going to revolutionize the world of blogging any time soon. AI apps and automation are still too expensive and difficult to maintain, they cannot replicate the human touch that bloggers rely on, and implementing them into a blogging platform can be difficult and time-consuming.

You guessed it. I “wrote” this with Notion’s AI tool.

I’m not really surprised. In fact, I’m surprised it took this long.

Back when Elon bought Twitter, one of the first things I did was to start using the official iOS Twitter app. I kept Tweetbot on my phone, but I used Twitter instead full-time because my assumption was that at some point third-party apps were going to be banned.

My use of the official Twitter app was fairly short-lived. The app sucks, to be quite frank. The algorithmic timeline is completely terrible and the injection of ads and sponsored tweets made it even worse. Even the act of composing a tweet was subpar.

I had been a Tweetbot user for the better part of a decade. To me, Tweetbot was Twitter. The chronological timeline, free of ads, and consisting entirely of the tweets and retweets of the people I followed and nothing else, was the epitome of the Twitter experience.

But good old Elon has decided that Tweetbot and all the rest of the third-party apps must go! Perhaps he’s jealous of the higher quality of Tweetbot, Twitterrific and others. Whatever the case, Tweetbot is cut off at the API and dead. RIP.

Enter Mastodon

Fortunately, I stopped using Tweetbot months ago when I deactivated my Twitter account in favour of Mastodon. I was lucky that I had started following Paul and Mark from Tapbots on Mastodon mostly so I could stay up-to-date on the happenings with Twitter and Tweetbot.

I figured the first place that I would learn about the death of third-party apps at the hand of Elon would be from the Tweetbot people. The fact they had gone to the trouble of setting up a Mastodon instance for Tapbots was a very good sign that something was brewing.

More fortunately, I was able to get one of the few TestFlight slots on the very first day that their new app, Ivory for Mastodon, was revealed. It felt instantly like home. It was Tweetbot-like, but still true to Mastodon - familiar, but different and not at all in an uncanny-valley way.

Ivory is wildly good. Along with the recent influx of the tech community into Mastodon, the existence of Ivory has made the transition from Twitter to Mastodon quite easy.

You Waited Too Long, Elon

I shudder to think of what things would be like if Mastodon wasn’t a thing and if new apps like Ivory weren’t around. Quitting Twitter was made far more palatable because there was a viable alternative.

Perhaps the biggest mistake that Elon made was waiting too long to kill off the third-party apps. By the time he pulled the trigger last week, we all knew Ivory was on the way and the momentum was quickly building on Mastodon.

Back in Time

In many ways it feels like we’ve been transported back in time about 10 or 12 years to when Twitter was new and the web was still a place where we all built our own sites and blogs. Mastodon has rekindled that sense in a lot of people of late. We watched as wall-gardens were built up and destroyed the indie web that we all loved.

But now we have a chance to do it all over again and do it right. Mastodon is like Twitter, but built on open standards and federated. People are thinking about blogging again and bringing back their sites on their own domain names.

I’m starting to really question whether the remaining walled gardens are something I’m willing to continue to contribute my content and attention to. I’ve all but quit Instagram and haven’t used Facebook in years and years. I don’t have a TikTok and don’t plan to get one anytime soon.

Maybe the best thing to come out of Elon buying Twitter is that those of us who adopted Twitter back in the early days will be reminded of what we loved about the web back then. Will Elon kill Twitter completely? Probably not. But does it really matter anymore?

He’s already done enough to drive the nerds and internet junkies over to Mastodon. The indie devs are excitedly building apps that leverage open APIs and can’t be shut down by one stupid childish man. It’s the return of the internet we all knew and loved.

And for that, I say “thank you” to Elon. You deserve none of the credit for your own ineptitude, but the internet thanks you anyway.

It looks like Twitter (aka Elon) killed off most third-party apps the other day. That’s not a big deal for me since I quit using Twitter a few weeks back. The goal appears to be to push all users to the Twitter iOS app and to push the algorithmic timeline over the chronological one.

Over on Instagram, the same thing has happened except there aren’t any third-party apps to kill off. The algorithmic timeline is king and that has me really considering dropping Instagram from my life as well.

I have two accounts on Insta. My personal account I use to follow some friends and occasionally I’ll follow some accounts to get me hyped up for a vacation or event. For example, I added a bunch of photographers from in and around the Canmore and Banff areas recently ahead of our trip there over the Christmas break.

I have another account that I used to use to post my rail photography. That account has something like 750 followers but I haven’t done much with it lately since I haven’t been out to do much rail photography really since the start of the pandemic.

The problem with Instagram is that a few years ago they decided that users should be seeing more than just the photos their friends are posting. That “more” includes ads, suggested posts and recently, Reels.

I mostly don’t care about the ads or Reels and Instagram is pretty bad at suggesting posts. It’s all junk. The real issue is that Meta needs to make more money and it’s pushing more of the crap I don’t want at me and less of the photos that I do want to see.

Opening the Instagram app now is mostly a waste of time. I might see a new photo from a friend, although it’s more likely going to be a “story”. I will for sure see a crap load of suggested posts, a crap load of ads and a bunch of Reels that I don’t care about.

What About PixelFed?

Some have suggested PixelFed as the solution. I’ve tried PixelFed but there are a few problems with it, from my perspective.

1. They are trying to mimic Instagram. The app (in beta) is basically a rip-off of the Instagram UI. They also don’t allow browsing without an account which is user-hostile and a dark pattern to get users to create an account. Gross.
2. Nobody I know uses it. The content on PixelFed is okay, but the reason I used Instagram was to see photos from my friends. They aren’t on PixelFed.

I could post photos to PixelFed and try and get some friends to hop on as well. There’s a chicken and egg thing there for sure. But is that going to be successful? I don’t know.

How About Mastodon?

I could also just post my photos to Mastodon now and then and thanks to the wonders of ActivityPub and federation, I can just follow PixelFed users in Ivory or on the web version of Mastodon.

Most likely I’m going to stop bothering with Instagram and start posting more photos either directly to Mastodon or to my blog (and then linked on Mastodon). I think the single, federated account is the right way to go for me with posts that are test, photos and links.

It was -24ºC when I woke up, -19ºC when I went for a run, and then -2ºC out in Kananaskis where we did a hike.

The run featured some trails along the Bow River and a trot through downtown. Really nice views!

After lunch at Wendy’s we drove out to Kananaskis Country near Nakiska ski area and did the short hike up to Troll Falls. The falls were mostly frozen, but the neat thing about this one was that you could walk in behind the ice.

The water has carved out a cave-like area and we explored around there a bit before taking the long way back to the car across a wide meadow.

Scenic Drive

We took Hwy 40 to Hwy 742 to get back to Canmore. The 742 stretch was snow-covered and a bit more of an adventure than I would have expected given the conditions on 40. Still a nice way to end the day’s fun.

More sunny skies and cold temperatures. But it gets milder later in the day and there’s no wind so it’s quite lovely. I started the day with a run again and toured the Policeman’s Creek trail.

The blue skies were incredible this morning. Really stunning.

Lake Louise

After that we drove up to Lake Louise, hoping the same sunny weather we had in Canmore would make for some glacier views. Sadly it was cloudy up there, although it’s always beautiful no matter the weather.

On the way back to Canmore, we took the scenic route which included a quick stop at Morant’s Curve. There was a train tied up in Lake Louise and another one at Castle Junction so perhaps there were issues on the mainline. Whatever the case, no trains to be seen at the Curve, but it’s still a great photo spot.

Another great day in the mountains. Tonight it’s going down to -17ºC so the run tomorrow morning should be the coldest of the week. With the cloud cover comes a change in temperatures and Friday is supposed to see a high of 0ºC.

Started out with a run (as usual). Today was colder than yesterday but still decent since the sun was coming up and the winds were still light.

I ran down 3rd to the Bow River as far as the Engine Bridge, then along the Spur Line and up to the CP mainline.

I stopped for coffee again (after meeting up with Ginny at the lights on the way back…a nice coincidence).

Stoney Loop

After that, Lindsey and I headed out to do a hike up Stoney Lookout near Norquay. This was a nice forested trail up to the summit of Stoney with panoramic views across the valley and up towards Canmore.

It wasn’t the toughest hike ever, but a nice way to spend an hour and a half. Lindsey enjoyed it and so did I.

The way down was quite a bit steeper, ending in the parking lot at Norquay ski area.

Chill Afternoon

After that, we chilled for a bit and then drove out to Vermillion Lakes to see Mount Rundle at sunset. There was some wild ice there that was just thin enough to avoid walking on and we discovered a warm water spring feeding into the lake.

I’m actually finding it hard to believe we only got here a few days ago.

I got up a bit later and waited for dawn before I went for my run. I planned out a route that included a few streets that I haven’t run yet and ended at Eclipse Coffee at Railway Ave. and Bow Valley Trail.

It was a lot colder today compared to Sunday, but not uncomfortable. I ran down through Spring Creek and then along the river for a short time before heading up 8th (the main street).

I walked back the 500m from the coffee shop and enjoyed the views as the sun rose over the mountains and painted them in light.

Johnston Canyon

Next up we drove to Johnston Canyon and did the hike up to the Lower Falls. We did this back in 2013 the first time we came out with the kids at Christmas.

The trail to the Upper Falls was closed for maintenance, so it wasn’t the full length, but still quite nice.

Pictures don’t do it justice.

Lunch and Another Hike

After the canyon hike, we hopped back in the car and drove a bit further up the 1A to Castle Junction where we had another one of our patented car lunches of croissants with turkey and cheese.

Lindsey found another hike on AllTrails that was close by so we decided to do that before we headed back. This was just about a kilometre up to the base of a waterfall and then the same distance back.

We didn’t have any company on this hike (unlike the Johnston Canyon hike). It was quiet and peaceful with beautiful views across the valley.

After that hike we snapped a couple of pics of Castle Mountain against a perfect, clear, blue Alberta “big sky” and drove back to Canmore to chill for the rest of the day.

It’s the first day of our mountain getaway to start 2023. We had a great and uneventful flight from Toronto to Calgary. The luggage made it and we got our rental car for the one hour drive to Canmore.

I woke up at a decent time and geared up for a pre-dawn run around the town to tick off a couple more streets I’ve never run.

Christmas lights along the sidewalk in Canmore.

A dark trail along Policeman’s Creek.

Spring Creek bridge at dawn.

After that, we did enjoyed Rocky Mountain Bagel Co. bagels for breakfast (the best), and then did some groceries. Then we grabbed some Eclipse Coffee flat whites and went into Banff for a bit.

We accidentally left Mac’s coat in the living room in Toronto so we needed to fix that problem first. The Bay came through with a big sale on winter jackets and we solved that before lunch without too much damage to the credit card.

Bow River Walk

Once we had the coat sorted, we decided to walk out along the Bow River to Bow Falls and then back to the town centre. It was a beautiful day with sunny skies and mild temperatures. What a difference from last year when it was absolutely frigid.

Bow River in Banff.

Cascade and the pedestrian bridge.

Rundle and Bow Falls.

Bow Falls.

We got back to the car after about 90 minutes and then made a quick lunch of croissants with turkey and cheese and some veggies and chips. Packed lunches in the car is a Banff tradition for us and we always remark that we’ve become our parents. The last two years here with COVID, eating out was difficult and grabbing stuff to make a lunch for the car was always a great option compared to getting some takeout at a fast food place.

Lake Minnewanka

We drove out to Lake Minnewanka and went for a walk out on the frozen lake. There was less skating this year, but way more of the lake was frozen over. Spectacular views as usual.

Lake Minnewanka.

Lake Minnewanka.

It was all supposed to be pretty easy. Our kid Lindsey (they/them), a first-year engineering student at UVic, would catch AC1902 from Victoria International Airport (YYJ) to Toronto Pearson International Airport (YYZ) on the Tuesday before Christmas to come home for a couple of weeks.

A few days before that flight, we started seeing some interesting weather forecasts that called for things like 20cm of snow or worse for Victoria, BC. That seemed unlikely given Victoria’s history with snow and so we didn’t think a whole lot of it. Until Monday.

That morning it was pretty clear that Tuesday might be a bit on the messy side and that getting to the airport would be challenging. We weren’t even sure the flight would go if the weather turned out the way the forecasters were predicting.

The First Hurdle

On Tuesday morning, Lindsey woke up to 30cm of snow on the ground and a real problem. The entire transit system in Victoria was shut down along with basically every thing else in the city. Somehow AC1902 still showed as “on time”. It seemed inevitable that it would be cancelled.

Beautiful, but unwanted. Victoria is not prepared for this much snow.

Taxis were impossible to find as most drivers weren’t out on the roads. Nobody picked up the phone and ordering online just resulted in an endless wait or an immediate cancellation. I tried finding a ride on Reddit and by calling in a favour with a friend in Victoria, but neither were successful as the streets were basically impassable.

By late morning it was clear that getting to YYJ wasn’t possible. The flight now showed “diverted” to Calgary (YYC) first before Toronto and delayed for hours, but it wasn’t possible to get to the Victoria airport to catch it. We got on the phone with Air Canada and I started searching for alternatives. Believe it or not, that plane eventually did make it to Toronto.

A Friday Backup

I managed to book the same flight (AC1902) for Friday at great expense, but it seemed like our only option at this point. After nearly three hours on hold, we spoke with a very helpful Air Canada agent who cancelled our Tuesday flight and graciously swapped in our Friday flight at the same price rather than then $1,280 I had paid to book it.

We thought maybe that was how it would play out. Lindsey would stick around Victoria until Friday and then fly home. But then the storm watches started popping up for Toronto starting on Thursday and through Friday and Saturday.

Despair to Hope!

On Wednesday I talked to Lindsey on FaceTime and we talked about how tough it was there. Most of their friends had left for Christmas break on flights or ferries to the mainland and the campus was still closed and the city mostly shutdown by the snow. It was going to be a boring, depressing few days. Tears were shed.

I did a bit more clicking around and working the Air Canada website, learning how flights pop in and out as people book and cancel their flights. Eventually I was able to snag a flight on Thursday morning from YYJ to Vancouver International Airport (YVR) and then a three hour layover before a flight to YYZ at 3:00 P.M.

I was excited to tell Lindsey the new plan and, as expected, it was just the bit of news needed to get through the rest of that day.

Looking Promising!

We thought we were home free now. Lindsey was excited to have an end date for the time on campus and it looked like the Thursday flight would be out of Vancouver well before the coming storm in Toronto that was supposed to start late Thursday and really develop on Friday morning.

We had the Friday flight in our back pocket and I booked yet another ticket on Saturday’s AC1902. Worst case, we thought, we would have Lindsey home for Christmas although the thought of being in Victoria until the weekend was not appealing and the dorms were closing on Friday afternoon meaning there was no place to live and no dining hall to get food at.

Another Snowy Surprise

On Thursday there was more snow in Victoria. We tried the cab option again at 6:00 A.M. but it was clear that wasn’t working. BC Transit was running again finally and so Lindsey trudged through the snow with a big suitcase and caught a bus from the UVic bus loop towards downtown where another bus would meet up to go up near the airport.

That went decently well and Lindsey was within 1.7km of the terminal a little under two hours before the departure. Flights were leaving on time and the plane that would become the flight to Vancouver was at YVR and on-time to come over to YYJ.

The bus never showed but they were able to order a cab from the airport just five minutes away that got them there in time to check in. Things were looking very hopeful! Flights were on time and the weather in Toronto was good.

It’s All Gone Wrong AGAIN

Then the YYJ to YVR flight was abruptly cancelled. No flight crew was the reason. We were screwed. The only option provided for rebooking was on Christmas Day. We took it because “why not” and added that to the list of flights we had booked. We also learned that we were eligible for significant compensation for the cancellation of this flight because the reason was deemed to be within the control of the airline.

A New Hope!

I fired up the Air Canada website again and got to work. I fairly quickly snagged a red-eye from YVR to YYZ departing at 11:55 P.M. It wasn’t cheap, but it was an option. We huddled up over FaceTime and decided to leave the island on the next ferry and get to YVR and hope this red-eye went.

Lindsey took a cab to the ferry terminal and got a walk-on ticket for the 11:00 A.M. ferry to Tsawwassen south of Vancouver. I got on the phone with my running buddy Miguel who happened to be in Vancouver. He’s one of the nicest people I know, a great friend, and someone who is always willing to give of himself to help others.

I called in a big favour - could he drive an hour down from North Vancouver, pick up Lindsey at the Tsawwassen terminal and then take them to YVR? And if the flight was cancelled, could he give Lindsey a place to sleep for the night?

Yes. Of course. No question.

Lindsey was on the ferry now and we were committed to the Vancouver option for getting home. That move cut off our AC1902 flight options for Friday at least, and probably Saturday as well since catching those would then involve heading back to the island on the ferry.

But we were willing to risk that given the greater options for flights to Toronto from YVR and the fact that we had a friend on the mainland to provide a place to stay if needed.

Even Better!

Just as the ferry left the dock in Swartz Bay, I was able to snag yet another flight. This one was YVR to YYZ departing that evening at 5:45 P.M. Lindsey could get to YVR with the help of a pickup from Miguel and the inbound flight to YVR was already in the air and on-time. This looked very promising!

The ferry was delayed a bit, but Miguel was waiting to provide the ride to YVR. Lindsey got there in plenty of time to check in, drop their big suitcase (finally) and get through the security lines. Then it was a waiting game to see if the flight actually went.

We were really starting to feel hopeful at this point. The flight was on time, the weather in Toronto was holding and it wasn’t going to be snowy and windy until Friday morning. We had the red-eye in our back pocket. I had booked yet another flight for Friday afternoon from YVR to YYZ as the final backup plan.

At this point I was feeling good. We had six separate flights booked from two different airports to Toronto. Lindsey was checked into two flights on Thursday night and both were still showing as either on time or slightly delayed.

Heading Home

By 5:55 P.M. Vancouver time, Lindsey was on the plane. It was snowing a bit in Vancouver but it seemed like it was all going to work out. A stressful 55 minutes later, the flight finally took off heading to Toronto.

A great view.

I got to work cancelling flights now. First was the red-eye, then the Friday flight from YVR to Toronto. I imagined someone like me on the Air Canada website snagging that seat or someone on standby getting a spot and rejoicing that they maybe had a new hope to get home. Then I cancelled the Saturday YYJ to YYZ flight. Lastly the Christmas Day flights were cancelled.

These were all fully-refundable fares so the money was coming back to the credit card in big piles and the stress of the whole experience was finally melting away. There was one last flight in our bookings – the Friday YYJ to YYZ flight that was our original “backup” plan.

A Bit of Sleep

We went to bed for a few hours but set an alarm for 1:30 A.M. so my wife Ginny and older daughter Mackenzie and I could all drive out to YYZ to pick up Lindsey. The flight landed while we were driving out to the airport and we parked at Terminal 1 and went inside to the baggage area.

We waited for Lindsey to de-plane which took a while because there were no ground crews to bring the plane to the gate. Finally Lindsey came through the doors from the gates area and we were able to greet them with hugs and some tears. We did it!

The luggage hall was a bit of a disaster zone. There were suitcases everywhere and people standing around as well as sleeping on the few seats and on the floor. Every time a baggage carousel started up, there were cheers.

Unclaimed suitcases everywhere.

Meanwhile we got a notification from Air Canada that the Friday flight from YYJ to YYZ had been cancelled. That was the news we were hoping for as it turned our non-refundable ticket into a fully refundable one. We cancelled the last remaining flight and got the last of our money back (aside from money for the flight that Lindsey did take).

At about 4:00 A.M. an announcement was made that the bags weren’t coming and there were no baggage handlers until after 6:00 A.M.

People were…unimpressed. But we just decided that we would head home and get Lindsey home to bed after a long day. We’d go back after 6:30 A.M. and hopefully retrieve the suitcase. It’s about a 30 minute drive each way, so we got to the house just past 4:40 A.M. and into bed before 5:00 A.M.

We got about an hour more sleep before we got back up to head back to Pearson to get the suitcase with all the clothes and everything else Lindsey brought back. Ginny ran in while I looped around the terminal roads. The bag was there and we were all set.

We got home at about 7:30 A.M. and the mission was fully accomplished. Lindsey was asleep in their bedroom and the suitcase was in the hallway.

An Epic Christmas Travel Story

That’s the story of what was an epic adventure to get home for Christmas around three major storms and many challenges.

We were thankful that we had the financial resources to book all these flights along with the technical abilities to work the Air Canada website.

We were thankful for FaceTime calls so we could speak face to face and commiserate or plan next steps and support each other through a very stressful time.

I was thankful for the Apple FindMy app that let me see where Lindsey was and help navigate the BC Transit ride with live bus tracking from the Transit app.

We literally couldn’t have done it without the help of a good friend who dropped everything to lend a hand. Thank you Miguel.

And lastly, we were grateful to everyone at Air Canada, BC Ferries, BC Transit, all the baggage handlers, aircraft maintenance workers, and everyone else who was working extremely hard under tough circumstances to get as many people to where they wanted to go as possible.

Merry Christmas everyone.

I was a devoted Firefox user for many years but recently, the list of annoyances with Firefox started to pile up.

Some of this is self-inflicted like the Proton redesign that changed the UI for the tabs in what I thought was a step backwards. Google also started to purposefully break things on Firefox including stuff like background blur on Meet calls and fullscreen viewing in YouTube.

I switched to Brave for a year or so and enjoyed that browser quite a bit. It’s Chromium underneath meaning that it shares the open source core that Chrome is built upon. Extension support is excellent and the look and feel is nice.

But Brave comes with a weird crypto play called Brave Rewards built around the Basic Attention Token (BAT) which is a cryptocurrency coin. You can disable all that stuff, but it’s not something I think belongs in a browser.

That left me looking for something new. I tried Safari but the lack of good extensions (especially for ad blocking) made that a non-starter. Orion is a new browser that looks a lot like Safari but adds Chrome/Firefox extension support. It’s in beta and it shows – it’s far too buggy to be an everyday browser.

Microsoft offers Edge that is also built around Chromium, but like Brave, they layer on a whole load of unwanted stuff. In the case of Edge, there’s shopping and other crapware built in that I don’t want.

What’s left? Vivaldi.

I’ve resisted Vivaldi a bit over the years because I don’t like the look and feel of it. I find the tabs and icons to be a bit weird looking, especially on the Mac. But I thought I would give it another go, partly because I like the direction things are going with Vivaldi but also because I learned that the UI is quite customizable.

Vivaldi’s UI is built using HTML and CSS meaning you can tweak things to your liking (to a certain extent). I’m not doing a whole lot, but I added a bit of padding on the left side of the bookmarks bar and bumped up the font size a half a pixel to make it look just a bit better to my eye.

One thing I still don’t like is that the tabs in Vivaldi are a touch narrower than I would prefer. I haven’t been able to figure out how to add some width yet, but I suspect it’s possible with the right CSS bits.

I’ve deleted all the other browsers from my laptop (except Safari) and I’m using Vivaldi full time now. So far so good.

I was a devoted Firefox user for many years but recently, the list of annoyances with Firefox started to pile up.

Some of this is self-inflicted like the Proton redesign that changed the UI for the tabs in what I thought was a step backwards. Google also started to purposefully break things on Firefox including stuff like background blur on Meet calls and fullscreen viewing in YouTube.

I switched to Brave for a year or so and enjoyed that browser quite a bit. It’s Chromium underneath meaning that it shares the open source core that Chrome is built upon. Extension support is excellent and the look and feel is nice.

But Brave comes with a weird crypto play called Brave Rewards built around the Basic Attention Token (BAT) which is a cryptocurrency coin. You can disable all that stuff, but it’s not something I think belongs in a browser.

That left me looking for something new. I tried Safari but the lack of good extensions (especially for ad blocking) made that a non-starter. Orion is a new browser that looks a lot like Safari but adds Chrome/Firefox extension support. It’s in beta and it shows – it’s far too buggy to be an everyday browser.

Microsoft offers Edge that is also built around Chromium, but like Brave, they layer on a whole load of unwanted stuff. In the case of Edge, there’s shopping and other crapware built in that I don’t want.

What’s left? Vivaldi.

I’ve resisted Vivaldi a bit over the years because I don’t like the look and feel of it. I find the tabs and icons to be a bit weird looking, especially on the Mac. But I thought I would give it another go, partly because I like the direction things are going with Vivaldi but also because I learned that the UI is quite customizable.

Vivaldi’s UI is built using HTML and CSS meaning you can tweak things to your liking (to a certain extent). I’m not doing a whole lot, but I added a bit of padding on the left side of the bookmarks bar and bumped up the font size a half a pixel to make it look just a bit better to my eye.

One thing I still don’t like is that the tabs in Vivaldi are a touch narrower than I would prefer. I haven’t been able to figure out how to add some width yet, but I suspect it’s possible with the right CSS bits.

I’ve deleted all the other browsers from my laptop (except Safari) and I’m using Vivaldi full time now. So far so good.

I got my hands on a Synology DS920+ a couple of years ago. It has two Seagate Ironwolf 4TB drives in it meaning I have a few TB of backup space sitting on my desk in the basement. But besides backing up your files, photos or computers, what else is a Synology good for?

1. Plex Server - I run a Plex home media server on my Synology along with Sonarr and Deluge (in Docker to pull down shows automatically). I generally use this to run a home PVR, downloading mostly stuff I could already get with my cable package. The downloads are nice though because there are no commercials.
2. Homebridge - I also have a Homebridge server running that bridges my non-HomeKit smart home devices over to the HomeKit world. You can read more about my Homebridge and HomeKit setup if you want.
3. OpenVPN - one of the best uses for a home server is running your own VPN. With OpenVPN, I can connect back to my home network (and internet connection) from virtually anywhere in the world. That means secure connections on public wifi and also access to shows and services like Bell Fibe TV from outside Canada since the data actually flows through my home internet IP.
4. Photo backup - I have my entire Lightroom library of photos backed up to my Synology in addition to being in Adobe Creative Cloud. It gives me some peace of mind in case something were to go badly with the cloud service.

Some other uses for a Synology include acting as a Apple Time Machine backup destination. Since the Synology is networked, it can be a great solution for providing storage for multiple computers in the household.

It's also possible to run your own Dropbox-type solution via apps like OwnCloud. You can even host a WordPress blog and your own email server if that's your thing.

Do I miss Twitter? Not really.

There are a few things that bring me back occasionally to do a search. Mostly it’s real-time news or information, including breaking news events like earthquakes or plane crashes. It’s also things like updates from our transit service on diversions and closures.

Over time as more and more people join Mastodon, there will invariably be more of that kind of information away from Twitter as well. A bot sort of provides re-posts of the transit information in Toronto, but it’s not all that reliable. I might just create my own with a combination of the various services I want all in a single Mastodon account.

When Twitter started, it didn’t have all this stuff either and it took a long time before it became the place the world went for information and news. Mastodon will get there eventually.

I’ve had a few “smart” devices around the house, but generally they all used Amazon Alexa for control and not Apple’s HomeKit. But with the recent updates to HomeKit (coming in iOS 16.2) and the news that Amazon is losing mega money on Alexa, I decided to give HomeKit a try.

I don’t have the most complicated setup:

1. Logitech Circle 2 camera - front porch.
2. Wyze Cam v2 camera - floats around as needed.
3. Wyze plugs (2) - desk lamp and other things as needed.
4. Wemo plug - fan.
5. TP-Link outdoor two outlet plug - Christmas lights.
6. Wyze Colour bulbs (6) - basement lights, front porch light.
7. Ecobee - smart thermostat.

Three of those devices have HomeKit support built in - the Logitech Circle 2, the Wemo plug and the Ecobee. Adding them to HomeKit was a snap. The rest doesn’t have HomeKit support so that meant I needed a solution for all the Wyze gear and the TP-Link plug.

Homebridge

That solution was Homebridge which is a server application that builds bridges between non-HomeKit devices and HomeKit. It runs on a server like a Raspberry Pi, or a Mac mini. In my case, it’s running on my Synology DS920+ NAS.

Set up was a little complicated, but not ridiculously so. Homebridge was easy to setup and get added into HomeKit. Once that was done, it was a matter of adding the plugins to Homebridge that I needed for my specific devices.

I used Homebridge Wyze Smart Home and TP-Link Smart Home. That took care of the bulbs and plugs plus the outdoor dual plug. That left just the Wyze Cam v2 which needed a different plugin. I used Homebridge Camera FFmpeg for that which required the Wyze Cam v2 to have the RTSP firmware (which I had already installed on mine).

HomeKit Hub

HomeKit also requires a Hub for all this to work. That hub can be either a HomePod mini or an AppleTV. I opted to get a new AppleTV 4K as I only had an older 3rd generation AppleTV around and it doesn’t offer full support for HomeKit.

Everything is all set up now and I can see my two cameras in the Home app. Plus everything is controllable via the app, by talking to Siri and also using HomeKit automations. That last part is really exciting to me as I’ll be able to do things like have lights turn off and on as people leave and arrive back home.

I’ll probably swap out the Wyze stuff over time for Philips Hue or something else. But until then, Homebridge does a great job bridging the non-HomeKit devices and the HomeKit world.

I’ve been full-time on Mastodon for a week or three now and don’t really use Twitter anymore. I check there every now and then, but I don’t follow anyone or post there.

In my time on Mastodon, I’ve noticed some things that are very similar to Twitter, but also a few things that are a little bit different. Here’s a few notes if you are just wading in.

• If you are on an instance that is not “general” and aligns with your interests, then the Local Timeline is worthwhile to look at. You can find new people to follow or at least see everything that is posted across your entire instance. If you are on a huge instance like mastodon.social, it’s not as great.
• The Federated Timeline is a little bit bananas. If you were on Twitter back in 2006-2007, then you might remember that you used to be able to just watch literally ALL the tweets go by. The Federated Timeline is like that and it’s exactly what you would imagine.
• DMs are different than on Twitter. If you have a DM conversation going between you and someone else, and then you mention a third person, they get pulled into that chat and can see the previous messages in the conversation. So be careful with that.
• Posts (sometimes called Toots) have different options between public and private. You can post public posts, unlisted (like public, but they don’t show up in searches), followers only and @mentioned only.
• Hashtags really matter on Mastodon. Search is generally best with hashtags so if you want your posts to be found, sprinkle a few #hashtags through your #posts and enjoy some increased #engagement.

I’ve noticed significantly more conversation happening on Mastodon. I’m pretty sure that the majority of Twitter users don’t read or even see a lot of the tweets of the people they follow thanks to the algorithmic view that Twitter forces on users.

It’s also clear to me that a high percentage of Twitter followers aren’t even there anymore. You might have 200 followers, but 100 of them no longer use Twitter, and when you Tweet, perhaps ten of your followers actually see what you posted.

On Mastodon, it’s far more likely that a higher percentage of your followers are actually using the service and will also actually see your posts.

Is Twitter dying? I don’t think it matters anymore. Mastodon is growing and people are discovering that there is an alternative social network to the bird site owned by the egomaniac billionaire.

I believe Mastodon has nearly reached a critical mass or inflection point where it can go from fringe alternative for geeks and nerds and will become something that anyone can, and will use.

The average person has now at least heard of Mastodon. They know it’s a Twitter-like service. They’ve heard of the fediverse and at least have a sense of how Mastodon is different from the centralized Twitter service. It’s all over the mainstream press and not just the tech blogs.

A few things could happen in the next little bit that would have significant impacts on Twitter and Mastodon.

1. The World Cup or another event brings back the fail whale – historically, large sporting events like the World Cup have put signficant strain on Twitter. Between the recent layoffs, firings and resignations, it’s possible that a significant event might lead to downtime. If Twitter goes down, there will be further and significant influx of users to Mastodon.

2. Trump reinstated – Elon Musk could reinstate the account of Donald Trump. If Trump returns to Twitter, it may very well be “a last straw” for some users. Until recently, there wasn’t a viable option for them, but Mastodon is growing quickly and many of these users who quit Twitter will head to Mastodon. UPDATE: Trump was reinstated not long after I posted this.

3. Brands and celebrities join – a few brands have waded into Mastodon, and if Twitter continues to implode, more will follow. Similarly, some of the “nerd” celebrities have joined or moved to Mastodon. Mainstream celebrities will naturally follow if they see the platform grow.

4. The media joins – Twitter is widely seen as a place to get realtime news and information. Right now Mastodon is not there yet, although as more users join, more info, videos and photos about significant events like storms, accidents, etc. will show up on Mastodon. If journalists and media outlets start to join, this will have a big impact on what kind of content can be found on Mastodon.

5. Bots – there are a ton of bots on Twitter sharing weather warnings, earthquakes, news, quotes, and fun stuff. Mastodon welcomes bots and makes it easy for users to create them. There are already bots on Mastodon, but not the breadth of what’s available on Twitter.

6. Apps and sites integrate Mastodon features – so many apps and websites have things like “Share to Twitter” built in. If Mastodon gets enough users, app makers and website owners will add “Share to Mastodon” making it far easier for users to quickly share content.

Mastodon has very little control over these things. But users of Mastodon can have a big impact on adoption.

We can quit Twitter and make a point of saying why we’re leaving and that we are going to Mastodon. We can push brands and celebrities to make the switch through tweets and encouragement. We can do the same for media outlets and journalists by suggesting they at least join Mastodon and cross-post. We can build bots to bring news, weather, alerts and other information to Mastodon. We can push app makers to add “Share to Mastodon” buttons and suggest to websites that they do likewise and we can add that functionality to our own sites.

This is the best chance we have to bring the fediverse and Mastodon into the mainstream. It’s not going to be a single event that does it, but a series of events that are used to build momentum that will take it to critical mass. Once we get there, it’ll be unstoppable.