fennell.dev is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
To the people who would like to contribute to postmarketOS but haven't, what is stopping you? Or, people who *have* contributed but stopped. (With the exception of just not having time or such)
I'd love to hear some feedback on how our contribution process could be streamlined.
TIL: systemd-modules-load.service, available e.g. on Debian trixie, which allows to load a set of kernel modules during (mid-)early boot, using textfiles in /etc/modules-load.d/.
Combined with:
```
[Unit]
Description=Hardening: disable late loading of kernel modules
Wants=network-pre.target
Before=network-pre.target
After=systemd-modules-load.service
Requires=systemd-modules-load.service
[Install]
WantedBy=multi-user.target
[Service]
Type=oneshot
RemainAfterExit=true
ExecStart=/usr/sbin/sysctl kernel.modules_disabled=1
```
I'm freezing the set of kernel modules loaded on my servers as defense-in-depth.
Trying to fix a device asking for proprietary firmware on my #Linux-based system, I `apt -y install firmware-linux-nonfree`. I didn't realize until too late it's a #Debian metapackage for “all the proprietary firmwares (not) fit to download”.
I previously curated a careful selection in /lib/firmware of only ones necessary for my hardware.
I'm left wondering how to clean up further? I generally want to *know* when a proprietary firmware ends up in use. I don't remember which ones are necessary.
A friend asked me about costs etc. in running my own Mastodon (glitch-soc) instance.
My reply might be useful more broadly:
Costs: I run mine on an Intel NUC, for which I paid about ~£200. But I ran for years on a Raspberry Pi, which was fine until my account got a bit big. It consumes some electricity, and I already have an Internet connection with IPv6 and a spare IPv4. So, incrementally, beyond the cost of the hardware, very little.
Time to set up: it took me about 30 minutes *but* I am already familiar with hardening a Linux server, and I build the basic infrastructure automatically. Honestly, this is the bit that would concern me the most, for someone planning on putting a box on the Internet. But it could also be a fun learning exercise.
Time to maintain: a few minutes a month. Upgrades are easy enough. Backups are automatic (because I have automated them).
🎙️ Next talk at #EmbeddedRecipes2026!
Pablo Correa Gomez takes the stage with an inspiring community-driven engineering story: "A Distributed Phone CI for postmarketOS".
📥 Slides: https://cfp.embedded-recipes.org/media/er2026/submissions/ZLSMQG/resources/pmOS_ER2026_kvJtwHO.pdf
▶️ Watch live: https://www.youtube.com/live/q4Y-G73pumY?si=VBi5-071scHk9Mb1
#EmbeddedRecipes2026 #EmbeddedLinux #postmarketOS #CI #Testing #OpenSource #Linux #Smartphones
@cwebber After cringing hard, seeing early #Unix Window Managers like twm and fvwm, it was such a breath of fresh air to see #WindowMaker. I rocked a WindowMaker desktop from about 1998 to about 2002, in #Debian #linux
If a casual chat about #Linux and #FOSS over a curry sounds fun, please come join us! Just reply to me by the end of 21 January so I know numbers for the booking.
Time: 24 Jan, 19:00
Address:
Kings Cross Tandoori
341 Gray’s Inn Road
WC1X 8PX
Hope to see you there, and any questions feel free to ask.