Stefano on littleFedi
It's me, Stefano, the BSD and illumos Cafe Barista - aka @stefano@bsd.cafe and @stefano@illumos.cafe
I'm testing something cool - #littleFedi !
This instance is efficiently running on a Raspberry PI Zero W, powered by #NetBSD.
I'll post general stuff - for more littleFedi news and updates, follow my other profile: @stefano@littleone.littlefedi.social
Let's go!
The weekend is almost over.
Someone should plan a serious and accurate study about the time compression that happens during the weekend.
@SecondChanceLemon@rebel.ar in the last few days, some more branches have been integrated and we're testing them.
The team did a great job, but lacked some coordination. Now things are improving.
@lorenzo@snac.bobadin.icu I think I found and fixed the issue. It should be working now (with new posts)
This is the mobile web interface of #littleFedi. It can also be installed as a PWA, with push notifications.
@EnigmaRotor@bsd.cafe @@stefano@rpi0w.stefanomarinelli.it yes, there’s definitely something that recently broke the picture attach. I’ll check tomorrow. Thank you!
Waiting for the pizza…
Before making this public, it'll probably be wise to make a test instance with more users. I'll think if this will be a BSD Cafe instance or not.
@blint@tutter.org currently not. the posted media will appear at the beginning (or end, still unsure which is the best approach) of the post. It would be a sort of quirk to implement it in the middle but still...maybe I can use some sort of custom shortcode like [1] for the first photo, etc and make sure it will be removed by the fediverse post, keeping only the photos... thinking...
@blint@tutter.org thanks. the idea is: it's not BSSG, it's not Wordpress, it's just another way to keep and distribute contents.
The Blog Option in littleFedi
littleFedi, like many social platforms, had both a strength and a limit. Posts, by their nature, are ephemeral. They get published, federated (unless local-only, which littleFedi handles) and then, over time, lost. Partly through self-deletion, partly through their normal blending in with the thousands of other posts that pile up over time. Sometimes, though, we want something to stay. And not just stay as a social post, but as an actual blog. A bit like with BSSG, I had thought it would be convenient to have a minimal system. Not to compete with WordPress or other solutions, but to have a small blog, integrated into littleFedi, that would produce and serve a blog updated every now and then, whenever the person writing felt like doing it.
And that's why the blog option was born.
The idea is simple: when you write a post, from the web UI or from the CLI, there's a checkbox, "blog post". If you check it, that post stops being just a status that will scroll past and disappear. littleFedi renders it into a real static site. No JavaScript, just HTML and CSS, an Atom feed, tag pages, a chronological archive. Nothing exotic, nothing that needs maintenance five years from now.
The blog isn't a parallel system you have to feed separately. It's not an export, not an import, not a bridge to some other CMS. The post you wrote is the blog post. Same database, same act of writing, still boostable, still repliable, still part of the conversation on the fediverse side. The blog is just a second representation of the same content, generated automatically. Every time you create, edit, or delete a blog post, the whole static site for your account gets rebuilt from scratch, and the new version replaces the old one atomically, so nobody ever lands on a half-built page. If the build fails, the previous version stays in place. Simple, but it has to work reliably, or the whole idea is pointless.
That's the core of it: two representations of the same post. As a status, it lives in the fediverse, interactive, part of the conversation, subject to replies and boosts like anything else. As a static page, it lives on the web, durable, indexable, with a permalink, something an RSS reader can hold onto. You don't have to decide in advance which posts deserve to last. You write normally, and if something turns out to be worth keeping, you flag it, and it gets its own page.
One detail I cared about while thinking this through: the generated site has to be self-contained. When littleFedi builds it, media gets copied or hard-linked into the generated directory - images, audio, video. If it's stored on S3, it keeps its public URL directly. Either way, the point is that the site on disk doesn't depend on the instance staying up. If the server goes down tomorrow, the blog files are still a complete, working website. That wasn't an afterthought, it was one of the requirements from the start.
Not every account gets a blog, and that's intentional. The instance admin has to enable the feature globally ([blog] enabled = true), and then grant it per account. It's not meant to be a CMS, and I didn't want it to become one. Blog posts can't be replies, can't be boosts, have to be public and top-level. These are constraints, not missing features: the blog is for your own writing, not for threads or reshared content.
There's no JavaScript anywhere in the generated site. That was deliberate too. It loads fast, it works offline if you cache it, and it will still render correctly in ten years without anyone having to update a dependency.
In the end, the blog option doesn't ask you to choose between writing socially and writing something permanent. You keep writing the way you always do, on littleFedi, and if a post is worth keeping, you check a box. No separate platform, no migration, no vendor lock-in. Just your own posts, some of them rendered into a small static site you can host anywhere, built out of something that already existed on the open web.
Remember: all this is being currently served by a Raspberry PI Zero W powered by NetBSD
Here's the result: https://rpi0w.stefanomarinelli.it/@stefano/blog/691cb62e-e7a1-434b-ba65-d059ee58ac41/
#littleFedi #SSG #BSSG #OwnYourData #Blogging #Fediverse #NetBSD