Submission + - Amazon Vine Review Recasts 'Coding Kids' Exposé as Learn-to-Code Primer for 1

theodp writes: "Amazon Vine," the e-tailer explains, "is an invitation-only program which selects the most insightful reviewers in the Amazon store to serve as Vine Voices. Vine Voices have the unique opportunity to order items free of charge and share their product experiences with Amazon customers to help them make informed buying decisions. [...] When customers see a review with the special Vine badge, they can trust that they're getting an honest, unbiased opinion from a real customer just like them."

So, how well does the reality live up to the promise? In the case of the new book Coding Kids: Big Tech's Battle to Remake Public Schools, not so much. Described by the publisher as "the inside story of how Big Tech catalyzed, co-opted, and ultimately came to capture computer science and AI education in America" ("Fourth graders doing Google-branded coding lessons. Amazon schooling seventh graders on its warehouse robots. Advanced Placement computing courses from Microsoft and Apple."), the top review selected by Amazon informs customers that the book is a 'good introduction to coding.'

"I really enjoyed Coding Kids," writes the 'trusted' Amazon Vine reviewer. "What stood out to me most was how the book takes something that can sound complicated—computer coding—and makes it feel approachable and even fun. As I was reading it, I found myself thinking that this is exactly the kind of book that could help a child become interested in technology without feeling overwhelmed by it. I particularly liked the way it encourages kids to be curious, experiment, and solve problems on their own. That was probably my favorite part because it shows that coding isn’t just about computers—it’s also about creativity and learning how to think differently. I would definitely recommend Coding Kids to parents, grandparents, or teachers looking for a good introduction to coding. I came away from the book thinking that it could genuinely spark a child’s interest in technology and give them the confidence to explore something new."

While likely just another example of Hanlon's Razor ("Never attribute to malice that which is adequately explained by stupidity."), the recasting of an investigative nonfiction book that casts a critical eye at Amazon's influence on K-12 education as a learn-to-code primer for children doesn't exactly instill trust in the Amazon Vine program or Amazon's 'Top Reviews' selection process. More on-point book reviews of Coding Kids can be found at the Washington Independent Review of Books ("Turns out, Silicon Valley isn’t especially altruistic.") and Science ("Big Tech’s crusade to get kids coding is more self-interested than it first appears").

Submission + - From Palm OS to Foldable Phones (linkedin.com)

ardiri writes: Long-time Slashdot reader Aaron Ardiri, whose Palm OS work has appeared here a few times over the years, has revisited a mobile architecture he developed more than 20 years ago after this week's renewed attention on fold-able phones.

MedHand International began developing medical reference software for Palm OS in 2000, eventually supporting Palm OS, Windows Mobile, Windows and Mac OS X. Because medical publishers supplied content in wildly different formats, MedHand developed its own canonical XML representation—“MedHand XML”—and separated structured content from its presentation.

That work resulted in a patent filed in 2005 describing components, containers, a layout manager, hierarchical information and display-dependent presentation. Its diagrams explicitly show the same information hierarchy being presented differently on a mobile phone, PDA and desktop display.

The interesting comparison isn't that MedHand somehow “invented the foldable phone”—it didn't—but that modern foldables create essentially the architectural problem the software was designed to handle: the underlying information remains unchanged while the available display environment changes substantially, requiring the presentation and visible information hierarchy to adapt.

Ardiri has written a retrospective comparing the 2005 architecture with modern adaptive mobile interfaces. There's also an amusing historical circle: MedHand International built its own XML publishing pipeline before EPUB became an industry standard, while Ardiri has just released his autobiography and Inside the Machine as EPUBs—including on Apple Books.

So how many supposedly “new” computing problems are really old architectural problems waiting for the hardware to catch up?

Submission + - 39 New Passkey Authentication Compromises + Bad UI = Passwords on Paper? (bleepingcomputer.com)

eqteam writes: We all saw this coming: "There are now at least 39 publicly documented methods, attack paths, research techniques, and exploitation scenarios involving passkeys and the infrastructure around them. Many already have working proof of concept tools or published research showing exactly how the techniques can be executed. Some are already appearing in real world attack patterns."

According to the above-quoted (sponsored) Bleeping Computer article: "A modern passkey authentication ceremony crosses an extraordinary number of trust boundaries. It can involve the web application, browser, operating system, password manager, cloud synchronization service, mobile device, Bluetooth transport, account recovery system, enrollment process, help desk, and ultimately the human being approving the authentication.

Researchers are attacking almost every one of those layers. Published techniques now include assertion mining, assertion replay, circuit breaker attacks, assertion phishing, browser hooking, assertion capture, challenge injection, detour replay, user verification manipulation, and user presence manipulation."

Furthermore, intrepid users who enable Passkey authentication end up turning it off because they can't figure out how to make it work across devices (thanks to confusing implementations that aren't consistent across platforms and operating systems). Additionally, Passkey adoption is pretty slow, with only 872 websites implementing Passkey authentication per this research paper titled The State of Passkeys: Studying the Adoption and Security of Passkeys on the Web presented at the 2026 USENIX Security Symposium.

With 2FA being deprecated by many large orgs and biometric authentication options proving to look like Swiss cheese, what are we to do besides going back to writing down passwords on paper while we wait for the technology to get better?

Slashdot Top Deals