221 karma · joined July 29, 2015
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.
My original story: https://news.ycombinator.com/item?id=27023395#27024492
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.
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.
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.
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?
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.
https://www.saronarameka.com/ https://www.frontiersin.org/articles/10.3389/fonc.2020.00578...
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.
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.
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.