I have a PocketBook InkPad Color and PocketBook Color (both first generation). I run KOReader on both. I tried to do an OTA update of KOReader, but it failed in both cases (locked up after hitting update) and trying to launch KOReader would freeze the device. My first idea was to update manually by connecting the PocketBook to my computer. I was still unable to launch KOReader. But then I noticed that there is an “ota” directory (Applications/koreader/ota). I emptied the ota directory. The app them launched as expected. Thus, if your ota update for KOReader on a PocketBook fails, try (1) updating manually through PC link and (2) clearing the ota directory before trying to launch.

A hand holding a Pocketbook in a blue case and a larger PocketBook InkPad Color in a gray case. Both cases are closed. There is a keytboard in the background.
My PocketBook Color and PocketBook InkPad Color. Note my keyboard (seen below) has USB outlets, which makes connecting them to my computer very convenient.

Of course, since that was the second consecutive time an ota update failed for me, I think I will just update manually through a PC link going forward. I already add books through PC link in any event.

Saturday was Newsletter day and I was busy on Sunday, so our daily Pook-Emu Bee links had the weekend off. But there are no such impediments this Monday, so I am back with my regularly scheduled links.

1. Indie developer lands in Steam approval limbo after being flagged for IP infringement over in-game references to their own past work (Amber V for Automation West. May 4, 2026.)

A cautionary and potentially instructive story for people who want to promote their own projects in games they publish to Steam (albeit very frustrating for the developer, assuming the facts are true as presented).

2. Ask.com, aka Ask Jeeves, has officially shut down after nearly 30 years online (Paul for AlternativeTo. May 4, 2026.)

You may read this story and think “what?” or “that didn’t die 15 years ago?” But I read it and sighed. I may need to write a Norton Safe Search follow-up article (see my original research article).

3. GameStop Proposes to Acquire eBay at $125.00 Per Share (GameStop Corp. May 3, 2026.)

Out: To the Moon. In: To the eBay.

4. Lipton releases… Pudding Milk Tea in Japan?!? (Oona McGee for SoraNews24. May 1, 2026.)

I’d try it. But it would probably take too much effort.

5. Reporting, the Easy Way (John Hinderaker for PowerLine. May 3, 2026.)

I publish long articles without compensation. Never once have I published a purported quote gleaned from a search engine’s AI summary of a query. But some N.Y. Times journalists who are being paid take a different, looser approach to gathering quotes. (Albeit credit to the Times for correctly identifying the error and not deflecting blame.)

6. Growing Sinkhole Causes Safety Concerns In Red Hook (Aurora Fowlkes for News12 Brooklyn. May 3, 2026.)

I walked by that intersection yesterday but did not notice the sinkhole. How close did I come to falling inside Red Hook?

7. Lime Wants Mamdani To Bring More Scooter Share To NYC (Sophia Lebowitz for StreetsBlog NYC. April 30, 2026.)

Absolutely not. This suggestion is a lemon.

8. Tucker Carlson nicotine pouches part of $4M in cargo recovered as theft ring exposed (Daniel Farr for the New York Post. May 2, 2026.)

Prediction: I wonder how he is going to attribute this to Israel and Mike Huckabee. Or has he already done so? I may not be upp to date.

9. The Wrong Kind of Black Poet (Ernest Jesuyemi for Compact. May 4, 2026.)

Interesting and thoughtful essay.

Replied to Observations on blocking various webbots by Sean Conner (The Boston Diaries)
Going through the logs from my web server for March, I noticed that 26% of all requests resulted in a failed client request (stuff like “404 Not Found” or “429 Too Many Requests”). These requests are more annoying than they are debilitating, but ideally, I would love a way to crash these bots as they're mostly scanning my site for exploits; fully 50% are just scanning for various PHP based scripts (which I don't use at all) and the rest for a variety of other files that can lead to exploits.

Sean Conner at The Boston Diaries wrote about trying to block annoying and/or malicious bots from crawling his website. It is a good read.

Beginning in late 2024, I started noticing The New Leaf Journal going down periodically. The server logs suggested that it was being overrun by bots and crawlers. I tried various methods to ensure that NLJ would be up all the time, including fiddling with Apache configs and my .htaccess file. I stumbled upon the “solution” (for now, at least) in late January. I use Cloudron to manage this server (which is home to both this site and NLJ). Cloudron has a built-in firewall. Back on January 30, I published Using Cloudron’s IP Firewall. I populated its firewall with IPs from the AbuseIPD blacklist, which is readily available in LittleJake’s GitHub repository. NLJ’s resource usage went way down (see the chart in my linked post) and my crashing issues have been gone for more than two months. The AbuseIPD blacklist is updated approximately every six hours. I have been adding the IPs manually but I have been meaning to look into a way to automate the process.

