ghjnut

I've been running my agents in a docker sandbox that automatically mounts the current directory. It's been a bit of a pain to figure out and maintain the set of tools I provision into the sandbox- but it's fun to watch codex go to the ends of the earth trying to figure out solutions using nodejs (the only runtime).

I don't know zig well. What's raising flags for you?

I had issues too that they sent a tech support out for while warning me "If they find it's your fault, you will be assessed a charge". The tech came out, climbed my local pole and then went down the street and climbed another one. He said it was a busted port and he moved me to a new one, and put in a service request to upgrade as it was out of ports.

CenturyLink sends me a bill for maintenance. After tons of back and forth I got to the point where I said "So can you state for the record since I'm recording this phone call, that I the customer should have climbed the telephone pole to remedy the issue".

After that he finally decides to get in touch with the fiber contractor they use who emphasized it was no fault of my own and they cleared the charge.

Some pretty interesting stuff that hits home for me. I was diagnosed with lung cancer in 2021 and I had an army of family and friends trying to find me a covid vaccine when it was only being offered to seniors 65+. Finally had a friend volunteering at a vaccination clinic which had some leftover and called me in. I wouldn't have considered it might impact my cancer treatment outside of them being unable to operate if I had covid.

My original story: https://news.ycombinator.com/item?id=27023395#27024492

Yup, went to Haiti and had my antibodies tested for Tdap and MMR before going. One of them I had to get titers for...I think Tdap?

Disingenuous take.

Here's the original study: https://www.nature.com/articles/s41586-025-09655-y.

There's a marked contrast between vaccinated and unvaccinated survival rates, and they pretty extensively tested and ruled out additional mechanisms they thought may be influencing their observations.

Aim small, miss small?

It is, which I'd argue has a time and a place. Maybe it's more specific to how I cut my teeth in the industry but as programmer whenever I had to ask a question of e.g the ops team, I'd make sure it was clear I'd made an effort to figure out my problem. Here's how I understand the issue, here's what I tried yadda yadda.

Now I'm the 40-year-old ops guy fielding those questions. I'll write up an LLM question emphasizing what they should be focused on, I'll verify the response is in sync with my thoughts, and shoot it to them.

It seems less passive aggressive than LMGTFY and sometimes I learn something from the response.

Carl Hewitt has been championing it for a while https://arxiv.org/abs/1008.1459 https://youtu.be/7erJ1DV_Tlo

I was diagnosed with stage III NSCLC February '21. Radiation, chemo, and a bilobectomy. I had the ALK+ morphology which meant I wasn't a candidate for immunotherapy but I've been on alectinib since my surgery in June '21 with no signs of recurrence so far.

The process is grueling in hindsight, but I'm glad to hear you're getting results. At first I would have said "if this is going to kill me, make it sooner rather than later" to avoid a drawn-out painful experience, but I'm starting to appreciate what the buying time really means. It's hard with all that's going on but get your head straight and make sure you enjoy it.

Keep on keeping on.

Which container extension are you using for domain grouping? I've been looking for a good one

Thanks for the response, that clears things up quite a bit. Would you create jump-boxes per environment or do you generally just have 1 with all the different service/env access logic?

Could someone do me a solid and explain best security practices around bastion hosts and vpn?

e.g. - would you still require users connected to the vpn to go through a bastion host? - would you ever run bastion/vpn through the same box? - are there preferred access use cases for each?

If you'd read through to section 3.1 you'll see that they detail the iOS and Android bootstrap mechanisms. The title doesn't specifically identify which OS was infiltrated though in this case it was iOS.

I'm guessing the reason why iOS exploits receive more face-time is: 1. Apple has advertised their phones as being at the forefront of security, which holds some merit. 2. iPhones have become commonplace among government employess (possibly as a result of point 1). Political exploits are inevitably more in the public eye if it's the tool of most politicians.

It's the same concept as the early days of Microsoft being the powerhouse of consumer operating systems- everyone was using it making it the most lucrative to exploit.

That's actually better than I heard. Since ALK is more generally rare biomarker (as opposed to EGFR) more of the drugs are still in trial. I asked an oncologist friend about costs and she said $11,000/month.

I live in Denver. I have not done any testing but moved into this house June 2019. Our inspection found the radon levels to be 3.9 pCi/L (4.0 is the recommended actionable cut-off). I recently installed a radon abatement system as we're refinishing the basement. Wish I knew for sure.

Thank you. This is exactly the stuff I'm looking for as a newbie to keto.

That sounds a lot like it. Maybe the cancer triggered it or maybe I just lucked out with an unrelated symptom prompting me to visit a doctor.

Definitely not the craziest think I've heard (vitamin B17 is). I'll check it out.

I have been turned off by how the approach is to treat me and I'm primarily a passenger for this ride. In response, I did the same research you did and came across the same stuff. During the chemo/radiation I was on a strict ketogenic diet with a less strict intermittent fasting schedule. Post-surgery I'm going to go the full 9 yards and extend to 7-day fasting once a month after hearing this anecdotal story:

https://www.saronarameka.com/ https://www.frontiersin.org/articles/10.3389/fonc.2020.00578...

I hadn't considered that. Thank you, I'll bounce that off them.

That is correct. Unfortunately the TKIs are more for slowing/stopping spread temporarily until the cancer no longer responds - then on to the next one. My doctors were going for curative so I've been going the more traditional route and those will likely be tagged on post-surgery in an effort to keep anything missed in check. Also ALK+ is non-responsive to immunotherapy which would have been nice weapon to have in the arsenal as a cleanup crew.

It may be a pipe dream, but I'm hoping to hold on long enough that some of these new mRNA approaches start offering clinical trials I might be able jump in on.

I had a dry cough for about 3 months that only seemed to crop up in the evenings. I didn't think much about it as I have quite a few allergies and chalked it up to that. I decided to visit the doctor when I started getting some chest tightness when I was going to sleep and I was also getting what I can only describe as hot flashes just as I was falling asleep. It felt like just as I was about to fall asleep I'd get an adrenaline shot and I'd spring back up wide awake.

My PCP did a clean EKG which showed nothing, then it showed up on X-Rays. I immediately got PET scans which showed 2 masses. I then had a bronchoscopy to ensure it was malignant where they noticed additional lymph nodes. I then had a mediastinoscopy showing spread in 3 clusters of chest lymph nodes. I went through 6 weeks of chemo and radiation that resulted in a 25% reduction in the primary tumor and no change in the metastases in a hilar lymph node. I'm now scheduled for a bi-lobectomty to remove my superior and middle lobe on the right side, as well as however many lymph nodes they can get a hold of (check out "da vinci thoracic surgery" to see the robot beast the surgeon will be using).

I have almost no symptoms outside of a slight cough and still run 1-2 miles per day.

I've generally been a grin-and-bear-it guy when it comes to my health. Please suck up your pride and stay on top of your health.

This is me. I'm 34 years old and was diagnosed with stage 3B non-small cell lunge cancer in February- a 3cm adenocarcinoma in my right lung as well as metastases in some lymph nodes. When they tested me they found my cancer to have an ALK+ biomarker which is frequently found in young, non-smokers. Luck of the draw I guess.

Hijacking a bit, but does anyone have any good resources/guides around managing terraform state in larger organizations? Terraform enterprise seems to address this but I was wondering if there's workflows that allowed subsections of infrastructure (think teams or systems) and didn't rely on a re-evaluation of the entire organization's assets. So far the only approach I've seen is having protected high level (VPC, subnets etc) as a separate state and using terraform_remote_state to reference those.

Didn't know what an SFU was. https://webrtcglossary.com/sfu/

Actor-based programming really interests me. The concepts behind erlang and smalltalk seem to be the closest to an ideal model for the amount of distributed computing power we have today.

It seems like we should be able to formalize a generic meta-programming language that describes discrete components. 'actors' would be concepts close to functions that receive inputs and return outputs, everything inside would be generally considered synchronous. These actors speak to other actors via addresses. That idea was all outlined by alan kay. Furthermore, these actors can live anywhere. They can be running on a single CPU, live across multiple threads, cores, processors. Ideally you just throw more processors or remove processors from the mix and the system distributes.

Where the rubber meets the road is all the communication mediums. The lowest abstraction is your actor return address is a stack pointer. The highest is the return address is another system (what we currently do with RESTful communications).

Once all the inter-actor controls are sorted out, there would need to be a system of dynamic resource distribution. The profiler/scheduler should be able to identify things like - this actor is handling 85% of traffic, distribute the actor to 6 cores - the cost of the route from a core to a core on the same processor is X, the cost of the route to a core across a network is Y - distribute actors that have the most cross communication as closely as possible - payload size would also need to come into account

on top of that, tooling that identifies workload-specific needs could also be identified: - this set of actors should be considered critical and available on % processors - take into account things like inter-region availability.

A lot of these concepts have already been hashed out and you notice the parallels to things like network architecture. Ideally in the end a 'system' would simply be a pool of usable resources e.g. SYSTEM1: my laptop, an AWS server, my phone, my watch. Computation work is unevenly distributed to the system based on route costs, computational power...even storage capabilities and peripheral access (printers, cameras, etc). A new actor would get initialized in the network and it could be scheduled on your desktop or your tablet. Eventually your system would just become an amorphous workload.

My desktop might begin distributing subsets of things that currently run locally to my AWS server because it's closer to the public API i'm accessing. If actors were generic enough they might be identified and made a reusable pool for multiple applications.

Sorry for the stream of consciousness.

It sounds like you haven't given it a whirl. I've been on neovim for about about 3 years now after 5 years of native vim and it's been a complete drag-and-drop.

It's also cool that artists will jump on to elaborate on their own lyrics. Here's Eminem talking about his hook in 'Rap God' https://genius.com/2566991

Tutorial's pretty quick and gets you a good idea of what they're shooting for. https://doc.rust-lang.org/book/README.html