For the first time, littleFedi will be shown publicly

And I have to say, this makes me very happy. :)

A pre-release build will be running on a Raspberry Pi Zero 2 W at Berlin FediDay, where people will be able to see it, try it, play with it, and probably abuse it a little too.

Unfortunately I won't be there in person, because I'll be at EuroBSDCon that same weekend.

But really, what better place than FediDay for the first public appearance of littleFedi?

A huge thanks to @vortex@tldr.nettime.org - Adam - for taking this on, building the demo, testing it independently, and agreeing to respect the temporary source embargo while we complete the last checks before the public release.

I'm especially curious to see how littleFedi behaves once it's in the hands of people who didn't build it.

This is exactly the kind of test I was hoping for.

More details about the presentation:

https://ctalx.c-base.org/fediday-2026/talk/review/AJNLVMPYRSVX3JDHDHYSEZZNSP9KQSYH

#littleFedi #littleOne #OwnYourData #Fediverse

Grateful for the Static Blog page ability which LittleFedi includes as an option for Instance Admins to offer their members :

https://littlefedi.org/blogs.html#enable

Borrowing / Extending that ability just a bit brings me to my Feature Request for LittleFedi.

Akin to how LittleFedi can allow Static Blog pages to be generated from regular posts,

And then appear in its own namespace, using mine as an example :

https://littleone.littlefedi.social/@himysyed/blog

My request is to likewise offer the ability for Instance Admins to allow optional Static "Photoblog" Page for members

ergo :

https://littleone.littlefedi.social/@himysyed/photoblog

This is distinct from the "media" button linked from LittleFedi profile pages, as that is a catch-all visual listing.

https://littlefedi.org/blogs.html#contents

On my profile page currently we can see the "Visit blog" button.

My Feature Request includes asking for a "Visit photoblog" button to appear on one's profile, using the same logic as was used in the Static Blog option.

LittleFedi "Photoblog" themes are something that can be created and uploaded via the existing CSS ability, and that would fall upon us, the LittleFedi users, to create and share.

https://littlefedi.org/blogs.html#appearance

I'll stop here, because my next feature suggestion might build upon this, if it's reasonable.

...oh right, the above photograph, was something I wanted to remember, because seeing someone changing a car tire nowadays is unusual, at least to me. Nothing special about this scene. It's a photo of a moment from my Friday afternoon.

And thus something I wanted to "Photoblog".

| #LittleFediPhotoBlog #Photoblog #LittleFedi

@himysyed And in conclusion, this is my third and final post capping my first LittleFedi Thread.

My intention was to create a thread,

Then circle back to the First Post in this thread,

Edit that first post and checkmark the "[_] Blog post" radio box,

So it would appear in my LittleFedi Static Blog page :

https://littleone.littlefedi.social/@himysyed/blog

As per https://littlefedi.org/blogs.html

Only the first post atop / beginning of a Thread can also appear on the Static Blog.

Any subsequent "replies", even if it is from myself, cannot become Static Blog Post.

All right, let's see what happens....

| #LittleFediThread #LittleFediBlogPost #LittleFedi

The social web vs the software web

I launched ChatGPT for the first time in a long time because I now have access to the new version. One new thing I see is that they are popping up suggestions about things you can do in realtime, like smart queries in a feed reader, which as far as I know is still uncharted territory. Like this: “let me know when the Mets have a three-game winning streak.”

That’s the kind of thing TBL dreamed about in his semantic web plan, but he wrote the spec before writing software, and that doesn’t work. His invention, the web, which came before was a perfectly timed, perfectly simple approach to sharing ideas on the internet. It worked because he created a product that worked, and made every piece completely replaceable. It came at a time when stagnation in tech made something necessary, or the whole thing was going to fall apart, and so close to so much incredible potential. Just like the moment we’re in now with AI.

Rules for Standards Makers says a lot about this.

The value of disruption is that it undoes stagnation.

Anyone who has the same software plan today that they had a year ago is going to find themselves isolated. Even WordPress, though it is open source, is a silo that imho in the future will not work. The main selling point of AT Proto is that it is a safe haven for developers who nuzzle up, another word for that is silo.

The siloers are probably scrambling to find a way for the AI to run inside their world, mistake — instead they should be trying to be fully relevant to applications in the AI world. Like Slack, for example, and Claude Tag. It’s now built in. Has to be replaceable too. Small pieces loosely joined. That’s what you have to be imho to have a role in the future of tech.