I had been using XFCE as my desktop on EndeavourOS. I switched to Cinnamon after having some issues with XFCE (I believe tied to Nvidia drivers). Since I switched my desktop environment, I then had a hidden files display issue in Thunar (the default XCFE file manager), so I switched to Nemo (Mint’s). Nemo works but for one issue. It was not showing image and video previews by default (only placeholders). I found an issue on the EndeavourOS forum from 2022. One poster had a solution:

In Nemo preferences, click on the Display section, and in the pull down menu next to “Only for files smaller than:” select “32 GB” (this is the default in Linux Mint 21).

I did not find the “Only for files smaller than:” setting in Display. However, this forum post was written in 2022. I did find it in Edit > Preferences > Preview:

Nemo file manager preferences: Display section.

The default for Nemo when installed using pacman on EndeavourOS was 1 MB for article previews. I upped it to 4 GB (as you can see above). Problem solved.

I run EndeavourOS on my main workstation. I recently switched from XFCE to Cinnamon due to having flickering/performance issues with XFCE after a Nvidia update. I was still using XFCE’s Thunar as my file manager. However, I ran into a strange bug starting yesterday where toggling “show hidden files” caused Thunar to crash with a segmentation fault (I love segfaults). I searched for a solution, but found that while I do not seem to be the first person to have had this issue with Thunar, there was no obvious fix. Very “year of the Linux desktop” moment. But fortunately, Linux makes it easy to circumvent problems instead of dealing with them head-on. I replaced Thunar with PCManFM and now everything works as expected. (I thought about going with Cinnamon’s default file manager but I have used PCManFM on other systems so I went with the lightweight option.)

I ran a full upgrade on my desktop workstation (EndeavourOS, which is based on Arch). One of the upgraded packages was nvidia-open-dkms. After the upgrade was complete, applications were flickering on my desktop. The same thing happened last week (I fixed with a “downgrade”). I decided that I did not want to downgrade again, so I investigated. Some posts in the EndeavourOS forum indicated that the issue was particular to XFCE. I decided to try a different desktop environment, preferably one I could set up quickly to go with my workflow and one that would not come with a whole slate of stuff I do not need. I landed on Cinnamon. I had only used Cinnamon for about 10 minutes before, but it works well (no flickering) and I configured some of my shortcuts from XFCE. It will do.

I mentioned in my previous post that I could not send our regular weekly newsletter due to a formatting issue in Buttondown. Fortunately, my support request was answered quickly. It turned out that I had an extraneous tag in the header (it had not caused any issues before this week). I sent the email. In so doing, I learned something interesting about Buttondown. Two reasons I like Buttondown is because it has a full searchable archive and an RSS feed. That is, it functions like a blog which supports my making Newsletter Leaf Journal its own publication. For today’s email, I set NLJ copy as the canonical URL since I published that before sending the email. To my surprise, I learned that when you set an external link as the canonical, the archive link for the newsletter takes you to the original instead of the Buttondown version (I assumed that the Buttondown archive version would be accessable but with the canonical tag pointing search engines to the original).

I use Buttondown to host my weekly newsletter, wherein I share links from this site and The New Leaf Journal as well as 21 links from around the web and other news and notes. I had finished drafting my newsletter. Unfortunately, Buttondown is producing garbled formatting that I would not want to put in anyone’s mailbox. I sent an email to support. In the meantime I published the newsletter on NLJ. Buttondown allows for setting canonical links, so it will not be an issue once I can finally mail the newsletter to our regular subscribers and newsletter followers.

I use a NETGEAR WAX 202 router running OpenWrt as my wireless access point. Unlike my router (MikroTik hAP ac3 running MikroTik’s RouterOS), it does not update automatically (I configured a script for the router after having previously upgraded it the old-fashioned way). I forgot about AP updates for some time. After remembering, I installed the latest OpenWrt on my WAX 202 on Thursday night through LuCI. The AP did not reconnect on its own. After about 20 minutes, I unplugged the AP and then plugged it back in. It worked. That was a relief. I was not looking forward to troubleshooting (having had done my fair share of troubleshooting in recent days). I also upgraded my TP-Link Access Point (now dedicated to delivering internet to a mini PC in the other room) for good measure (that update went through without any intervention on my part).

