Leo was sad that he didn’t get pancakes this morning.
https://lemmy.world/pictrs/image/3d67abf9-1325-4040-89a7-46e8e4ee7b2e.jpeg
Daisy and Rose were concerned that they might starve to death, but they always think they are starving and they got their salad at the usual time.
https://lemmy.world/pictrs/image/764214ee-48f6-4057-98f9-fbef6fe16722.jpeg
If someone told me years ago that I’d cook food for my pets, I’d probably laugh it off. And yet here I am.
As Kika (my 17yo cat) gets older, she’s becoming more of a picky eater. We had a vet checking her, she’s healthy; but she was eating less and less kibble, and losing a bit of weight. (Not enough to be visible, but enough to be noticeable when picking her up.) And she was still enthusiastically eating even harder treats, so there was no issue with her teeth or appetite.
So I rummaged the internet for info on cat nutrition, and came up with a decent recipe for cat food. I prepared it and offered her a bit of that food. And oh boy, she ate it. She ate it with shining eyes, and the voracity of someone who’s tasting ambrosia. (The divine one.) And asked me for more.
Curiously, Siegfrieda (my other cat; she’s ~9yo?) smelled the food, made a “…meh” face, and went for her kibble. I say “curiously” because she was adopted in her adulthood, and used to be a street cat.
Now I’m even a bit worried since Kika stopped touching her kibble altogether; I tried my best to make the recipe balanced and healthy, but I can’t rule out some missing micronutrient.
Hi! I am running Umbrel on a Raspberry Pi 4 and I have “Home Assistant” installed in it, I oly have some smart lights connected to it. I would like to integrate a Thermostat with HA. But I am a bit overwhelmed with the different types of connections (Z-wave, Zigbee, Wifi, …)
Do you guys have any kind of recommendation, what connection is better? I would like to keep it local (or connecting remotely via Tailscale) but I would like to avoid any cloud or third-party server solution.
What thermostat hardware can I buy?
I’ve recently started with home assistant on a pi as well. Today I have 2 zigbee relay for my lights from Sonoff, 2 zigbee fire alarms, 1 wifi plug from Shelly and 3 Ikea remotes working on Matter over Thread.
Basically, any protocol you want to support other than wifi and Bluetooth will need a dedicated radio device. Luckily they are all pretty well supposed with home assistant. I have 2 Aeotec Zi-stick, one for Zigbee, the other flashed with OpenThread firmware (that’s for Matter over Thread, it wasn’t a good idea to buy twice the same device, I had to work around this issue). I don’t have Z-wave devices today, as I noticed they tend to be more expensive that the zigbee equipment. The new IKEA smart devices are very competitive in terms of price, they all work on Matter over Thread protocol.
In the end, you don’t need to choose. You can support all these protocols on the same raspberry pi. It’s just a matter of adding the corresponding radio and integration in home assistant.
My understanding is that that is because Google and Apple want to onboard it to their own home automation platforms, and HomeAssistant just piggybacked on that because it was easier, and it hasn’t been a priority to rewrite it. But this is based on a few old threads I just looked up, I’m not exactly an expert.
I think there was some talk about Bluetooth onboarding, but that’d require the devices to have a Bluetooth radio, which is more expensive that a QR code sticker. Idk if anyone uses it.
Having something like a WEP button would certainly be nice though.
I can’t wait to hear about this one will just randomly combust and melt a whole in the Earth.
my only complaint it’s not for over 65’s as well
Those old brains are beyond redemption, the new ones may be saved yet.
Voiden is an offline-first, git-native API tool built on Markdown - and it very intentionally didn’t start as “let’s build a better Postman”.
Over time, API tooling became heavyweight: cloud dependencies for local work, forced accounts, proprietary formats, and workflows that break the moment you’re offline. Testing a localhost API shouldn’t need an internet connection.
So we asked a simple question: What if an API tool respected how developers already work?
That led to a few core ideas:
Offline-first, no accounts, no telemetry
Git as the source of truth
Specs, tests, and docs living together in Markdown
We opensourced Voiden because extensibility without openness just shifts the bottleneck.
If workflows should be transparent, the tool should be too.
Github : https://github.com/VoidenHQ/voiden
Download here : https://voiden.md/download
Wow, an org mode rest client; this might be worth switching to! What I like about these is that you end up with documentation in a standard file that can live along with your APIs. Org mode can of course be saved either as org files, or exported as any number of things - whatever your team uses. Ok, time to go bully some vim users.
curl is great. I use curl. Most developers use curl. But “you can call an API with curl” and “curl is enough as an API working environment” are two very different claims.
The problem is that real API work is almost never just one request typed into a terminal like some kind of beautifully minimalist Unix haiku. It usually turns into auth, environments, copied headers, reused payload fragments, request chains, documentation, testing, debugging, sharing examples with teammates, reviewing changes in Git, and trying not to break prod because you forgot to swap one token or one base URL.
At that point, people are not really using “just curl” anymore. They are using curl plus shell scripts, plus notes, plus env files, plus copied commands from Slack, plus random JSON files, plus tribal knowledge. Which is fine, until it becomes annoying, fragile, and weirdly hard to collaborate around.
That is the gap Voiden is trying to solve.
So for me it is not “curl vs Voiden.” curl is a low-level execution tool. Voiden is a workspace for actual API work: writing requests, organizing them, reusing pieces, documenting them, testing them, versioning them in Git, and not duplicating the same headers/body/auth setup 45 times like a person slowly losing control of their life.
Hello!
I’ve been playing around with self-hosting for a while now and I’ve started moving over to a VPS. At home I have a PC that’s on more or less 24⁄7 with an *arr stack, jellyfin and some other services. They can only be accessed through Netbird. The services aren’t that important, the data doesn’t really need to be backed up since it’s not very important. On the VPS, however, I would like to host some more critical services, such as:
I want them available 24⁄7, even if I decide to distrohop and wipe my PC at home. The problem is how to structure all this. My current idea is to run Gitea and Overleaf out in the open behind some reverse proxy without authentication (Nginx or Nginx Proxy Manager). I’d like Vaultwarden and Immich to be on the same VPS, but, I don’t want those services to be accessible to anyone but me, so I’d need some form of ACL or authentication system. I’m thinking of using Netbird for this, since I already use it on all of my devices.
So I would set up DNS records from within Netbird that would point immich.domain.tld and vaultwarden.domain.tld to the internal Netbird IP of the VPS. In the reverse proxy, I’d set up access control such that it only redirects the Netbird IP range to those services. On Cloudflare, I’d point git.domain.tld to the external IP of the VPS with proxy enabled.
Everything would receive HTTPS certificates, and I’d block incoming traffic on every port except for 80 and 443.
Is this a good setup? Any tips or recommendations? Any pitfalls?
Thanks!
@versionc
Nice setup, pretty close to what I run. Few thoughts:
Reverse proxy + auth: I'd look at Traefik over Nginx Proxy Manager - it plays really well with Docker (auto-discovers containers, handles Let's Encrypt certs). For the auth layer on Vaultwarden/Immich, consider Authentik instead of tying it to Netbird. Gives you SSO across everything and you're not locked into one VPN mesh for access control. I run Authentik in front of most of my services and it's been solid (minus the time I accidentally deleted its secrets and locked myself out of everything - back up your auth server config).
Netbird approach: Using Netbird IP ranges for access control on the reverse proxy can work, but it's a bit fragile. You're coupling your network topology to your auth policy. If Netbird changes IPs or you add a device, you're editing nginx configs. A proper auth proxy in front gives you more flexibility.
Gitea / Forgejo: I'd also recommend checking out Forgejo if you haven't - it's a community fork of Gitea that's been moving faster and stays fully open. I ran Gitea for years before switching. Either way, I'd push back on running it without auth entirely. Even for public repos, you want auth on the admin/write side. Forgejo (and Gitea) support public repos with anonymous read access - you don't need to skip auth, just configure repo visibility. The built-in controls are solid enough.
General structure: Your instinct to keep critical services (Vaultwarden especially) off the public internet is right. Password manager should have the smallest attack surface possible. The VPS-as-entry-point pattern is good. I do the same thing with a cheap VPS running a reverse tunnel so my home IP is never exposed.
One thing to think about: if you wipe your home PC, make sure your VPS services can stand alone. Docker volumes + a backup strategy (even just weekly to cheap cloud storage) will save you when something goes sideways.
I posted this in c/Canada, but I thought I would share it here to. What have your experiences with jury duty been like?
Note about what “First Person” columns are:
First Person columns are personal stories and experiences of Canadians, in their own words. This is intended to showcase a more intimate storytelling perspective, and allow people from across the country to share what they have lived through.
A good piece will spur conversation. It could be a slice of life or a transformative moment that changed your life. Perhaps your personal story will inform how the reader thinks about the world.
Intro:
I knew I was a goner as soon as the sheriff walked into the room. He looked like everyone’s genial Uncle Bob except for the police vest and the walkie-talkie that hung from his belt.
“Juror 322, gather your things. We have to go see the judge,” he said.
A young blond woman picked up her bag and followed Bob out the door.
I knew that exchange meant she wouldn’t be back. And, as the alternate juror for a 12-member jury, I would take her place.
I have never met anyone who wanted to be on a jury. I certainly didn’t.
However, over the course of a three-week trial, we evolved from a gaggle of annoyed people crabbing about how this was going to take time away from watching The Pitt or on the pickleball court to a group that worked hard to figure out whether the accused committed the crime.
In true Canadian fashion, there wasn’t one moment when the piano started playing O Canada or we recited Jeff Douglas’s “I Am Canadian” speech. Instead, it was a collective shoulder shrug that basically said, “We’re stuck here. We might as well figure out the correct answer.”
I’m in the US, but my experience was a lot like that. I ended up as the foreman of a jury that was given an unusually nasty domestic abuse case. It was an intense experience. The court phase lasted three days. The testimony was disturbing and brutal, but the judge did a great job on all counts. The trial was well managed, the legal issues were clearly laid out, and the jury was told what we needed to do and how we should go about it.
Once we were sent to deliberate, everyone settled in rather quickly to doing their jobs carefully and honestly. We had long, detailed, and surprisingly analytical discussions. We requested transcripts of several key sections of the testimony and reviewed some of it word-by-word. Despite the intensity of the subject matter, everyone tried to keep the process rational and not emotional.
There were two holdouts. No one complained about them. We talked with them about why they had reservations and then dug into the evidence around those issues. We spent about a day-and-a-half deliberating, but we did come to a consensus. At the end, I think everyone felt good about our verdict, and about the way we came to it.
The whole process was very much what you hope a trial would be like, but don’t really expect to see. The judge and the lawyers were all engaged, professional, and competent. Everyone on the jury took their jobs seriously. They were thoughtful, careful, and thorough.
That experience actually did a lot for my faith in humanity.
I watched the first three episodes of it, starting yesterday, and I’m loving it so far.
More testing
guest test
guest test2
Read his name in the credits then look him up in the library.
Though I doubt that would work for this.
Oh baby.