# kill-the-newsletter I gave in and just created kill-the-newsletter RSS feeds on the official service for the few newletters I have that aren’t RSS-able. The cost of increasing my vps size was more than I was able to justify for just a few RSS feeds. Since setting it up it’s been working great and I have no complaints. As long as they keep it up and running, I should be good.

I was updating apps today on my phone and noticed this release version number on the Google Play Books app. So I checked out apkmirror and sure enough it’s been the same message since June of 2023. How little do you have to care about your products and users to not even take the time to tell the user what is changing? It would take all of 5 minutes to update with something relevant.

Just realized a major drawback with self-hosted WriteFreely; the inability to upload images. Clearly if it took me this long to notice, I don’t often have posts with images. Still this is unfortunate. My syncing sources from here then goes out to micro.digitallyadrift.com hosted on micro.blog. The out to the fediverse. I checked the WriteFreely site and it looks like they’ve had it as a “wishlist” feature multiple years. The ticket is still unassigned so I’m not optimistic it will get added any time soon.

I’m on to figuring out the last piece of my self- hosted RSS to read later setup. I need to get a solution in place for handling email newsletters. Kill-the-newsletter is what I’m going to try. It gives you unique email addresses that it converts into RSS feeds. They have their own managed option but I want to go fully self-hosted if possible. Unfortunately Yunohost doesn’t have kill-the-newsletter as an easy install option.

Just picked up two new books from the library last night and moved them over to my Currently Reading section for 2025. Broken Code: Inside Facebook and the Fight to Expose Its Harmful Secrets by Jeff Horwitz and One Dark Window by Rachel Gillig Read the first chapter of each and they both did a good job pulling me in so far. I’ll be interested to see which one gets more of my attention and finishes first.

I feel like this time of year is always a bit of a struggle. After the holidays and all the visiting and eating and events, it feels like all that’s left is an empty quiet. I feel like there’s usually a slow down in news (I mostly follow tech news and this is a down time outside of CES, usually) but this year nothing I follow has been untouched by the current political climate.

I have not been able to get Readeck configured as an OPDS option for KOReader on my e-reader. Not sure if it’s a permission issue or what. Unfortunately there’s not much feedback when trying to connect other than a simple error message. I guess I can try and set it up with another application that supports OPDS and is easier to set up than entering all details manually on my e-reader.

Linode and Yunohost have been great together so far. I’ve got a handful of services up and running and have completely moved my RSS –> read-it-later workflow. FreshRSS to manage feeds and read them when I’m on a computer. On mobile (Android) devices I’m able to connect ReadYou and Cappy Reader to FreshRSS. Both are solid options and I haven’t settled on one yet. For saving articles I want to take notes on or that are just longer reads I’m between Wallabag and Readeck.

Working on getting the Wrtiefreely CLI setup. It was pretty easy. Just install the go binary and authenticate with my server I’m trying to think through a good way to keep all my posts archived in a way that makes sense but is also under my control. With the CLI I will have the ability to write Markdown files and post them with a single command. This means I can create a git repo that will store and version everything and I can push that to a self hosted git repo manager like Gitea or Gitlab.

Testing a post from locally hosted (sort of) Writefreely instance.