zzyzxd

All my servers were debian until I brought some Raspberry Pi 5 boards. Debian still does not have tested images for them today.

A better link to point to the comment from the former employee:

https://forums.plex.tv/t/2026-20-0-beta-ios-and-tvos-4k-dovi...

Plex stopped working on any DoVi/HDR10 videos I have, and today I found this thread.

I don't use Docker but I love reading the compose file when a project has it. It is the quickest way for me to get a high level idea of this project's architecture. It's the best documentation :)

I was going to recommend ente as well.

My photos and videos are the most important files I have in my self-hosted storage system. Being end-to-end encrypted buys some peace of mind knowing that it's not end of world if my homelab is compromised. And I can backup the data to whatever public clouds without worrying too much about leaking data.

There are reasons graphical interfaces exist. Otherwise why don't we hide everything behind one single search box? And unless you are a die-hard Apple fan, you may not always know the correct feature name to search for.

I would never have figured out the toggle for writing tools is in `Settings -> Screen Time -> Content & Privacy Restrictions -> Siri -> Writing Assistance`

It's funny because different people would interpret this sentence differently.

If you have high level understanding of the tech behind it, this feels like a threat. But if you don't, this sounds like an honest message from someone who genuinely wants to protect you.

A regular user log into Google account and see their photos today. Tomorrow they log in and see the photos again. And they would assume this system will always work like this.

Those people are designers. And they don't necessarily understand software, data, or security. When I explained to my non-technical friends about how they were being tracked by website cookies, it sounded like a sci fi story to them. But yes, it's dumb.

I was more surprised by how they managed to keep using work devices after termination. This sounds to me like a failure of their manager to do their job to follow the standard exit process.

In my experience, those operations require understanding, judgement, and taste. But all of that only matters if I care about the codebase enough for it to matter.

So I don't think the disagreement is really about git. It's about how much of the thinking you're comfortable outsourcing. I do have some repos that's highly vibed up, in those repos I just let AI do whatever it want.

The author had 27 years of experience but still found "babysitting git" was painful.

I couldn't remember what's the last time git got in my way. I guess such benefit from AI is probably very specific to their setup. I don't know, maybe the author had some really complex workflow or used some super advanced git features.

My water heater once emitted a cryptic warning light. I called a local contractor, the person came and spent 10 seconds inspected the appliance, then start dialing the appliance vendor's support number. Support asked him to press some buttons in a fixed sequence and the tiny display on the water heater showed an error code. Support said "yeah, that means part X is not working, but we don't know why" and the solution was replacing that part entirely.

"Wouldn't it be nice if the water heater comes with hundreds of sensors monitoring each part and emit metrics? You can diagnose with historical data and see what was working and at what time which part showed anomaly". As a person doing SRE in my day job, this was what I had in my mind at the time.

I am not saying that I want spyware in all the appliances in my house. But if I am an appliance manufacturer, I would always want the capability to manage appliances just like how software engineers managing software lifecycles.

> Yeah but you won't so it's not a big problem

The reason you can comfortably say this is exactly because we orchestrate our society around what someone "could" do.

Operating a drone is not that easy, today. And killing someone has consequence most people don't want to face.

What if we enable every human to be able to kill someone anonymously by pressing a button?

I think the blog post's target audience were people who already embraced vibe coding. It's not for you (or for me).

But still, between the lines the blog seems to want to picture an imaginary AI agent that has somewhat predictable behavior ("if you do X with your agent, you will achieve outcome Y"), which is definitely wrong expectation.

That's my point. It's not about the technology itself, because that's never cut and dry. It's about having a process to evaluate and criticize a technology before fully embracing it. Socrates was in a position with loud voice. Critics of technology exist today too, but they aren't loud enough. Instead, there's a far stronger force coming from private companies and their investors to push whatever they want onto us.

But I want to admit that I was indeed shoehorning my rants about AI (not the technology itself, but how it is being adopted) into this topic. Let me stop steering the discussion further. I do think the fact that we could recover Herculaneum papyrus like this is amazing!

It's a thread border router and matter controller, providing Remote access to local-only devices, scheduling, automation... with better track records on security and privacy than competitors.

I think nowadays the Apple TV is more about smart home than TV. But as long as they keep calling it a "TV", most of the people will compare it with the built-in apps in their smart TVs and think it's unnecessary. Even if you tell them that it can do much more than watching TV, they will think the money they spend on the TV related functionalities is a waste. The old price was already hard for them to justify, the new price is almost impossible.

Every friend I asked about why they don't buy Apple TV, "I don't need TV apps" was the reason. Guess what, many of them still wanted smart home integrations so they brought smart home hubs from Google/Amazon or other vendors for not much lower price, even when they already use and like iPhone and other Apple devices.

Well I didn't say it was achievable at the time. But is it really that unimaginable?

> assuming nobody fell asleep on watch, the wood was dry, the fog cooperated, and the enemy hadn't already lit a fake beacon to mess with you.

So you are talking about dealing with "packet" loss and data encryption, right? Those concepts were not new to them.

They already learned to use light and fire to transfer data over long distance. How much difference is there between beacon fire and fiber optic cable?

But I think they would be more surprised by how we managed to invent things like social media and AI, which destroy our brain. Ancient societies valued wisdom much more than us and were much more careful when introducing new technologies. It was fascinating for me to learn that even writing, as a skill considered universally good these days, was once subjected to scrutiny[1].

https://en.wikipedia.org/wiki/Plato%27s_unwritten_doctrines#...

