zzyzxd

You are right. I didn't read the terms. Looks like ABE can only be used by a business entity.

This is interesting to me as the IT support for my family. I have been considering using MDM to provision Wi-Fi credentials and other device configurations. 3rd party solutions are a little bit too much for what I need.

Apple Business Essentials with AppleCare+ for 3 devices and 200GB iCloud storage is $19.99 per user/mo. That's the same price as AppleCare One alone.

I have a GL.iNet travel router. When I am not travel, it connects to the router's second WAN port. If my main internet goes down, it takes me 30 seconds to tether my phone and failover manually. My carrier detects and throttles hotspot traffic by measuring packets TTL, so I tweaks the router's iptables to dodge that. Typically I get over 400 Mbps.

From time to time I get the itch to improve my home network uptime, and I have to keep reminding myself that the current setup is fine.

I used to be the cool tech guy in school because I memorized the tutorial to jailbreak iPhone or to cheat in games with a memory editor. You know, stuff like "when you see this screen, click that icon", "find row 5 and change the second value to 0", or "open terminal, copy paste this command and hit enter". I don't think I learned anything useful from those.

Capital One does this to me as well, but at least they make it clear so I actually understanding what they mean ("You haven't opened an email from us lately...").

It's fine, Capital One. I did open your emails, I just didn't load your shady tracking pixels.

A gitops repo can never be the reflection of the system's actual state. It's a desired state your humans want the system to reach eventually, sometimes defined very loosely. This is the idea since Weaveworks invented the term years ago. Unfortunately I admit it's not very intuitive, especially to engineers who are not super familiar with declarative systems.

I used to be on the side of single NUC, but when my self hosted services became important enough, I realized I need to take security and reliability seriously, you know, all the SysAdmin/SRE stuff, and that's when I started moving to "that side".