If your advantage is your silo, undo that as quickly as possible. Become the default version of whatever it was meant to be wrt the web. Both Bluesky and WordPress find themselves in the same quagmire. Probably a lot of others do, but this is the area I study. (I just am very familiar with the products of both companies, for some reason.)

This is the intuition we all had, coming to fruition. Evolution is something we haven’t seen much of in the software world since 2006 or so. Incredible stagnation because of the dominance of the social web. We lost the software web. All the focus was on personalities, celebrity — hype and 99.999% bullshit. It was a 20 year period where all that happened was scaling.

Lots more to say about this. The world we lived in ran on hype, now guess what — having lived through a few big evolutionary changes in tech is a huge advantage vs the people who have never been part of one, and I think most of the people in tech today qualify.

A story my Dad told me during the single digit years of childhood...

He read in the newspaper about a man who lived in Las Vegas who made his livelihood via gambling every day.

He set down rules for himself, had the self-discipline to never change those rules.

The man would visit the Casino every day, and begin with a budget of $20.00.

Maximum.

Whenever he lost that initial $20.00, then that was it for the day.

He left the casino and enjoyed the rest of his day.

Other times, his initial "Seed Money" of $20.00, via subsequent betting, would grow.

Whenever that Total Daily Winnings reached a certain dollar amount, I can't recall whatever that amount was, this man would cash out and leave the Casino.

No matter how much of a "roll" he was on, or sudden big bet winnings, once he reached his daily target number, or surpassed it, he quit for the day.

He wasn't greedy, nor needy.

He treated this behaviour like a regular Day Job one would go to, work at, then leave and go home.

The man had a house, wife, kid, a regular life, in Las Vegas.

What does this have to do #littleFedi cf. Mastodon?

My first year or so being on my original Mastodon Instance, I didn't realize how many hours I was spending there everyday, I often lost track of that time.

I consider that an "anti-pattern" I wish to avoid.

I wasn't spending "money" as one does at a Casino, I was spending time.

The direction of LittleFedi provides for what I consider "patterns" which I wish to enjoin in.

Accessing the Fediverse via this LittlefFedi approach does not feel like a Casino.

And with that, I going outside to enjoy this Sunny September Saturday around Toronto.

@fasnix Yes. It is that good.

A few disjointed points to suggest why I say so...

My experience began with using MediaWiki for a specific project about 18 years ago now.

I concluded it remained tailor-made for Wikipedia's use case, and not a general purpose wiki software product. It's bloated and complicated for simple ideas. And harder still to set up for a basic internet person like me.

I migrated, meaning I manually cut and pasted all the pages' writing and images on my initial MediaWiki powered site, into different wiki software products until I tried DokuWiki, ...twice.

The first time I considered DokuWiki, I did not recognize my error in skipping over it, I judged it wrong.

A few years later, I returned to DokuWiki and found I didn't research smart enough the first time, and what I wanted in a wiki software had always been there, once I explored the optional extensions available.

It's a simple php set of files that fits into one folder and can be FTP'd into, and set up and maintenance was within my non-programmer / non-technical person abilities.

When I first encountered Stefano's "BSD Cafe" world building, I smiled as I immediately found bsd.cafe goes to wiki.bsd.cafe,

Which is a DokuWiki powered site . . . . ( ! )

Per Stefano's judgement, as DokuWiki is his tool of choice for an entry point into the BSD Cafe world, then I found it reassuring.

It suggested to me, his internet infrastructure worldview is closer to the things I would like to be using and be involved with.

Returning to my initial observation,

Mastodon feels "heavy", bloated, in its requirements to set up, and in its architecture. And its initial purpose was as a twitter alternative.

The first two years as a simple "user" on a mastodon instance, any number of things kept bothering me about being on there, until a I gradually recognized it was the same "feeling" I had all those years ago when I was entering and updating information in my initial MediaWiki powered site.

It wasn't fun anymore.

DokuWiki is simple, again, if feels like "fun", if and when you want it to.

Likewise, LittleFedi.

#Introduction

My name is HiMY (Pronounced Him-Me), from Toronto, Ontario, Canada.

I have been following all things #LittleFedi ever since @stefano 's replies about it began appearing in #snac2 related conversations.

Found myself reflecting on the LittleOne Community and LittleFedi possibilities often when I've been going about my day, away from the computer.

I'm usually that person in the room who looks at things from a different point of view and asks that question which seems obvious in hindsight, yet difficult to spot before it being raised.

For the past month, I keep seeing possibilities here, and the only way to ask such questions about them, was to finally join and experience LittleFedi for myself, to test my assumptions instead of remaining an outside observer.

Away from the computer, you may find me making #Labyrinths in and around my hometown of Toronto.