Matthew Lang

I was looking at the DuckDuckGo traffic for the last few years. The stats are pretty impressive. A seven-fold increase in queries over the previous five years and this month’s number of queries is already more than last January. It looks like it’s going to be another year on year increase for queries.

It’s got me wondering about my usage of DuckDuckGo.

DuckDuckGo has been my search engine of choice for many years now, and as a result, I’m pretty familiar with a number of the bang methods that are available to help with your searches.

Now, I know DuckDuckGo is a privacy-first search engine. It’s why I use it in the first place. Saying that I’d still be interested to know how many searches I do over the year and how often I use the different bang methods. I don’t want the actual search terms tracked, just the number of times I search and how often I use each of the bang methods.

If DuckDuckGo did this, it would raise a few concerns about where they are going with tracking. This functionality might be best done in a browser extension so that it’s purely an opt-in feature.

Not everyone will agree with me about tracking your search usage, but I still think it would be quite interesting nonetheless.

On Sunday night, I migrated a couple of Rails apps to Ruby 2.7, including Writeabout. Last night, I did the same with another Rails app. By the end of the week, I hope to have Markcase moved over to Ruby 2.7 and Dailymuse upgraded to Ruby 2.7 and Rails 6.0.

Upgrading apps is a pain if they’re left alone for too long. I’ve left Dailymuse alone for such a long time that it’s still sitting on Rails 5. Markcase is on Rails 6 but requires a wee bit of maintenance regarding Webpack.

I’ve learned that leaving apps for such a long time between updates is not the best thing to do. Even upgrading an app regularly through its patch versions is better than just leaving them sitting gathering dust.

Last night I needed a much needed break from the usual Rails coding, so I worked through an example on the StimulusJS website so that I could add a “copy to clipboard” button for the displayed writing prompt on Writeabout.

For me, this is the ideal level of integration I need with JavaScript. A framework that does some of the heavy lifting on the user-interface without me having to re-write the whole front-end.

The end result is nice, but I don’t like the way the elements on the page move up and down when the copy button has been pressed. I’ve added a little div section with an indicator that the button has been pressed. It disappears after a few seconds, but it moves the elements on the page up and down when it changes its display state. I’ll fix it another day, but the first pass at this functionality is still good.

Over the holidays I mentioned that I was writing a blog post that I would publish this week. Well, after a delay thanks to the flu, I finally hit the publish button on my return to using my main domain. My first post, about my focus for 2020, is a return to building up some long form content that I want to reside on that domain.

Is this the end of my time on Micro.blog?

Definitely not. Micro.blog is a wonderful blogging platform that I will keep on using. This blog on Micro.blog will be my social feed to the net. It’s the one place that I will post to daily. Short posts, photos and links will continue to pour out from here.

So what’s the point of the new site?

For a while I’ve been trying to find a way of supporting short and long content. I’ve tried mixing these two lengths of posts over the years and it’s never sat well with me each time I have tried it.

Now that Micro.blog is my daily social feed, I can now focus on pushing longer posts through my main site again.