Local timeline

Replying to @stefano

@stefano @fasnix @shom @madamada I thought that because it moves away from the idea of ​​a minimalist server. My comment was just that—a comment that I now see was unnecessary.

Just testing out the visual editor; it’s simply fantastic because it makes it easy to create text with a wealth of formatting and emphasis options—a great addition to Littlefedi.

Weird bug, Ivory can’t connect to littlefedi with an error “client_name is required” 🤷🏼‍♂️

Albeit this is not Mastodon, but it seems to offer some Mastodon compatibility.

Replying to @stefano

@stefano I am reading this (obviously will take a while) and will eventually send you a full report.
Yell if you need/want a translation into something else

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.

"Why light-weight websites may one day save your life.

Imagine being in a situation where you have limited internet access: your internet is slow, or you're relying on a small data bundle, or you are stuck in the middle of nowhere with spotty coverage.

Now imagine that suddenly, you need help. Emergency medical information, food resource locations, shelter, assistance, anything.

Then, in your emergency state, you look up resources on the internet and find... a website that first requires you to load 500 MB of JavaScript, and lord knows what else.

Maybe she's born with it, maybe it's ReactJS. 💅🏻

(Post-publication addendum: 500 MB is an exaggeration even for React. But you catch my drift.)"

Further reading:
https://marijkeluttekes.dev/blog/articles/2026/01/21/why-light-weight-websites-may-one-day-save-your-life/

#MarijkeLuttekes #CSS #WebDev #Webdesign #SmallWeb

Day 2 of my vacation..
The lack of stress and repeted phone calls and emails is starting to show, all suppressed emotions of 12month grind is taking its toll..
It can be gruesome when the people around are glad that you jump the gun every time.
The unspoken, if a device blinks it must be under my care.
The false profecys about how great AI is, it just dumbs ppl down, its a tool. not a solution.
The few times ive check it out its been a mix of makeup variables and commanda to fix an issue.
To type this in window to get to the special properly box you need.

I know i type as a think, dazed and confused.

But all you fantastic ppl, take care. i mean it
I want to dream about cool tech things, not stupid tech

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 @stefano

@stefano @fasnix @shom @madamada Forgejo allows you to choose between SQLite (default), PostgreSQL, MariaDB, or MySQL. I don't know how laborious or complicated it is to implement this functionality.

Replying to @stefano

@stefano
If you add a public server, would you aim for it to accept an "unlimited" amount of users, or would you rather restrict it to, say, 100 / 500 / 1000 users?
(Where are the limits for sqlite?)

@shom @madamada

Replying to @madamada

@madamada
On the one hand, I understand your approach.
On the other hand: most fediverse services aren't like twitter at all, as they offer far richer functionalities.
So, a comparison to only twitter could end in:
"I never used twitter anyway, so the fediverse isn't for my liking."
I think it's necessary to show a broader view of what different fediverse services are capable of.

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 @shom

@shom
I agree, however, I hope this server will stay permanent, not just as a "test environment" :)

@stefano @madamada

Replying to @menel@snikket.de

@menel@snikket.de oh hi @menel@snikket.de! Yes I did, part of the reason to change was just to upskill and increase my knowledge. I already have some regret as it was insanely solid and never missed a beat, but Prosody is still sitting in it's proxmox container - it isn't being deleted and may go back to it once I've had my fun 😉

Replying to @drscream@fru.bar
Nigel
@nigel
Public en edited

@drscream@fru.bar @stefano@bsd.cafe mainly masochism I guess... 🤔
I have a solid Prosody server setup, has worked for years great, and in that time I also dabbled with ejabberd but never in any serious way. So I thought, how can I learn how to make this clearer in my head... I know, run in production!

The main reason really is that I have grand ideas of running a public server one day, and read @thomas@metalhead.club post on migrating trashserver.net from prosody to ejabberd back in the day - and a friend still uses his server, which seems solid. The invite system ties into this longer goal/dream/stupid idea.

So yeah, basically because I wanted to learn things. If someone was starting out, or even not just starting out but wanted their own server, I 100% recommend Prosody. Every time.

Replying to @nigel

It turns out I found a minor bug in the invite system 😅

But its working, and friend invited ☺️

Replying to @mavu@mastodon.social
Nigel
@nigel
Public en edited

@mavu@mastodon.social it treats it like a linked desktop client I believe. You still need it installed on a phone. I use it for work unfortunately, but on a separate work phone, and it means my xmpp clients can all access the same chats as well.

And my wife and kids use it also, so the family group chat is on whatsapp - and the slidge bridge means it is also on my personal phone and desktop pc without whatsapp being able to access those devices.

Load older posts