A while back I shared Kitchen Board here, a small self-hosted family organiser designed to feel like an old kitchen wall planner, running on yesterday’s hardware because we all have that knocking about.

I've been rather busy working on all the suggestions you put forward, and hopefully this is a half decent update for you.

The project is still built for one household, runs as a single Docker container, stores everything locally in SQLite, and does not require an account with me or any external service. This is purely for selfhosting.

Source: https://gitlab.com/g33kphr33k/kitchen-board
Docker: https://hub.docker.com/r/g33kphr33k/kitchenboard

The big additions since the last post are:

• Chores, with open, assigned, or rotating responsibility
• Optional points for completing chores - I was excited for this suggestion!
• Rewards that can be claimed with earned points - You set the rewards they can spend points on.
• Stats for household activity, points, shopping, and Time Since routines
• Time Since routines that can rotate between selected household members
• A full Meals week planner
• Mealie recipe importing - yes, it now imports correctly. However, it is still only a mild import and I definitely won't try to oust Mealie from your life.
• CSV meal importing for people without Mealie and who like spreadsheets
• Shopping Trip mode organised by supermarket aisle - You have to add your items to the correct aisles, so it’s a little more work for now. Go to Lists and you’ll see the aisle settings. This will be improved in later versions.
• Stock tracking with remembered locations, expiry dates, low-stock reordering, and safer shopping list integration
• Shopping Suggestions, including admin controls for hiding, correcting, merging, and restoring suggestions
• Spanish added to the household language picker, alongside British English, International English, German, French, and Italian - I may need some help here for natural translations.
• Notification controls by area, quiet hours, daily and hourly digests, and links that open the relevant page
• Better offline support for shopping lists and queued changes - PWA improvements.
• Phone quick-add for shopping items, events, notes, timers, and meal plans - Due to using my phone a lot for this.
• Improved tablet layouts, including landscape iPad Mini support - Yes, I give my almost-6yr-old the iPad to use to look at the Time Until and he will eventually be able to use it and understand the chores and rewards (he says, hoping).
• Optional TOTP multi-factor authentication with backup codes - Fixed, thank you u/LouisRed_
• Better support for older Android tablets and Amazon Fire devices - I'm keeping this Silk browser compatible.
• Lots of smaller fixes around recurring events, countdowns, sound playback, autocomplete, translations, and stale PWA caches.

There is a “Time Since” page for things like “Teas made for the wife”, changing the towels, watering plants, or taking the bins out. There is a “Time Until” page for birthdays, holidays, appointments, and the all-important “how many sleeps?” questions.

The visual style is still deliberately old-fashioned, with paper-like cards, handwritten headings, ruled dividers, and five built-in themes. It is intended to look at home on a kitchen tablet, while remaining usable from phones.

A few boundaries remain intentional and I don't plan on changing them:

• It is for one household, not a hosted multi-tenant service
• The calendar export is read-only ICS
• Meals are still a lightweight planner rather than a replacement for Mealie
• Language support is fairly basic - I will only update them if people submit them to me.

I use it every day with my own family, and it has become one of those projects that keeps expanding because somebody asks, “Could it also do this?” and, if I like the idea, yes, it will be added.

Screenshots and setup instructions are in the README:

https://gitlab.com/g33kphr33k/kitchen-board

Right, over to SelfHosted and those of you already using this - what did I break? What needs fixing? What needs improving (lots, I keep finding minor quirks between tablets and desktop to expect many incremental fixes and changes)? Finally, what did I get right and you are pleased with?

Sorry that this is another ramble post, it's just how my mind works.

Seatsurfing can be self-hosted for room and desk booking — and it solves the "who is sitting where" problem. What it did not solve is the physical side. Once people stopped sitting in fixed offices I kept walking into the wrong room looking for a colleague. The booking system knew where they were. The door did not.

