The self-hosted app never went away; I've been running it for the last 8 years or so, first on a MacBook Pro, then a Raspberry Pi, and now a repurposed HP T620 thin client.
They promote their cloud controller pretty strongly, followed by the Cloud Key, which is their own preinstalled self hosting setup, but the self-hosted UniFi Network server has stuck around. (It changed names a couple of times; it was the "UniFi Controller", then "UniFi Network Application", and now "UniFi Network Server".)
Seriously though... why didn't the SAR team try sending a text? Texting before calling is the standard protocol for anyone up to date with modern phone usage, but it's also way more reliable when trying to get in touch with someone with a flaky connection, which is probably the case when lost in the wilderness.
Ahhh... a popular topic in my household; lots of digestive issues here.
Collectively these chemicals (the ones that cause digestive issues like the author's) are known as FODMAPs, and cause issues for a lot of people. Monash University is the authority here, having identified them in the first place and produced a ton of dietary information about them: https://www.monashfodmap.com/about-fodmap-and-ibs/
The author says she doesn't have any trouble with lactose, fructose, and gluten, but cutting out sugar alcohols (polyols, the "P" in FODMAP) helped a ton. This is pretty common; people with FODMAP intolerance can typically digest some but not all of them.
The process is basically (1) go on a very restrictive elimination diet that cuts out all FODMAPs, then (2) gradually test each one at different quantities to find out if you can handle it and at what quantity.
My wife and I find that taking a whole 120mg (12 hour) pill makes us too jittery, but they're easily broken in half, and half a pill gives acceptable decongestant effects while making the side effects a bit better.
My HN workflow is to open a bunch of tabs, then close the main page, and read through all the articles. When I got to this tab, I saw "404", figured I'd hit a bad link, and closed the tab... then realized that that was the name of the publication.
Something I didn't mention in my comment is that I would love some kind of mounting bracket that would fit a WD Easystore (the big cheap disks that r/datahoarder loves) in such a way that I could easily open it up and swap in another disk; this would be for my backup box, which backs up everything to a USB disk that I periodically swap out with another one that lives offsite.
I'm always interested in seeing a new attempt to solve the problem of organizing a ton of little devices and a mess of cables. My personal attempt involves mounting a couple of UniFi bits directly to the wall, plus a little shelf made out of scrap 1x4 pine for the odd shaped things and the power strip.
Maintenance issues aside, the setup in the linked article looks quite pretty and should have decent airflow for passive cooling, which is nice!
The Chromebook edition is based on the "brya" motherboard design shared by other Chromebooks with 12th gen Intel processors, so it won't be the same as the usual 12th gen Framework board. You can install Chrome OS Flex on the standard Framework mainboard, though; I think earlier commenters have provided more detail.
If you want to release it as open source and don't care about owning the copyright, there's a process you can go through to release a new open source project. If you just want to send patches to an existing project, you can generally just do that, as long as the project has an approved open source license and is not on the (short) list of disallowed projects.
This is very very cool. I had coincidentally just spent my evening trying to figure out how to get Wayland and Sommelier working in a slightly odd environment (Crouton, on Chrome OS), and this article showed up on HN just in time for me to appreciate it :)
With my 2014 MBP, my Windows laptop, or my Chromebook, I can plug straight into a hotel TV and watch a movie from my laptop. With my 2019 MBP, I need an adapter.
This doesn't seem like a big deal, but the first time I went on vacation with my family after getting the 2019 MBP, I forgot that I needed to pack the adapter, and we couldn't watch whatever series we were currently binging on Netflix or HBO, which was pretty annoying. I'm happy to see HDMI ports showing up on more laptops these days!
Googler here... I transferred teams this year, and did it by searching Grow for keywords I was interested in, then emailing a hiring manager. I think out of the thousands of jobs in there I was interested in about two or three, but that was enough.
Another way to do it is to ignore the official process and go make friends on teams you're interested in. If you're looking for Go jobs, maybe just do a code search and figure out who's writing a ton of Go, and see if any of those look like fun. I know there's a lot of Go code in Cloud, which is usually hiring. There's some Rust in Chrome and Chrome OS, if you're into that.
I've never done a 20% project myself, but I hear those are good too. I gather that lots of little teams hardly ever get headcount, and starting out as a 20 percenter is the only way to get into one of them.
Another Googler here, speaking directly to the "working on ads" point: Ads is huge, but it's not hard to stay away from it if you're not interested. I worked in Cloud (App Engine) for four years and am now working on Chrome OS, and out of all the people I've worked with who transferred to other teams, I've only heard of 2-3 who moved to Ads.
Internal transfers are pretty easy too; it's not unheard of to switch teams every 18 months or so, so when you get sick of working on whichever huge distributed system you start with, you can go work on consumer hardware, one of the various operating systems, Google Maps, the Chrome browser, a site like Google Docs, one of the many iOS apps, one of the Cloud products, etc etc.
Working at Google isn't the wonderland some articles paint it to be, but it's definitely not boring, and there are lots of interesting people and projects around. You might not find your job itself to be super meaningful, but being surrounded by thousands of other engineers who all would like some meaning in their lives makes for an interesting community, and tons of fun little at-work side projects.
Yeah, T1 is pretty much just a pain whatever you do. Low carb does make it quite a bit easier, and I imagine would pretty much be the only safe way to eat if you were using a non-rapid insulin.
Unfortunately (doctor's orders) I also have to cut back on the cholesterol, which seems to be very high in all my favorite low-carb foods :( It's a constant experiment; it may turn out to make more sense to eat more fat but take statins, but I need to wait a bit longer and see how my lipids look with the current diet.
(BTW I'm actually doing fine -- pretty decent control/A1C -- but I had to rant in response to the Walmart insulin suggestion above!)
Type 1 diabetic here. Managing T1D even with the "Gucci" insulins (I use Novolog and have tried Fiasp) is still a huge pain in the butt; you have to give yourself a dose of insulin a fairly precise amount of time before eating, and accurately judge how much you're going to need, which is half science and half wild guesswork. My per-meal dosage requirements vary randomly from month to month -- a dose that would be fine one month is either inadequate or deadly on another month, and the only way to tell if you've got it right is to obsessively monitor your blood sugar.
And that's with the $700/vial insulin... the $25/vial stuff is stone age technology by comparison; you have to take it twice a day, and then eat at two specific times afterwards, or you'll go hypoglycemic (unconscious or maybe dead hypoglycemic, not just the feeling-a-bit-tired kind that people who don't use insulin are familiar with).
The situation right now is that the best and most expensive T1D technology, even the various "artificial pancreas" solutions, still gives you nothing like the experience of a normal pancreas. It would be really nice if the Walmart insulin were a viable long term solution for the cost problem, but unfortunately the negative health effects of older insulin tech are considerable :(