Stefano Marinelli - littleFedi

@stefano Created:

Barista at BSD Cafe and illumos Cafe - @stefano@bsd.cafe / @stefano@illumos.cafe
Spreading weather forecasts all over the Fediverse via FediMeteo - @admin@fedimeteo.com

Testing littleFedi here on littleOne, its first instance open to outside users. Small ActivityPub server, single Go binary, still in active development.

I will also use this account to provide information about this instance and the development of littleFedi.

#littleFedi #Fediverse #OwnYourData

Visit blog
RSS
Replying to @sturai

@sturai it seems you're clearly missing the entire right bar. this is strange. I'll perform some tests. thanks!

Replying to @stefano
Screenshot in Zephyr theme
Screenshot in Zephyr theme

@stefano @sturai I just tried the Zephyr and it appears on the right (see screenshot), when using Safari. Could you please test with another browser? just to understand if it's a problem only with brave.

Replying to @sturai

@sturai but this is clearly a bug, so thank you for the head up!

Replying to @sturai

@sturai hi! is going back to another theme bringing it back?

Replying to @joany

@joany I can confirm it works perfectly on a zone (tested it personally), even if it will use the slower compatibility sqlite driver (unless you use PostgreSQL, which is native).

Replying to @shom

@shom @fasnix @madamada Built-in backups of the database, the configuration and, optionally, local owned media, with a manifest and a restore command.

You can fully export all your contents (including posts) and re-import them into another littleFedi instance. It'll be another account with another handle, but you won't lose any of your contents. Your data stays yours.

#OwnYourData

I've received quite a few questions about the use of AI in and around #littleFedi.

So, after discussing it within the team, we've decided to update the FAQ and make our position clear.

It probably won't come as much of a surprise to those who already know me and the projects I work on. But littleFedi is reaching people who don't know me, or us, and I think it's fair to explain where we stand rather than assume they already know.

The short version: littleFedi doesn't use AI. No ranking models, no recommendation engines, no language models deciding what you see.

The longer answer, including how I approach LLMs and code contributions, is now in the FAQ:

https://littlefedi.org/faq.html

Replying to @shom

@shom @fasnix @madamada the backup procedure is already backing up the blogs, so we’re covered. And yes, that’s a good approach. I’ll try to put it into the todo list. Thanks!

Replying to @andypiper

@andypiper I’ll check. Thank you for the feedback!

Replying to @xenotar
Replying to @adam@toots.adamu.jp

@adam@toots.adamu.jp Of course! Your question is completely valid and makes total sense. Since I'm not the only person involved, I have the thankless task of having to explain and convince the decision-makers, whether I agree or not.

Replying to @adam@toots.adamu.jp

@adam@toots.adamu.jp thanks for the suggestion! The team was more oriented towards a positive approach, which is the same I usually have at BSD Cafe. Pro, not against. So saying they’re enjoying programming is a positive message. Saying “no AI here” is something different, even if the message itself is clearer. I’ll try to talk to them.

Replying to @adam@toots.adamu.jp

@adam@toots.adamu.jp the about page says:

In a period where it is fashionable to boast about the dozens of AI agents doing things on your behalf, we are the Little Computer People.
We are people who love doing things with our computer, who treat it as an instrument of creativity, of expression, of life. Of friendship, of play, of letting off steam, of sharing.

This is the message the team wants to send to the world. And I think it's self explanatory.

Replying to @stefano

@stefano @fasnix @shom @madamada another solution could be put the blog files into the s3 storage, too (if configured) and serve them just proxying the files.

Replying to @xenotar

@xenotar @fasnix @shom @madamada We're not planning to add mysql/mariadb as it will make the codebase larger and harder to maintain and we'd avoid it, at least for now.
We're planning a db switch procedure so you can switch from one to another in a native way.

Replying to @fasnix

@fasnix @shom @madamada I don't know 😃 Some local automated tests show that 100 users with sqlite are fine, as long as there's not too much concurrency in writing stuff into the DB. For the public server....I don't know as well. The limit will probably be the limit of the hardware I'll be using. There's something to be fixed: blog generation will only work on single process installations, not on clustered setups. I'll probably easily adapt it to build blogs only on one specific machine (the one doing the housekeeping). Still, the blogs will finish into the local file system, so this needs to be sorted, too. But this will come later.

Replying to @fasnix

@fasnix @shom @madamada this server will be permanent.
I'm planning to add a "public" server. I'm not sure if it will be this (using sqlite, we could hit some limits) or another one, using PostgreSQL, ready to scale.

But yes, this is our littleOne and will stay.

Replying to @fasnix

@fasnix no. You’d lose the quoted part. And this is a privacy feature, not a bug.

Replying to @fasnix

@fasnix No, you can convert any of your posts to blog posts whenever you want to. But you can't convert a boost into a blog post. Which sounds reasonable, I think.

Load older posts