I could not find a door sign to buy that ran on batteries without a licence, a hub, or a vendor cloud, so I built one. It is an e-paper display that wakes on a schedule, queries the Seatsurfing API directly over the LAN, draws who has the room, and switches itself off again. Tap it with a phone and it books the room on the spot; the NFC tap alone powers the chip that wakes the rest, so it works with the device completely off. That part picked up an honourable mention in the "Least Power" category of Hackaday's Green-Powered Challenge last year.

It does not deep-sleep between updates — a MOSFET disconnects the whole circuit from the battery and a real-time clock switches it back on, so in between there is no microcontroller running at all. The oldest unit has been on a wall for 15 months on one set of three AAA alkaline cells and is still going.

I already included a few more uses for the device - including home assistant and homematic. I am very much interested in more ideas!

Firmware, PCB and 3D-printable case are open source.

Hackaday project and logs

To find out whether there is enough interest, there is a pre-launch page on Crowd Supply.

I was super surprised to see Jellybox to see article on xda-developers - https://www.xda-developers.com/i-turned-jellyfin-into-the-spotify-alternative-ive-always-wanted-with-this-app/

I read them sometimes and was really surprised to see article about my app that I spent few years working on it. Anyway I just wanted to share it, since things like these happening once in a life time

For those who dont know what jellybox is - open source crossplatform native music client for jellyfin and emby and can do:

• Spotify-like playlists
• Full offline mode(it really works unlike other vibe coded apps)
• AppleCarplay app
• Browsing, lyrics, etc
• Full screen studio mode
• Airplay cast(DLNA and chrome cast to be added soon)
• A ton of small UX stuff like saving your playback position and resuming next time you start the app and so on.

Available on https://github.com/avdept/JellyBoxPlayer or links to stores here - https://jellybox.app

i am new to sh, iirc barely a week and a half, and yes this is an addiction, i wanna selfhost everything i can lol

the hardware i am using is a spare old decapitated laptop i had lying arround.

havent bought a domain yet so forgero and nextcloud arent setup properly

also writefreely and feishin's logos werent available on siso just chose random ones instead, i am gonna switch to dynacat as i have been advised to do so; very soon.

cant improve the hardware cause I currently don't wanna spend money T_T lol

https://preview.redd.it/9i9l7jo1ounh1.png?width=1199&format=png&auto=webp&s=4dbf7753f5690d15684338d3501879437df57f9d

https://preview.redd.it/pfur6it8ounh1.png?width=1340&format=png&auto=webp&s=3e93c845078edca9918a5fad219ae522a0b6c7cf

I have ~2TB of a daily radio show archived on my home NAS with thousands of episodes across messy nested folders with inconsistent filenames spanning 15+ years. Finding "that episode where they did the thing" meant remembering roughly what year it happened and digging.

So I built a pipeline that turns chaos into a searchable library:

How it works:

1. Inventory walks the NAS tree, every audio file into a SQLite files table
2. Rundown scrape pulls episode-by-episode text rundowns (fan-maintained episode guides exist for this show, decades deep) into a rundowns table
3. Date extraction parses air dates out of messy filenames and writes them back
4. Index FTS5 index over all rundown text
5. App one search page: type a phrase from the show, get the episode, joined to the actual audio file, hit play

So the search experience is: type "the segment where they argue about the cake" → the episode date → the rundown snippet → the audio starts playing. The join key is the air date: rundown date matches filename date matches audio file.

SQLite FTS5 is genuinely underrated for personal-scale search.

I recently set up a 3-node Kubernetes homelab on bare metal (on Dell OptiPlex) using Talos Linux, mainly to have a proper environment for learning, testing failures, networking, storage, GitOps, observability, and general Kubernetes experiments.

The setup uses three control-plane/etcd nodes with a shared Kubernetes API VIP, and I documented the full process from network planning and DHCP reservations to Talos installation, per-node configs, bootstrap, workload scheduling, and HA testing.

I’ve written the full guide with commands, screenshots, and the reasoning behind the setup:

Blog: https://blog.prateekjain.dev/building-a-3-node-highly-available-kubernetes-homelab-with-talos-linux-0372066fe49c?sk=4c66cf9181999f9db19ac3aacabcd8e8

