Aside from being a cyclical hobbyist I don’t blog as much as I potentially could because I end up posting something on Fedi and repeating myself feels weird unless it’s something completely bonkers that I want to capture for posterity. Last week I thought about writing an application that did just that and link it to this here blog. But the last few days I’ve been preoccupied with littleFedi.

Converting threaded posts to blog proposal

Based on my incessant posts it’s clear that I’m a fan of littleFedi and the static blog integration. Currently, it is possible to take an existing public post and mark it as a blog post and takes that existing post and all the interaction on it and creates a blog post from it (with the interactions as comments), brilliant.

Desired State

> The idea is that if you end up writing a series of posts and it becomes something that is more meaty and has some value for longevity it can be persisted by simply changing the post type to a blog, after the fact.

This is what I wrote when I first learned about this feature and the more I think about it the more it makes sense for me. The whole premise was that you start writing something and have interactions with others or have updates over time and now it is a “body of work”. How can that be made into a full-on blog post without the venerable copy-paste method. And again, from that original post > it’s cognitively easier to write a series of posts instead of sitting down to write a blog post.

Proposal

A threaded post is a known quantity in the Fedi world and littleFedi does a great job of showing threads. So when editing a post the threaded replies that are either nested replies OR replies to the top post from the original author can be considered for inclusion into the blog post. Making an assumption on which posts should be part of the blog is not possible since the author did not write the posts originally with intent for a blog post. This is a potential way this can be achieved but I can imagine how the implementation can be hairy and supported scenarios could be difficult to define and explain. Here’s a visual to illustrate the idea, I created this with the littleFedi UI and developer tools in Firefox

link to post shown: https://littleone.littlefedi.social/@shom/1ad99f9c-2c9a-47d2-80fa-04399dc477d5