My test running Ubuntu Touch on my Pixel 3a XL as my primary phone continues. I received an MMS for the first time today. Instead of displaying the MMS, the default Ubuntu Touch messaging app told me it could not be downloaded. I tried fiddling with the APN settings to no avail. Then I found the solution in a long UBports forum thread titled No MMS with Wifi ON. I read the thread and tried the recommended solution of turning wifi off and then downloading the message. This worked. However, I agree with a number of commenters in the thread that (1) MMS should ideally work with wifi on and (2) at a minimum, the error message should note that MMS does not work with WiFi on (unless your phone is receiving internet from another device via mobile hotspot). Of course, I cannot receive MMS on my Pixel 6a (running GrapheneOS) with WiFi calling on, so MMS may indeed be a complicated issue.

Filed an Issue Koko Analytics Recording SBInstitutionsBot/0.1 Requests as Visitors/Page Visits · Issue #296 · ibericode/koko-analytics by nafnlj (GitHub)
My Set-Up I run the non-pro version of Koko Analytics on my WordPress site. I disable cookies and exclude visits from all logged-in users. What Happened? On two separate days, Koko Analytics was sh...

On March `12 and 19, I received a highly unusual number of visitors and page views on The New Leaf Journal according to Koko Analytics. By “unusual,” I mean about 10X as many visitors as expected. No individual article had an unusual number of views and my Koko Analytics stats showed the usual list of referrers (mostly search engines) at usual referral numbers. I checked by server logs on the 19th and determined that the likely culprit was SBInstitutionsBot/0.1 (it appears to be a Japanese web crawler for AI), which was hammering my site with requests as I was seeing unusually high visitor numbers. I used Jeff Starr’s BBQ Pro firewall plugin to block the bot. My Koko Analytics stats quickly returned to normal. I reported the issue to Koko Analytics on GitHub, so I hope the relevant IP addresses are added to the do not count list if it turns out that my diagnosis was correct. (In any event, one of my former visitors, PoorlyConfiguredWebCrawler, was much better behaved than SBInstitutionsBot.)

I came across Gautam krishna R’s blog-post-workflow repository on GitHub last night (being January 2, 2025). In short, it is a GitHub workflow for fetching RSS feeds and adding them to a GitHub profile README.md file. I created a profile repository (I had been meaning to for a while) and added three feeds: My ATOM feeds for this site and The New Leaf Journal and my Buttondown newsletter feed. Everything worked, but symbols in headlines for this feed and New Leaf Journal were being rendered oddly. I tried switching both WordPress feeds from ATOM to RSS. Now everything works perfectly. It is possible that I could have fixed the formatting using the available configuration options, but for this purpose (for mosy purposes, really), there is no difference between the WordPress RSS and ATOM feeds. You can see my GitHub profile with the feeds here.

I have a librebooted Lenovo T400 laptop which I picked up on Ebay a few years ago. I went to turn it on for the first time in a few weeks and, to my great disappointment, the screen did not turn on. I did some research and determined that the culprit could be the RAM. The laptop came to me with a spinning hard drive and 4 GB of RAM (2×2). I replaced the hard drive with a solid state drive and doubled the RAM to 8 GB (4×4). The laptop’s screen powered on when I removed one of the new RAM sticks. I got rid of the broken RAM and re-inserted one of the original 2 GB sticks of RAM (so we now have 6 GB total) while waiting for a new order of two 4 GB sticks. I also ordered new case screws since I have a few missing screws and two of the screws that were holding the palm rest seem to not fit correctly. At least it works, I suppose.

Replied to Fixing Computer With Punch by Nicholas A. FerrellNicholas A. Ferrell
I built my current desktop computer back in August 2020. One of the benefits of building your own computer is that you can easily fix it when you have a hardware issue. For example, one of the top fans on my case is becoming a bit off-kilter. Once in a while (maybe once every 30-40 start-ups), it wi...

I had to buy case-fans for my current computer, which I built back in August 2020. I have had issues with the fans rotating askew and making an unpleasant noise. I had already replaced two before one of my replacement fans started to go. In February, I fixed the replacement fan by punching the top of my computer case. Unfortunately, the punch solution became unreliable on the morning of October 26, 2024. Having work to do, I unplugged the offending fan. I think I can harvest case fans from my previous desktop PC, which I built in 2011.