If anyone is planning a similar homelab or has questions around Talos, the API VIP, etcd quorum, or the setup in general, happy to help.

Hello everyone, Brandon from NetBird.

NetBird 0.78 introduces Draft Mode in the Control Center. The Control Center is the network map that shows your peers, groups, policies, networks, and resources. Draft Mode makes it so you can use that map into an editor, so you can restructure access by dragging connections on a canvas, then review the exact API calls before anything is applied to your live network.

NetBird is an open source, WireGuard based zero trust networking platform that connects your machines into a private overlay network with identity based access control.

GitHub: https://github.com/netbirdio/netbird

Draft Mode

Start from an empty draft or from your current live view. Starting from the current view breaks your existing infrastructure out by group so you can edit what is already running.

• Drag connections between groups and resources to create access rules, like giving a dev group SSH to a specific host
• Add servers, agents, policies, groups, networks, and resources from the canvas
• Install a new peer directly from the draft using a single use setup key, then wire it up on the map
• Connecting a peer with no policy opens the policy creation window automatically, with port and protocol config
• Add routing peers and resources to your networks
• Switch policies between bi-directional and uni-directional inline
• Focus view isolates a single group and hides everything else, which matters once your map has more than a handful of overlapping policies

Docs: https://docs.netbird.io/manage/control-center/draft-mode

There has also been many other updates around performance and stability. You can see the release notes here: netbirdio/netbird and netbirdio/dashboard

Announcement Article: https://netbird.io/knowledge-hub/control-center-draft-mode

CasaOS -> Glance -> Homepage

made these backgrounds too.

I previously made a post a while ago about wanting to leave Proxmox for my own version of Arch using packages such as Cockpit, Podman, and other tools. Though I decided to use Debian 13 instead for this task. I only had a very basic Proxmox setup at first and did not really like the way I had configured my server. This made me wonder if I could use a more bare bones distribution like Arch or base Debian and configure my system the way I liked it to try and challenge myself more. If anyone has an suggestions of more services to deploy or things to try please let me know. Also, I do not hate Proxmox I just wanted a way to challenge myself and learn some new things.

Here's an overview of my new setup:

Host Specs

Intel Core i7-9700K

32GB DDR4-2666

128GB SATA SSD x4

Storage and Filesystem

Instead of using a basic partitioning scheme I built out my storage to fit my needs. I used RAID for my root and gave it 20GB on each drive so I could have enough storage for my main system files. Then I dedicated the rest to my ZFS pool for /home where all my containers were to be held. My purpose for using ZFS on /home was because I wanted all the benefits of ZFS for all my containers.

Partitioning Scheme

o 1GB EFI

o 8GB SWAP (RAID 10)

o 20GB root using BTRFS (RAID 10)

o Remaining mounted on /home using a striped mirror zfs pool (essentially RAID 10)

Networking

Host Interface

o Statically assigned on my LAN subnet

Podman Macvlan

o Used to assign containers their own individual LAN IP addresses

Kernel Macvlan Shim

o Virtual bridge to allow host-container connections and allow routing from my VPN

Services

Cockpit Web GUI

o I use this to stand in place of Proxmox’s web interface, as it allows me to remotely manage and watch my host’s status and resource utilization.

Uptime Kuma

o I am running this application in Podman and it allows me to set a dashboard that monitors the uptime of services such as my DNS, VPN, DDNS, and more.

Ntopng

o Used to monitor live traffic flows across my network and is run in Podman. It monitors my host’s network interface and allows me to view all egress and ingress traffic.

Technitium DNS

o Configured local authoritative forward zones and reverse lookup zones with custom A/PTR records for my LAN and WireGuard peers. I also added a blocklist to my network to block trackers, telemetry, and ads.

WireGuard VPN

DDNS Configuration

Ok, I posted this here a few months back and it didn't go well. I gathered the feedback, and the fair part of it was that I never explained why I built this or how it compares to what everyone already runs, so it read like just another "self-promotion, vibe-coded over a weekend" post. Trying again.