It's totally fine to not to use k8s. Personally, I think I have made several good decisions in my career to use/avoid k8s in different scenarios.

But if someone wrote a blog to brag about not using k8s, they can't stop people from wanting to compare their work against k8s. If there's any arrogance in the air, it feels stronger on the other side.

If this creation stays as is, then it's not very complicated and pretty easy to understand and support. But that is a big IF, and very likely won't be true. Over time people will add more useful features to it, then it becomes another Kubernetes (and if you don't have a strong engineering team, it will probably be much worse than Kubernetes).

The biggest concern about Ubiquiti to me is still its software/infrastructure quality.

Off top of my head, besides all the UI/UX glitches:

- They once allowed a human employee to access static AWS root access key.

- Their employee once claimed "remote access" was end to end encrypted, but later people figured out they probably just meant TLS in transit.

- They had a configuration error that allowed some users to access other users' camera feeds. They corrected the error, but never explained how the hell was it even possible or if they made any architecture design change to prevent that from happening again.

Now, ZFS is nice. But even after years of iterations, I still need to do 50% of my operations via SSH on my Truenas system. I can't imagine Ubiquiti to do any better

I totally believe this works for you. But in your case, isn't NixOS just another declarative orchestration system like Kubernetes? Similarly I can just run a standalone nginx, caddy with acme, and a coredns pod in a bare minimum k8s cluster.

Personally, I think the complexity is on the same level.

> One thing that I think people new to it don’t realize is that it’s not at all batteries included - to get a basic managed cluster setup, you’re still going to be installing a bunch of additional controllers (ingress, cert-manager, external dns to start).

And if you can do this again, what's your solution to reverse proxy, certificate management, DNS...etc? I guess you can docker-compose some custom stack on a single machine, maybe add one more machine then you can say it's HA enough for small scale. But you can also spend the same amount of time to install those kubernetes controllers with zero customization. In my experience, if you go with the default configuration, most of the well-maintained k8s components are boring as hell these days.

> (if you’re on EKS, make sure to read about scaling and monitoring CoreDNS)

If load to your service increases, you need to scale up/out your service. This is universally true. Do you have a proprietary solution that's easier and more reliable than bumping up the replicas count in kubernetes?

There are lots of design decisions in Kubernetes that I hate. But if you want me to choose between Kubernetes and any proprietary stack, in 2026, I would definitely choose Kubernetes.

IMO that is not a rockstar developer, but a junior developer rocking LLM agents.

Completing each individual programming task is easy. Engineering the system in a sustainable way that changes can be traced, understood and reasoned about is difficult.

The problem is, as many other comments have pointed out, typically the business doesn't value this.

Automation should always be the serialization of understanding of the system, which can execute on its own under normal conditions. When it breaks, your reaction should not be removing the automation and asking humans to get back to manual operation, that is the wrong approach. Instead, you should ask humans to leverage their understanding to step in, reason about the automation system, and fix it.

This is how I have been doing SRE for the past decade. And the inability to practice this under-the-hood reasoning is the main reason why I don't trust any modern AI based automation systems. They are helpers for some manual work, but they can't be automation.

If they are ok with shortcuts being vibecoded, maybe it's time to expose a proper programming language to the end users as well.

All my automation shortcuts can be easily explained in pseudo code under 5 minutes, but it took me ages to put them together because that weird UI/UX forcing me to drag-and-drop squares around to manipulate data structures. Programmers hate it, non-programmers can't understand it, it is not designed for anybody.

I never care about AI usage disclosure, because I don't believe that human produced code is necessarily better than AI produced code, unless it's someone I personally know.

People need to be responsible for code they commit and push anyways. This has never changed. Whether the code is written by hand, by their cat walking over keyboard, or by AI, is not my concern.

A project's code quality can decline for all kinds of reasons. I don't think it's productive to laser-focus on whether it's produced by AI or not. That's a distraction. If a person just want to find excuse to criticize AI, and another person wants to fight back and defend AI, sure, go for it. But that's not how you would want to assess a project's code quality.

It would be nice if I could talk to my parents in person everyday, feeling their touches and temperature. But we live in different countries, so instead I talk to them over FaceTime everyday. TBH, even if they live next door, I may not always find time to visit them everyday. So having a way to use a device in my pocket to talk to them is nice. It's a compromise I accept.

On the other hand, if I live in 150 years ago where telephone had not been invented, I may never make such decision to live so far away from my parents at all.

"Technology giveth and technology taketh away"

> every single manufacturer that wants you to install their app and use their ecosystem

That's good. I don't want a single company to control everything in my house. Having multiple vendors with different implementations is healthy for the industry.

The real problem is there's nothing "smart" about those "smart home devices" to begin with. They are just remotely controlled devices. Technically, someone or something still has to control them because these devices can't really make decisions on their own. And then, to make those decisions remotely (either in the cloud or in a home local controller), every home installation needs to be highly customized. There are several light switches in my house that I never need to touch -- their states are automatically shifted based on like ~15 conditions: time of day, light conditions, occupancy, human activities(iOS focus modes). Non technical people can't do that.

I would want those devices to make simple decisions on their own (I have a few "dumb" light switches with motion+light sensors and they are pretty good already), and for complex decisions, they expose some APIs for other devices/controllers to call. Matter seems to be the right direction, but it is still controlled by a handful powerful players.

It just takes time to design your hardware/software stack to be able to survive reboots and recover back to ideal states. I guess nobody really enjoys rebooting machines, but at the same time, I don't think people should be afraid of doing it.