I'm playing around with different ways of organizing writing and reading. This is about the 18th way I've tried doing it. Is this the right one? I thought so, urgently, when I set out to do it this way. I cleared the whole week to "work" on it. But I'm moving very slowly, because I have gotten really conservative about the WordLand codebase. And these changes scare me for some unknown reason.

I've tried out so many different ways, but it's really clean now, and stable. In the last set of big changes, to get the Markdown editing mode working, I did a lot of cleaning out of hacked-together bits to get the kind of interaction I wanted. Now it not only works exactly as I want, more or less, but the code is super clean. Much more so than Drummer or FeedLand, both of which are working basically flawlessly. So I know I'm at a very strong level of stability here, but I don't have it well enough modularized so that I can just drop a WordLand into another app as seamlessly as if it were actually one app. So I'm pulling the much-developed timeline code into the WordLand codebase. But not letting it change the WL codebase. Tiny very well documented hacks are allowed.

I'm also thinking about whether I will want to use Drummer to write Scripting News, because I now have all my other feeds in this app too. Scripting News isn't that special now. It used to be everything. But now I'm getting my different writing spaces integrated. That includes multiple WordPress sites, btw. I'm not planning on bringing any Masto or Bluesky feeds in, they are too freaking ugly and with character limits — ugh.

I'm going to release a new reader app, reader.scripting.com. It's a place you can go instead of scripting.com, which I guess will now become the legacy home page?