Exactly. Once I was connecting to my VPN in AWS and was totally prepared for 90% of the websites to throw human verification at me. Then a faked cloudflare one almost got me. It was 3AM and my brain was barely functioning. (it didn't work, only because it instructed me to run a PowerShell command and I was on macOS).

Garage also decide to not implement erasure coding.

Teslas are the worst offenders in my area. I don't own one but I looked up online out of curiosity, and saw many owners complained because they got flashed a lot. Turned out the factory settings for the headlight angle was too high. They went to the menu and adjust the angle down by "2-3 clicks" and they reported never got flashed again.

If your infrastructure can justify the complexity of Kubernetes, keeping up with Kubernetes native software is extremely easy comparing to anything else I have dealt with. I had some horror story managing nginx instances on 3 servers with ansible. To me that's much harder than working with ingress controllers in Kubernetes.

Replacing an ingress controller in Kubernetes is also a well documented practice, with minimum or even zero downtime if you want to.

Generally, if your engineering team can reasonably keep things simple, it's good. However, business needs to grow and infrastructure needs to scale out. Sometimes trying too hard to be simple is, in my experience, how things become unmanageably complex.

I find well-engineered complexity to be much more pleasant to work with.

This idea has been around since at least a decade ago. The truth is, only a fraction of customers care about ads or privacy, and only a fraction of technical people in that group are capable of doing network filtering (VLAN, MITM, DNS blocklist, whatever). The absolute numbers are so small, as long as manufacturers can extract enough value from the remaining 99% of customers, they just don't care.

I have had a lot of friends amazed by the fact that when they connect to my home Wi-Fi they stop seeing ads. Zero of them interested in implementing something similar in their home.

Abstraction needs to happen on a different layer. Because your power users are already dealing with complicated stuff and you don't want to make their lives even harder.

I know about 10 people in real life that uses Handbrake. And 10 of them use it to rip Blu-ray discs and store media files on their NAS. It will piss them off if you hide all the codec settings and replace the main screen with a giant "convert to Facebook compatible video" button.

Instead, do it like how iina[1] packages mpv[2].

1. https://github.com/iina/iina

2. https://github.com/mpv-player/mpv

Earlier this year I found a leak in the house and called a local plumbing business. It was after hours, and a dreaded robot voice answered my call. I was fully prepared to spend the next 10 minutes rewording my issue over and over, hoping to hit the magic key word it actually understand (and also spell out my weird custom email domain). Surprisingly, this robot understood every single sentence I said, and repeated back in a slightly different, more professional way for me to confirm. It also captured my email address accurately in one try, without questioning my weird domain name. That's the moment I realized it's a LLM. It asked a few more smart follow-ups, then ended the call. The next morning, the owner called me and jumped straight into solutions, pricing, and his availability, without any more question or BS, because the LLM already told him everything he needed to know.

That's the most pleasant customer service call I have ever experienced. I wish more business could adopt similar approach. I don't mind talking to AI. In fact, instead of a live agent, I actually prefer to talk to your LLM, so my issue can be quickly triaged to the right human who actually understand my situation.

e2ee makes it easier to sell their hosted version, and there's probably not enough incentive to justify the additional overhead of having an unencrypted option.

Also, my house is less secure than commercial data centers, so e2ee gives me greater peace of mind about data safety.

The article is unnecessarily long only to brag about "a service we didn't use went down so it didn't affect us". If I want to be picky, their architecture is also not perfect:

- Their alerts were not durable. The outage took out the alert system so humans were just eyeballing dashboards during the outage. What if your critical system went down along with that alert system, in the middle of night?

- The cloud marketplace service was affected by cloudflare outage and there's nothiing they could do.

- Tiered stroage was down, disk usage went above normal level. But there's no anomaly detection and no alerts. It survived because t0 storage was massively over provisioned.

- They took pride in using industry well-known designs like cell-based architecture, redundancy, multi-az...ChatGPT would be able to give me a better list

And I don't get whey they had to roast Crowdstrike at the end. I mean, the Crowdstrike incident was really amateur stuff, like, the absolute lowest bar I can think of.

But you are not talking about maintaining Kubernetes, you are talking about maintaining a CI/CD system, a secret management system, some automation to operate databases, and so on.

Instead of editing some YAML files, in the "old" days these software vendors would've asked you to maintain a cronjob, ansible playbooks, systemd unit, bash scripts...

Still, as a candidate, it sucks that they worked for hours and only got a rejection with a templated message. At least tell me the reason why you don't like my work, so I can learn something from it!

I get it that it's not always realistic to do, especially if the hiring manage reviews hundreds of applications for a hot role. But that's why take home assignment sucks. Some candidates may waste hours of their lives for nothing. Both sides need to be respectful of other people's time.

I am also one of those guys don't always carry my phone around. That's why I load my keys and credit cards on Apple Watch, turned off most of the notifications on it, and only allow calls and text messages from wife.

And it's much easier to customize.

- I run it in Kubernetes with multiple replicas behind a load balancer for high availability.

- A companion iOS shortcut for family members to temporarily pause protection on all replicas for online shopping.

- Configuration as code, which gets mounted as a secret.

- Query logs from all replicas forwarded to loki for visualization and performance review.

Looks like a fun project!

But it reminded me of some people I know who lost their loved ones. Mother's Day, Father's Day, Valentine's Day...etc, could be extremely painful for them. As a friend, I learned that the best thing I could do, is to not to mention it at all, and block them if I need to post holiday related stuff on social media.

I absolutely hate that these days most of the online shopping sites blindly spam all their customers with holiday promo emails. Some sites give you an option to opt-out specific holidays but most of them don't.

How much value can LTS provide? If you care about stability, just stick with stable API versions and you will likely be fine. For instance Pod[core/v1] has been around for a decade.

If you go with a LTS version, you rely on the vendor to backport security patches, block your engineers from exploring new features, and if you use 3rd party operators/controllers, good luck with getting LTS support from all of them!

In enterprise market, people have been dealing with weird proprietary software for decades, finally there's a decent open source software with sane version skew and deprecation policies, and strives to make upgrades less painful. If you still can't do this upgrade once every year or two, likely you won't be able to do it in 12 years.

I imagine this might make sense if you are a non-tech company hoping to buy a software from a vendor and never worry about it. But in that case, Kubernetes is the wrong abstraction layer for your business.

From my experience dealing with them, Seagate's default warranty info is based on drive's date of manufacture. So it is possible that this drive had sat in some Amazon warehouse for 5 years before you got it.. You can register the drive with receipt to get that data corrected on Seagate's side.

I only linked to the HN thread, but there you can find links to discussions in HA community, for example: https://community.home-assistant.io/t/consider-to-avoid-addi... , which includes responses from forum admins and founders.

That's why I asked about attitude, not anything else. It's perfectly fine to decide to not to support someone, but...

"I release my code under FOSS license, but if anyone distribute it in a way I consider not nice, I will re-license it just to screw them over." [1]

When I was considering using HA and was casually browsing community discussions, there were many posts gave me similar feeling like above case. There were other technical reasons that I decided to not to use HA, but this certainly left a really bad taste in my mouth.

1. https://github.com/NixOS/nixpkgs/pull/126326#issuecomment-86...

What's the HA community's attitude towards FOSS nowadays? Comparing to 3.5 years ago?[1]

1. https://news.ycombinator.com/item?id=27505277

I am not saying 6 days is long enough, but if your automation always wait until the last minute to renew certs, you may have more issues to worry about than the CA's availability. If I am going to use a cert with 6 days lifetime I will be renewing it at least once a day.

What these companies worry about is not free information. Their concerns are usually around company IPs, copyrights, reputation/branding...etc.

Do those risks exist? Sure. But it's silly to blindly forbid your employee's outside-business activities like this. However, in this job market, employers probably can easily find candidates that don't have problem with this silly restriction so they don't have incentives to allocate resources to deal with the headache.

A personal website may sound too "professional" to a legal person. I bet OP could post the same information on facebook/twitter without getting into any trouble.

How many places is generally irrelevant. If a system requires user to provide 2 factors to authenticate, it is 2FA. A password manager software itself should be no exception.

For resources that are supposed to be cleaned up automatically, fixing your operator/finalizer is a better approach. Using this tool is just kicking the can down the road, which may cause even bigger problem.

If you have resources that need to be regularly created and deleted, I feel a cronjob running `kubectl delete -l <your-label-selector>` should be more than enough, and less risker than installing a 3rd party software with cluster wide list/delete permission.