It's a wrap! The BSD-NL Conference - Early 2025 was a blast! 
A huge thank you to all the amazing speakers, (Kristof and Benedict!), attendees, and sponsors who made this event possible! 
Check out the videos of the talks here: https://exquisite.tube/c/bsdnlconference/videos
Visit the website for more info and the next edition: https://bsdnl.nl
See you at the next one!
T-6 days until BSD-NL Full Day Event - Early 2025
Sponsor Spotlight
We can not do this without our wonderful sponsors!
LAYLO
https://laylo.nl/
2025-04-12 / April 12th 2025
10:00-23:00 CET
Brouwerij Maximus (Utrecht) https://bsdnl.nl
T-7 days until BSD-NL Full Day Event - Early 2025
Sponsor Spotlight
We can not do this without our wonderful sponsors!
OpenBSD Amsterdam
https://openbsd.amsterdam/
2025-04-12 / April 12th 2025 10:00-23:00 CET Brouwerij Maximus (Utrecht) https://bsdnl.nl
The last episode of the #BSDNow podcast is talking about #FediMeteo
i'm hoping #RunBSD is already someone's rap/band name
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.
#Poll: are you "dog-fooding" #BSD?
Unlike previous polls (
) I have tried really hard to make sure the options make sense. Select the lowest item in the list that is true for you:
Of the ten options, the first four are for those that don't use BSD regularly (let's say at least once per week).
The fifth option ("VPN/server") is for someone who uses BSD on a server they manage, but don't have physical access to.
The sixth ("at work") through eighth ("secondary laptop/desktop") is for those who regularly use some variant of BSD, but not as a primary daily driver.
The ninth and tenth options are for "dog-fooding"
Oh, right, and I'm sorry, but it really must need be said: MacOS, iOS, and other Apple products do not count. Sorry again. I will count any FOSS BSD-like OSes like #OpenIndiana, though.
I will also count retro commercial Unixes, if you're actually daily-driving them. ;)
@VeilidNetwork Has Arrived!
The Internet was supposed to be a place of freedom and connection — not a marketplace for your personal data. Veilid is here to change that.
In a world where privacy feels like a luxury, Veilid brings hope. It’s a platform built to empower everyone with private, distributed applications that don’t trade your information for profit.
What makes Veilid different?
True privacy: No tracking. No data collection.
No hidden agendas: Built with passion, not profit.
An official CULT OF THE DEAD COW projekt.
Veilid isn’t just technology — it’s a movement to take back control of how we connect online. No compromises, no surveillance. Just freedom.
Artwork by @Banshee
When I founded BSD Cafe, I did it because I knew the community around BSD is amazing. More like a family than just a community. And every day I get confirmation of that.
I can finally, officially confirm that the talk "Why Choose to Use the BSDs in 2025" has been accepted and is scheduled for the next OSDay 2025, which will take place on 21/03/2025 in Florence, Italy.
There was a vote on GitHub, and this talk, by a narrow margin, received the most votes overall. Another testament to how the BSD family moves as one.
It is an honor to receive all these votes and to present, in a brief 25-minute talk + 5 minutes for questions, our beloved BSDs. I will try my best not to disappoint you, but for now, let me say a huge: THANK YOU!
wow, that was quick - more than 30 instances already connected to my relay in just such a short time :) Let's be federated and help even smaller #instances to distribute their content & posts!
You can find more information at:
https://fedi-relay.gyptazy.com
The instance is reachable on IPv4 and IPv6.
Calling all #FreeBSD folks
Having troubles keeping IPv6 operational on a #Netcup VPS with FreeBSD. Seems to be a known issue with a Netcup and FreeBSD combo.
Any advise appreciated.
https://forums.freebsd.org/threads/netcup-ipv6-intermittant.96489/
#RunBSD
.:: PWNAG3 CHARTZ ::.
T34M DeGU (aka APT 77 aka Fluffy Rodent):
jail by chewing a hole in its baserootMe: “~i CaN mAkE cOmPuTeR pRiNt On BoTh sIdEs oF pApEr~”
UPDATE: I haven't seen Recall in action there. I was just asking the doctor how they'll deal with it.
This morning, I went to the doctor for a scheduled appointment. While she was looking at the results of blood tests from two years ago on the screen (and suggested repeating them for a follow-up), I realized she was using Windows 11. A detail came to mind. The doctor is extremely polite and friendly, so I asked her, "How do you handle the feature called Recall?" The doctor was taken aback and had no idea what I was talking about. I was about to drop the conversation, but she, being a serious professional, immediately called the technicians who manage their PCs to ask for clarification. They downplayed it, saying it's not an issue and that it's a feature "on all PCs, so we can't do anything about it." She started to express that she didn’t like it and wanted it deactivated. No luck: they won’t proceed because, according to them, even deactivating it is "a hack that could compromise future updates." She’s furious and will talk to her colleagues and the decision-makers. She wants secure systems because "there’s patient data involved."
In reality, patient data is stored on servers (which I haven't investigated), but everything that appears on the screen is, in my opinion, at risk.
I’ve offered to help them find a solution—because, if I'm right, all they need is LibreOffice and a browser. In that case, I’ll suggest one of the *BSD or Linux systems and do it for free.
I don’t want to make money off my doctor. I just want patient data to be (sufficiently) secure.
ssh-askpass bash script to a posix sh script ssh-askpass.sh.#!/usr/bin/env bashIn sh it is:
# Remember to export SSH_ASKPASS=~/.local/bin/ssh-askpass in your .bashrc
RESULT=$(pinentry-curses --ttytype=xterm-color --lc-ctype=en_US.UTF8 --ttyname=/dev/tty <<END | grep -E '^(D|ERR)'
SETDESC Enter your SSH password:
SETPROMPT
GETPIN
END
)
if [ "$RESULT" == "ERR 111 canceled" ]; then
exit 255
else
echo ${RESULT:2:${#RESULT}-2}
fi
#!/bin/shIt might not be perfect but it works for me. #RunBSD #FreeBSD #Posix
# Remember to export SSH_ASKPASS=~/.local/bin/ssh-askpass.sh
RESULT=$(pinentry-curses --ttytype=xterm-color --lc-ctype=en_US.UTF8 --ttyname=/dev/tty <<END | grep -E '^(D|ERR)'
SETDESC Enter your SSH password:
SETPROMPT
GETPIN
END
)
if [ "$RESULT" = "ERR 111 canceled" ]; then
exit 255
else
length=$(printf "%s" "$RESULT" | wc -c)
length=$((length))
echo "$RESULT" : '..' | cut -c 3-"$length"
fi