"OpenBrain presents Agent-2 to the government, including the National Security Council (NSC), the Department of Defense (DOD), and the U.S. AI Safety Institute (AISI). "
4,559 karma · joined June 27, 2016
Github: https://github.com/zelon88
@zelon88
"OpenBrain presents Agent-2 to the government, including the National Security Council (NSC), the Department of Defense (DOD), and the U.S. AI Safety Institute (AISI). "
Astronomers have thousands of interesting things they would like to point their telescopes at. There are thousands of capable ground stations that could take the easy targets, and only 2 x-ray satellites which should be used only for the highest value targets where absolute clarity and resolution is required. But if you start obstructing those ground stations, the workload must be taken over by just 2 satellites.
Ground stations are valued because they help solve the capacity planning problem. More usable telescopes === more observation time. Having more ground stations frees up the 2 satellite telescopes for truly stunning shots.
The telescope was launched into orbit in 1999 and has been a tremendous value to astrophysics. Although it is showing signs of it's age, and it is not as capable or cost effective to operate as the James Webb telescope; it still offers scientists much needed capacity and logistics capability that come with having two telescopes in orbit instead of just one.
One of the fascinating parts about the telescope is it's resiliance and the dedication of the staff who control it. For example, to maximize the usable lifespan of the anti-radiation shielding, and to prevent radiation damage to sensitive features, the position of the craft is constantly being planned and adjusted relative to the sun to balance radiation exposure and maximize observation time at various targets. Much like telling a small child "don't stare directly at the sun" as they take in as much information about their surroundings as possible.
Where I'm sitting, the only manufacturing that exists in the USA is, for subassemblies or components that are purchased by larger companies on a contract basis, and manufactured by lower-middle class citizens. Boeing and GE is an example. And the reason Boeing buys domestically is only because they have to in order to limit their liability, reduce labor costs, and protect their IP. If the America you're looking for existed, Boeing would happily pay twice as much for labor to make components in house. If that America existed your television would be made here too, by people who weren't being subsidized themselves by Food Stamps.
There are no consumer commodity manufacturers in the USA who provide gainful employment without significant consideration towards corporate profit. There is basically nothing at Wal-Mart that you can buy that is made in the USA by people who are living in financial comfort. That's just not how late stage capitalism works.
In the case of Linux DKMS updates: DKMS is re-compiling your installed kernel modules to match the new kernel. Sometimes a kernel update will also update the system compiler. In that instance it can be beneficial for performance or stability to have all your existing modules recompiled with the new version of the compiler. The new kernel comes with a new build environment, which DKMS uses to recompile existing kernel modules to ensure stability and consistency with that new kernel and build system.
Also, kernel modules and drivers may have many code paths that should only be run on specific kernel versions. This is called 'conditional compilation' and it is a technique programmers use to develop cross platform software. Think of this as one set of source code files that generates wildly different binaries depending on the machine that compiled it. By recompiling the source code after the new kernel is installed, the resulting binary may be drastically different than the one compiled by the previous kernel. Source code compiled on a 10 year old kernel might contain different code paths and routines than the same source code that was compiled on the latest kernel.
Compiling source code is incredibly taxing on the CPU and takes significantly longer when CPU usage is throttled. Compiling large modules on extremely slow systems could take hours. Managing hardware health and temperatures is mostly a hardware level decision controlled by firmware on the hardware itself. That is usually abstracted away from software developers who need to be able to be certain that the machine running their code is functional and stable enough to run it. This is why we have "minimum hardware requirements."
Imagine if every piece of software contained code to monitor and manage CPU cooling. You would have software fighting each other over hardware priorities. You would have different systems for control, with some more effective and secure than others. Instead the hardware is designed to do this job intrinsically, and developers are free to focus on the output of their code on a healthy, stable system. If a particular system is not stable, that falls on the administrator of that system. By separating the responsibility between software, hardware, and implementation we have clear boundaries between who cares about what, and a cohesive operating environment.
I'd like to add my reasoning for a similar failure of an HP Proliant server I encountered.
Sometimes hardware can fail during long uptime and not become a problem until the next reboot. Consider a piece of hardware with 100 features. During typical use, the hardware may only use 50 of those features. Imagine one of the unused features has failed. This would not cause a catastrophic failure during typical use, but on startup (which rarely occurs) that feature is necessary and the system will not boot without it. If it could, it could still perform it's task... because the damaged feature is not needed. But it can't get past the boot phase, where the feature is required.
Tl;dr the system actually failed months ago and the user didn't notice because the missing feature was not needed again until the next reboot.
You'll be charging a 57kw model X for AT LEAST an entire day using solar panels that would barely fit in the trunk.
Musk touts the CyberTruck as "the perfect armageddon vehicle" but if you have no cell phone service how do you charge the truck? What if Tesla disappears, or GCP is down, or WW3 actually happens and the datacenters go dark? Can you operate the vehicle? What if the power goes out because... Armageddon. How do you fuel the vehicle?
What if Musk sees what I said about him on social media and accuses me of violating the TOS? Will he disable my vehicle remotely? I've seen this in the real world when a machine shop missed it's payment to Haas.
In a real armageddon, my 1997 shitbox would still function. My 2013 F150 would function right up until the EMP hit. A 2025 EV probably would not make it to a fueling source within 24 hours after the power goes out.
It would be nice to know when a site is probing the local network. But by the same token, here is Google once again putting barriers on self sufficiency and using them to promote their PaaS goals.
They'll gladly narc on your self hosted application doing what it's supposed to do, but what about the 23 separate calls to Google CDN, ads, fonts, ect that every website has your browser make?
I tend to believe the this particular functionality is no longer of any use to Google, which is why they want to deprecate it to raise the barrier of entry for others.
As a side note, BeamNG.Drive has the most accurate throttle response and audio response of any driving game I've ever tried. You can almost feel the car pull vacuum (or build boost).
Seriously, just screw off. We needed you 3 months ago. We'll call you when it's time for your day in court at Nuremburg 2.0.
I can't imagine anyone who would make the mistakes this guy makes, yet here he is; freely using his computer in clear view of a reporter with a camera.
The article states that "at least one line of code must've been added" to support such a feature, which I believe to be an honest and accurate assessment.
I'd be concerned purchasing a book from a "programmer" who claims to teach people how to code without code. Kinda sounds like an "author" who publishes books without writing books.
Honestly, I have no compassion for Apple or Google. I'd be willing to endure a lot of headaches in the name of costing those two companies influence over our society.
You seem so alarmed by my proposition to nationalize a private company. Would you have been so alarmed if the government were punishing people for crimes without due process?
The US Government should nationalize Starlink and provide all Americans with internet service. It's the only way satellite internet makes sense.
I'm someone who tries to avoid AI tools. But this paper is literally basing its whole assessment off of two things; wages and hours. This is a disingenuous assertion.
Lets assume that I work 8 hours per day. If I am able to automate 1h of my day with AI, does that mean I get to go home 1 hour early? No. Does that mean I get an extra hour of pay? No.
So the assertion that there has been no economic impact assumes that the AI is a separate agent that would normally be paid in wages for time. That is not the case.
The AI is an augmentation for an existing human agent. It has the potential to increase the efficiency of a human agent by n%. So we need to be measuring the impact that is has on effectiveness and efficiency. It will never offset wages or hours. It will just increase the productivity for a given wage or number of hours.
$229 per year on a closed source product and this is the level of quality you can expect.
You can have all the respect for users in the world, but if you write downright hazardous code then you're only doing them a disservice. What happened to all the metered internet plans you blasted for 3 months? Are you going to make those users whole?
Learning from and owning your mistake is great and all, but you shouldn't be proud or gloating about this in any way, shape, or form. It is a very awkward and disrespectful flex on your customers.
This is basically a reliable, commercially viable version of that concept.