I have a fleet of IoT devices (very cool robotic hives) writing messy, unstructured logs, and I needed something that can store and search years of it. What I ended up looking for was a real inverted index, long retention that doesn't cost a fortune, fast needle-in-a-haystack search, and something one person can run and manage.

Why not Loki: Loki indexes labels, not log content. Search for anything outside your labels and it slows down a lot. Fine when you know which stream you want. Less fine when you don't, which is most of my searches.

Why not ELK: It does full text search well, no argument there. But it's a lot of moving parts for one person: nodes, shards, heap, ILM. I didn't want that to become my second job. To put it simple: it felt too heavy for my needs.

Why not VictoriaLogs: I like it, and I run it for different purpose. It stores on local disk though, and object storage is on their roadmap but not shipped, so retention still means paying for EBS. Otherwise a great tool and you can happily point it at your logs.

On the other hand, this amazing tool - Quickwit - does what I needed. Proper inverted index, and the index files live in object storage, so queries read straight from the bucket. Mine is around 100GB a day of raw logs, compressing about 5.5x, kept for 24 months, and S3 comes to roughly $300 a month.

So why I built Rootprint?

Quickwit ships an API with very basic UI. I ran it behind Grafana's Quickwit plugin for a while and that plugin gives you search and not much else. My team works with these logs every day, so I built the layer above it:

• log search with a field sidebar, click-to-filter and a histogram
• saved views that remember query, filters, sort and columns
• configurable context around a log line, plus a traceback tab for stack traces
• OTel traces next to the logs, basic APM based on spans
• ingest over OTLP or HTTP NDJSON, or pull from Kafka, Kinesis and SQS/S3
• roles, scoped ingest keys, Google and GitHub login
• indexes, mappings, field config and retention from the UI

It's built around OTel, but most of the features works also with custom-shaped data.

What it's not: no metrics. This is logs and traces only, so for metric dashboards and alerting you still need something else next to it.

Demo with real data: https://demo.rootprint.io

Code, Apache 2.0: https://github.com/rootprint/rootprint

Tech-stack: Bun and Hono on the API, SvelteKit for the UI, Postgres for metadata, Quickwit for search.

Fair warning: I'm a solo developer on this, with QA from my team, so expect bugs, rough edges and some clunky UI. Open a GitHub issue and I'll look at it. I'm not claiming parity with Grafana, VictoriaLogs or ELK. It's just a passion project after 8+ years of doing strict infrastructure work and getting a bit tired of it :)

On AI, since it came up last time: Claude Code wrote some parts of the project and I've been refactoring them constantly. It also does a first review pass on my code and some general reviews. The core logic and architecture is mine, mostly written by hand. Feel free to call it AI-assisted, because that's what it is.

Sync-in is an open-source, self-hosted platform for file storage, synchronization, sharing, and collaboration.

Highlights of this release include:

• Favorites for files and folders across personal files, collaborative spaces, and shares, with a dedicated view, filtering, sorting, and gallery/list layouts.
• Improved selection management, with a new Selection panel showing selected items, their total size, and available actions.
• Unified recent activity, bringing recent files and comments together in a single filterable timeline.
• Redesigned copy and move workflows, with easier navigation between spaces and the ability to skip conflicting files during copy, move, and upload operations.
• More reliable full-text search, especially for dates, email addresses, hyphenated terms, Unicode characters, and prefix matches.
• Numerous UI and accessibility improvements across desktop and mobile.
• Major authentication, OIDC, WebDAV, upload, editor, and configuration reliability improvements.

This release also includes several important security fixes covering OIDC account binding, OnlyOffice callbacks, SVG thumbnails, WebDAV quota enforcement, notification links, authentication secrets, SQL queries, stored XSS, external sharing permissions, and storage path validation.

Full release announcement:
https://sync-in.org/news/sync-in-2-5/

GitHub release:
https://github.com/Sync-in/server/releases/tag/v2.5.0