c.im is one of the many independent Mastodon servers you can use to participate in the fediverse.
C.IM is a general, mainly English-speaking Mastodon instance.

Server stats:

2.8K
active users

#runbsd

30 posts24 participants7 posts today

Now that it's official, I can announce it - although I may have dropped a few hints earlier! 😉

My talk "Why (and how) we’re migrating many of our servers from Linux to the BSDs" has been accepted, and I’ll be honored to present it in June at BSDCan in Ottawa.

The joy of meeting BSD friends in person again (and those I haven’t had the chance to meet live yet) will be immense, and the honor of sharing my story in Canada is truly beyond measure, especially considering the level of other talks and all the people attending.

Of course, I’ll be bringing various BSD Cafe gadgets with me!

For more information, here’s @mwl 's post with further details: blog.bsdcan.org/2025/03/18/bsd

blog.bsdcan.orgBSDCan 2025 Talks, Tutorials, and Registration – BSDCan Operations Team
#BSDCan#RunBSD#BSD

Mastodon will no longer support Redis Namespaces. The reasons are fully valid. Redis (or, more specifically, Valkey or KeyDB) is lightweight software that is easy to install/manage, so separation is always a good thing.
However, I read that many admins will face problems because they use Redis "in the cloud" and, therefore, have a single instance. Unfortunately, this is also a side effect of the "cloud," meaning the loss of control over your own software.

On FreeBSD, a thin jail with "Redis" takes up very little space and resources.

#OwnYourData – in the long run – always pays off.

github.com/mastodon/mastodon/d

Background Mastodon has supported using a dedicated namespace for keys in redis for a long time. The idea was that several applications (or instances of Mastodon) could share a single redis databas...
GitHubRetiring Redis Namespaces · mastodon mastodon · Discussion #34198Background Mastodon has supported using a dedicated namespace for keys in redis for a long time. The idea was that several applications (or instances of Mastodon) could share a single redis databas...

Report of the day, 19:30:

I’ve finished preparing the talk for Friday. Unfortunately, it’s not as I would have liked: the 25+5-minute limit is extremely restrictive, and talking about the BSDs in such a short time means having to skip over some fundamental points. Specifically, I will need to reduce the emphasis on the initial part, the less technical and more “motivational” section. I would have needed at least 40 minutes. 25 is really too little for a talk worthy of the name.

On the plus side, in the next few days, I will have to set up a new, quite interesting setup based on the BSDs. I’m considering using both FreeBSD and OpenBSD – the power of jails, the security of OpenBSD as an endpoint – unfortunately, I can’t provide many details as I’ve been asked to keep it confidential. Still, it will be very interesting for me to implement.

I’ve also modified several reverse proxies, switching from nginx to haproxy – I’ve integrated Prometheus and Grafana as well, and the ability to impose granular limits has improved the management of traffic spikes for FediMeteo. I’m really satisfied with the results.

Replied in thread

@mms with complete disregard of any Ubuntu/rutils drama ( about which I am completely unaware of and utterly uninterested in ), my personal attitude towards the #BSD license hasn't changed a bit, neither as a #RUNBSD user nor as a lawyer for, at least, the last 20+ years.

Hope that helps! 🤗

If anyone's interested here is the graph for CPU temperature when my new #OPNsense N100 router was running in the homelab cabinet rack vs when I just put a simple USB desk fan beside it to blow out the heat. A roughly 15C drop so the results will be much better hopefully when I get the proper cooling fans for the cabinet. PS The drop to zero is where I powered it off whilst tidying some other cables near by.
#HomeLab #RunBSD #FreeBSD