Groups | Search | Server Info | Login | Register
Groups > sci.electronics.design > #739799
| From | Jan Panteltje <alien@comet.invalid> |
|---|---|
| Newsgroups | sci.electronics.design |
| Subject | Re: Raspberry Pi goes to war |
| Date | 2026-01-28 06:26 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <10lca6p$6tma$1@dont-email.me> (permalink) |
| References | <un1inkd3bjmum40nn6tre6djsb31v1v1ap@4ax.com> |
>john larkin <jl@glen--canyon.com>wrote: >> >https://www.nytimes.com/2025/12/31/magazine/ukraine-ai-drones-war-russia.html Reminds me of my drone experiments: https://panteltje.nl/panteltje/quadcopter/index.html It is all too simple I did the auto-tracking too Not even a raspberry needed, just some lines of PIC asm https://panteltje.nl/pub/target_tracking_test_IMG_4688.JPG that is a camara on 2 servos, horizontal and vertical no servos needed in the drone case, just steer it. What's new? Good thing I open-sourced it, but then China has had all that stoff for many years. Where will it go? This from alt.survival today: >Colon Powell <Colon.Powell@tutanato.com>wrote: >>Kind of weird that these billionaire tech moguls are warning the masses >of how dangerous what the billionaires are funding is. > >https://www.rt.com/news/631622-anthropic-ai-unimaginable-power/ > >The CEO of leading AI company Anthropic, Dario Amodei, has issued an >ominous public warning that humanity is on the cusp of being handed >“almost unimaginable power,” for which it is dangerously unprepared. > >In a nearly 20,000-word essay titled “The Adolescence of Technology,” >Amodei sketches a near-future where AI systems vastly more capable than >any Nobel laureate or statesman could be at everyone’s disposal within >the next few years. A critical and accelerating factor, Amodei reveals, >is that AI development is now creating a self-reinforcing feedback loop. > >“Because AI is now writing much of the code at Anthropic, it is already >substantially accelerating our progress in building the next generation >of AI systems,” he writes, warning that the company is close to “a point >where the current generation of AI autonomously builds the next.” > >The deepfake threat is reshaping global politicsREAD MORE: The deepfake >threat is reshaping global politics >He argues that without decisive and careful action, this technology >could lead to catastrophic risks ranging from mass job displacement to >human extinction. Other existential dangers include the potential for “a >global totalitarian dictatorship” enabled by AI-powered surveillance, >propaganda and autonomous weapons. > >Amodei also details “autonomy risks,” where AI systems could “go rogue >and overpower humanity” – noting that this danger would not even require >a sci-fi army of physical robots. The essay chillingly observes that >“plenty of human action is already performed on behalf of people whom >the actor has not physically met.” > >Among the most urgent threats, Amodei highlights the potential for AI to >drastically lower the barrier to creating biological and other weapons >of mass destruction. > >‘Catastrophic outcomes’ could accompany rise of advanced AI – Google >DeepMind CEOREAD MORE: ‘Catastrophic outcomes’ could accompany rise of >advanced AI – Google DeepMind CEO >“A disturbed loner can perpetrate a school shooting, but probably can’t >build a nuclear weapon or release a plague,” he writes. A powerful AI, >however, would make “everyone a PhD virologist who can be walked through >the process of designing, synthesizing, and releasing a biological >weapon step-by-step.” > >In a worst-case scenario, he warns a powerful AI could theoretically >guide the creation of a synthetic pathogen capable of “destroying all >life on Earth.” > >As one of the key industry leaders, whose company is a chief rival to >OpenAI, Amodei calls for “surgical” regulation, starting with >transparency laws, to build necessary guardrails. > >READ MORE: ‘Superintelligent’ AI could end humanity – tech icons >“Humanity needs to wake up,” Amodei concludes, framing the coming years >as a critical test of civilization’s maturity. With the technology >itself now fueling its own breakneck evolution, he urges a collective >response to steer the “glittering prize” of AI away from potential ruin. > >You can share this story on social media:
Back to sci.electronics.design | Previous | Next — Previous in thread | Find similar
Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-27 10:43 -0800
Re: Raspberry Pi goes to war bitrex <user@example.net> - 2026-01-27 15:22 -0500
Re: Raspberry Pi goes to war wmartin <wwm@wwmartin.net> - 2026-01-27 12:27 -0800
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-27 13:46 -0800
Re: Raspberry Pi goes to war bitrex <user@example.net> - 2026-01-27 17:19 -0500
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-27 14:45 -0800
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-01-29 02:54 +1100
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-28 08:13 -0800
Re: Raspberry Pi goes to war bitrex <user@example.net> - 2026-01-28 14:21 -0500
Re: Raspberry Pi goes to war Joe Gwinn <joegwinn@comcast.net> - 2026-01-28 16:02 -0500
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-01-29 13:41 +1100
Re: Raspberry Pi goes to war bitrex <user@example.net> - 2026-01-28 22:59 -0500
Re: Raspberry Pi goes to war Joe Gwinn <joegwinn@comcast.net> - 2026-01-29 17:46 -0500
Re: Raspberry Pi goes to war Coileán Pól Nioclás de Ghlostéir <thanks-to@Taf.com> - 2026-01-29 14:41 +0100
Re: Raspberry Pi goes to war Lasse Langwadt <llc@fonz.dk> - 2026-01-29 19:03 +0100
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-01-30 15:25 +1100
Re: Raspberry Pi goes to war liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-30 10:15 +0000
Re: Raspberry Pi goes to war Don Y <blockedofcourse@foo.invalid> - 2026-01-30 04:03 -0700
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 00:12 +1100
Re: Raspberry Pi goes to war liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-30 13:25 +0000
Re: Raspberry Pi goes to war Don Y <blockedofcourse@foo.invalid> - 2026-01-30 07:03 -0700
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 16:35 +1100
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 00:09 +1100
Re: Raspberry Pi goes to war liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-30 13:43 +0000
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 02:34 +1100
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-01-29 13:25 +1100
Re: Raspberry Pi goes to war albert@spenarnc.xs4all.nl - 2026-01-29 12:18 +0100
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-29 05:00 -0800
Re: Raspberry Pi goes to war Jan Panteltje <alien@comet.invalid> - 2026-01-29 14:09 +0000
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-29 08:53 -0800
Re: Raspberry Pi goes to war Gerhard Hoffmann <dk4xp@arcor.de> - 2026-01-29 20:25 +0100
Re: Raspberry Pi goes to war Joe Gwinn <joegwinn@comcast.net> - 2026-01-29 18:18 -0500
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-29 16:53 -0800
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-01-30 15:49 +1100
Re: Raspberry Pi goes to war Jan Panteltje <alien@comet.invalid> - 2026-02-01 11:58 +0000
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-02-02 09:48 -0800
Re: Raspberry Pi goes to war Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2026-02-02 18:29 +0000
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-02-02 12:33 -0800
Re: Raspberry Pi goes to war Jan Panteltje <alien@comet.invalid> - 2026-02-03 05:50 +0000
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-02-03 07:56 -0800
Re: Raspberry Pi goes to war Jan Panteltje <alien@comet.invalid> - 2026-02-04 05:44 +0000
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-02-04 03:24 -0800
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-02-05 01:35 +1100
Re: Raspberry Pi goes to war Gerhard Hoffmann <dk4xp@arcor.de> - 2026-02-04 21:31 +0100
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-02-04 13:21 -0800
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-02-05 16:50 +1100
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-02-05 11:36 -0800
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-02-06 18:30 +1100
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-02-06 03:41 -0800
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-02-07 01:12 +1100
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-02-05 16:46 +1100
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-02-05 11:37 -0800
Re: Raspberry Pi goes to war Jan Panteltje <alien@comet.invalid> - 2026-02-06 06:18 +0000
Re: Raspberry Pi goes to war Jeroen Belleman <jeroen@nospam.please> - 2026-02-06 09:51 +0100
Re: Raspberry Pi goes to war Jan Panteltje <alien@comet.invalid> - 2026-02-06 12:30 +0000
Re: Raspberry Pi goes to war liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-02-05 09:14 +0000
Re: Raspberry Pi goes to war Don Y <blockedofcourse@foo.invalid> - 2026-02-05 04:39 -0700
Re: Raspberry Pi goes to war liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-02-05 14:30 +0000
Re: Raspberry Pi goes to war Don Y <blockedofcourse@foo.invalid> - 2026-02-05 08:36 -0700
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-02-06 02:07 +1100
Re: Raspberry Pi goes to war Jan Panteltje <alien@comet.invalid> - 2026-02-04 15:53 +0000
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-02-05 01:04 +1100
Re: Raspberry Pi goes to war Jan Panteltje <alien@comet.invalid> - 2026-02-04 15:58 +0000
Re: Raspberry Pi goes to war Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2026-02-03 16:23 +0000
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-02-03 09:03 -0800
Re: Raspberry Pi goes to war Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2026-02-03 17:47 +0000
Re: Raspberry Pi goes to war wmartin <wwm@wwmartin.net> - 2026-02-03 11:18 -0800
Re: Raspberry Pi goes to war Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2026-02-04 01:21 +0000
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-02-03 18:52 -0800
Re: Raspberry Pi goes to war Joe Gwinn <joegwinn@comcast.net> - 2026-02-03 13:40 -0500
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-02-03 23:38 +1100
Re: Raspberry Pi goes to war Jan Panteltje <alien@comet.invalid> - 2026-02-03 05:41 +0000
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-02-03 10:46 -0800
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-01-30 03:08 +1100
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-29 08:56 -0800
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-01-30 15:56 +1100
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-01-30 03:04 +1100
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-29 08:59 -0800
Re: Raspberry Pi goes to war Gerhard Hoffmann <dk4xp@arcor.de> - 2026-01-29 20:50 +0100
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-29 19:22 -0800
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-01-30 16:00 +1100
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-29 15:43 -0800
Re: Raspberry Pi goes to war Lasse Langwadt <llc@fonz.dk> - 2026-01-28 17:42 +0100
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-27 13:47 -0800
Re: Raspberry Pi goes to war bitrex <user@example.net> - 2026-01-27 17:31 -0500
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-27 14:42 -0800
Re: Raspberry Pi goes to war bitrex <user@example.net> - 2026-01-27 17:55 -0500
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-27 15:03 -0800
Re: Raspberry Pi goes to war bitrex <user@example.net> - 2026-01-27 19:04 -0500
Re: Raspberry Pi goes to war albert@spenarnc.xs4all.nl - 2026-01-29 12:24 +0100
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-29 10:43 -0800
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-01-30 16:07 +1100
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-30 11:45 -0800
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 16:51 +1100
Re: Raspberry Pi goes to war Don Y <blockedofcourse@foo.invalid> - 2026-01-29 23:03 -0700
Re: Raspberry Pi goes to war Gerhard Hoffmann <dk4xp@arcor.de> - 2026-01-28 00:18 +0100
Re: Raspberry Pi goes to war liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-28 11:57 +0000
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-28 08:19 -0800
Re: Raspberry Pi goes to war bitrex <user@example.net> - 2026-01-28 15:18 -0500
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-28 13:12 -0800
Re: Raspberry Pi goes to war bitrex <user@example.net> - 2026-01-28 16:54 -0500
Re: Raspberry Pi goes to war bitrex <user@example.net> - 2026-01-28 15:13 -0500
Re: Raspberry Pi goes to war Don Y <blockedofcourse@foo.invalid> - 2026-01-27 15:32 -0700
Re: Raspberry Pi goes to war bitrex <user@example.net> - 2026-01-27 17:44 -0500
Re: Raspberry Pi goes to war Don Y <blockedofcourse@foo.invalid> - 2026-01-27 15:55 -0700
Re: Raspberry Pi goes to war bitrex <user@example.net> - 2026-01-27 19:13 -0500
Re: Raspberry Pi goes to war Joe Gwinn <joegwinn@comcast.net> - 2026-01-27 19:53 -0500
Re: Raspberry Pi goes to war Don Y <blockedofcourse@foo.invalid> - 2026-01-27 20:30 -0700
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-01-29 01:56 +1100
Re: Raspberry Pi goes to war albert@spenarnc.xs4all.nl - 2026-01-29 12:29 +0100
Re: Raspberry Pi goes to war Don Y <blockedofcourse@foo.invalid> - 2026-01-29 23:09 -0700
Re: Raspberry Pi goes to war liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-30 13:25 +0000
Re: Raspberry Pi goes to war Don Y <blockedofcourse@foo.invalid> - 2026-01-30 07:07 -0700
Re: Raspberry Pi goes to war john larkin <jl@glen--canyon.com> - 2026-01-30 11:49 -0800
Re: Raspberry Pi goes to war Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 02:40 +1100
Re: Raspberry Pi goes to war wmartin <wwm@wwmartin.net> - 2026-01-30 11:23 -0800
Re: Raspberry Pi goes to war Don Y <blockedofcourse@foo.invalid> - 2026-01-31 01:17 -0700
Re: Raspberry Pi goes to war wmartin <wwm@wwmartin.net> - 2026-01-31 12:19 -0800
Re: Raspberry Pi goes to war Don Y <blockedofcourse@foo.invalid> - 2026-01-31 18:36 -0700
Re: Raspberry Pi goes to war liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-30 13:25 +0000
Re: Raspberry Pi goes to war Lasse Langwadt <llc@fonz.dk> - 2026-01-28 17:38 +0100
Re: Raspberry Pi goes to war bitrex <user@example.net> - 2026-01-28 17:19 -0500
Re: Raspberry Pi goes to war bitrex <user@example.net> - 2026-01-28 17:36 -0500
Re: Raspberry Pi goes to war Jan Panteltje <alien@comet.invalid> - 2026-01-28 06:26 +0000
csiph-web