I've just updated my blog post: Make your own E-Mail server - Part 1 - FreeBSD, OpenSMTPD, Rspamd and Dovecot included
ownyourdata
About a year ago, a client I've worked with for over fifteen years informed me that some of their "less critical" servers would be migrated to $CLOUDPROVIDER. According to them, this provider would guarantee an efficient management panel, "more freedom for their devs", and lower costs. This didn't impact me financially but, on an ethical and personal level, I warned him about the potential problems. Yet they decided to move forward, aided by the arrival of $YOUNGDEV who "has worked with it, it's reliable, and everything works fine". Again, I warned them (where are the backups? A disaster recovery plan? etc.) but they insisted: $CLOUDPROVIDER is efficient and gives us everything.
I studied their plan and immediately understood that their "cost-cutting" strategy wouldn't work: I know their workloads, and the plan they chose was insufficient. Needless to say, a few days later they went down and had to make an "emergency" purchase of the next tier up. The cost? Higher than their previous server infrastructure.
I heard nothing more about these workloads for almost a year but my monitoring tools still were marking them down, from time to time. Then, I get a phone call this afternoon. $YOUNGDEV asks me for support. He doesn't explain, but I immediately understand it's one of those workloads. A serious problem, and they don't have a backup of the database. They don't have a test environment to run diagnostics. The DB is very large, and they don't know what to do. My predictions - not even my worst ones - had come true.
I was running between two appointments. I only remarked that this situation could have been avoided and that it's not something I manage or can manage, but I nonetheless suggested we sync up tomorrow morning. I'm not going to get my hands dirty, but still, $YOUNGDEV is in trouble, and I offered to take a look to suggest a strategy. I then asked for the access credentials to $CLOUDPROVIDER, considering that up until a year ago, I managed all of these workloads. He replied that he "doesn't know if he can give them to me" and that he "would have to ask his bosses". I pointed out that if he wants my help, I need something - I don't even know how $CLOUDPROVIDER grants access to data (or if it does) - how can I give him advice?
It's 18:30 and I have received nothing. Tomorrow morning, if the phone rings, I will answer, but at this point, I won't do anything. I prefer, albeit reluctantly, to completely end the relationship with this client.
If this is the price of dignity and respect, I'll gladly pay it.
WordPress on FreeBSD with BastilleBSD: A Secure Alternative to Linux/Docker
Tired of the Linux/Docker “monoculture” for WordPress? This article guides you step-by-step through the secure installation of WordPress on FreeBSD using @BastilleBSD
Discover how jail separation, performance, and the versatility of ZFS offer a more robust and easily manageable environment, far from common vulnerabilities often linked to poorly maintained plugins. Get ready to make your site more secure and reliable.
#BSDJournal #FreeBSD #RunBSD #Wordpress #OwnYourData #Hosting #IT #SysAdmin
Edited 102d ago
Ever heard of vibe coding?
It’s when the code looks fine, tests pass, vibes are good - so it goes to production. Even if it’s wide open to SQL injection.
I’ve seen it happen.
AI wrote it. Devs trusted it. Management loved it.
Nobody understood it.
We’re trading skill for speed.
And that’s how we lose our freedom.
Vibe Coding Will Rob Us of Our Freedom: https://it-notes.dragas.net/2025/06/05/vibe-coding-will-rob-us-of-our-freedom/
EDIT: Given the trends and the comments, I wrote something off the cuff about it: https://my-notes.dragas.net/2025/06/05/when-we-become-cheerleaders-for-our-own-demise/
#ITNotes #ai #coding #data #ownyourdata #programming #IT #SysAdmin
Edited 148d ago
Make Your Own Internet Presence with NetBSD and a 1 euro VPS – Part 1: Your Blog
I've just updated the blog post: Increasing or Modifying Character Limits and Poll Options in Mastodon 4.3 and 4.4
https://it-notes.dragas.net/2024/10/09/2024-modifying-limits-in-mastodon-4-3/
I think it's time to write an #introduction for this account as well!
I'm Stefano Marinelli, Barista of the illumos Cafe and the BSD Cafe. I'm a technology and open source enthusiast, a strong advocate for #OwnYourData, and against computer monoculture, even when it comes to open source solutions.
I've been active in the #Fediverse for years and am a firm believer in it. I decided to found this Cafe to bring the positive spirit of the BSD Cafe to curious and passionate users of #illumos based operating systems (#OmniOS, #SmartOS, #Tribblix, #OpenIndiana, etc.).
I'll mainly use this account for content related to this instance and illumos-based operating systems, while my account at the BSD Cafe - @stefano - remains my primary one.
For more information about the illumos Cafe, you can read the introductory post here: https://it-notes.dragas.net/2025/08/18/introducing-the-illumos-cafe/
Fortunately, @voron 's site on snac themes still has this screenshot, which I'm happy to share.
This response from the author of snac motivated me to continue, study, and appreciate this fantastic software for the Fediverse.
Snac is an example of true internet democracy: it runs everywhere and allows anyone to have their own autonomous, personal space in the Fediverse.
"Don't despair or quit", says an author who cares. And the Fediverse cares about them.
For today's #ThankYouTuesday, I want to thank grunfink - @grunfink - for the excellent work they do, quietly and with passion. I suggest that if you think snac is a good idea and you have the means, you offer them at least a coffee.
Edited 66d ago
Another small victory today.
A salesperson had almost convinced a client to move their email from 365 to Google because "they hold all the cards now". I stepped in and suggested they keep their email on servers that they control instead. The salesperson almost mocked me, treating me like a "nerd" who doesn't understand how the world works.
I was happy to be a nerd, if necessary, to explain the pros and cons of the solution to the client.
The result? The salesperson was politely thanked and "sent home", and I'm now evaluating some details of the new mail server, which, by the client's choice, will be based on OpenBSD.
Because people need explanations, not brochures.