The only possible way for this to do anything measurable if it somehow reduces the 50/60Hz AC hum impressed on your body. But either way with the wavelength of 60Hz in meat being like earth sized I dont think any significant electric fields will arise within two points of your body to do anything meaningful (as long as you stay AC coupled, if you DC couple to mains health effects are guaranteed).
Well considering the proof is pretty much accepted by mathematicians to be correct (I'll be happy with that!), it would be sort of unnecessary to cheat. Maybe if some aspect is really tricky to formalize it could have done something there? If I had to search for it, I would go for parts of the original proof that are "outsourced" to other mathematical works.
Imagine one of the agents struggling to download a paper due to a paywall or whatever and just deciding to cheat lol
I think there's a big misunderstanding going on here, translating the proof to Lean is, well... a translation task. Formalizing the proof in a way that's useful (breaks the proof down into relatively independent blocks that can be used for other maths and, importantly, understood individually) is a quite bigger, more creative endeavor. Not sure if LLMs would be able to do it, maybe yes?
It wasn't clear that LLMs were up to a Lean translation task of this scale until now. The background required to formalize the FLT proof was tremendous, so many people assumed we would have to wait until all of that was formalized in Lean before we could ask it to formalize Wiles' proof. Now it seems like almost any mathematics paper we can ask an LLM to formalize, including all necessary background, and it can just do it.
note that this is exactly analogous to an LLM being able to slop code some demo, but not build something more generally useful/maintainable (say something suitable for inclusion in a standard library).
I wonder, at the point of such a simple thing as the Saheed (there are videos online of some of its electronics, not saying it's bad, indeed it's cheap and effective, but it's dirt simple), does the USA really need to reverse engineer it? Is it just a way to prevent project management turning the thing into a million dollar per unit thing?
People calling it "reverse engineered" are not entirely correct.
The "Low accuracy, low speed, drone" concept has not changed since the V1 was invented by the Germans. Who then went ahead and built a more modern one back in the 80s. It should look very familiar:
It has all the bells and whistles you can recognize: GPS guidance, shitty small piston engine, lumbering speed, launched from a box truck using a small booster rocket.
See, the funny part is that the project was considered a failure because they were designed as anti-radar munitions, to just hang around until a radar transmitted and home in and destroy it. But that part of the project never figured out a good seeker.
It's just convergent evolution. That's what the design requirements imply.
Makes sense, I presume any defense corporation (even small ones of the drone manufacturer style) could get one of these running in a few months if needs arise.
Now, for the defense model of "western" nations (once again, not saying this is a bad thing nor wrong), a dumb warhead that just lands wherever and explodes makes no sense, no tactic would be enabled by it, so I guess the natural course of actions is you get heavier guidance requirements (case in point, radar homing), then you get operation in GPS-denied environment, then some other part of the army decides it needs to be carried on fighter jets, and another team wants it carried on frigates, and suddenly you have developed a million-€ loitering munition instead of a 10k€ V1 tactical-analogue!
I'm a bit of a victim to this mindset. I don't particularly play many video games, except the occasional one that clicks, but love making small game experiences and similar. I find that gamedev programming is very fun and engaging. Nonetheless, I don't think that I have the combination of skills and creativity (nor game knowledge) to make a game as great as those that have clicked for me in the past ;)
I'm running my remarkable on some ancient software version, and honestly for my use case (reading textbooks and occasional note taking) the old version is perfectly fine.
I don't connect it to the internet, just use the awesome RCU software (paid, but distributed with source code) to move stuff between it and my computer. I presume if I were to try to update it, I'll find the same fate! About exporting, the notebook format is relatively simple, I wrote a very bare-bones software that's able to convert the notebooks to PDF in a few hundred lines of Nim, or you could just use the integrated web UI.
You can't use a solar sail for this, but if you use lasers, you can get a few newtons / GW of incident laser power. Sci-fi stuff but if you can make a very very light reflector that can somehow be cooled (microscopic IR dipoles come to mind), and a very very focused and powerful laser, you can go a long way. Not sure what the purpose of moving a thin metalized foil at a fraction of lightspeed would be, though :)
Yeah, many of the theoretical solar sail ideas fall down on what I consider a useful "probe" is, and what it can mass. As mentioned in my other comment, if you define the "probe" to be "a single particle" we /already/ do this all the time in particle accelerators. But it's clearly not a useful "probe" I believe the original thought experiment implied. A few hundred grams of super thin solar sail material is still very much in the "Not A Probe" definition in my mind.
Plus even the best laser dispersion quickly gets significant at the distances required to give the sail the time to accelerate at such a low thrust.
reply