fidzu : geek

CNN reports: The popular theory that comets were crucial in kick-starting life on Earth billions of years ago may not hold up, according to new computer simulations that counter decades of scientific thinking. The finding suggests the fragile organic molecules supposedly carried by the icy objects would have been destroyed on impact, upending an established origin of life theory that dates back to at least 1961 [with earlier versions postulated in 1908]... Early in its history - over 4 billion years ago - Earth may have experienced a period of heavy bombardment from more than 100,000 comets larger than 100 meters (328 feet), according to the new study, published Wednesday in the journal Scientific Reports. Those impacts, however, were mostly too heavy for life-starting molecules to withstand. The team used the latest models of comet formation and evolution to simulate this early planetary period 100,000 times. "Given what we know about surface environments on the early Earth, on average, our simulations found that there were no successful impacts," said lead study author Richard Anslow, who conducted the research while completing his doctorate at the Institute of Astronomy of the University of Cambridge in the United Kingdom... "The typical velocities of these comets when they impact the Earth meant that actually very few, if any, would have been able to deliver intact organic molecules, so comets actually don't seem to be as useful for prebiotic chemistry as was previously thought," Anslow said. More precisely, 54% of the simulations showed no impact at all, while the remaining 46% had at least one and a "tiny minority" returned up to three collisions, Anslow said. "We can't rule out confidently that there was never a successful impact - there could have been one of these fluke impacts." However, such flukes had to occur in a "perfect location" that already met several important conditions, including the presence of liquid water and other chemicals needed to support life. That combination makes the overall process unlikely, he added. The article notes his argument that even if a successful impact occurred, it's unlikely an important chemical like hydrogen cyanide (HCN) could survive the impact, and would've dissolved in an ocean impact. Plus, "many other precursor molecules are also needed, such as compounds that contain phosphorus and sulfur, but these are not routinely found in comets, Anslow said." An alternative cosmic source of organic material could have been asteroids, which typically struck Earth more slowly and in greater numbers. Anslow pointed to recent findings on samples from asteroids Bennu and Ryugu, which contain the majority of protein-building amino acids. The recent study also raises another intriguing possibility: While Earth may not have had the ideal conditions to foster HCN from comet impacts, ancient Mars might have been better suited. "Because Mars is much smaller than Earth and further away from the sun, the typical impact velocity of comets is much lower, so while these impacts on Earth were destroying most of the HCN, this wasn't the case so much for Mars," Anslow said. This idea could add another dimension to the long-standing question of whether the red planet once supported life. While the authors closely analyzed how HCN could have survived comet impact, the chemical may have undergone reactions before the icy bodies entered Earth's atmosphere, said Queenie Chan, an associate professor of Earth sciences at Royal Holloway University of London, who was not involved with the study. This process could have created biologically important compounds, such as those protein building blocks, that are less volatile and more likely to survive.

Read more of this story at Slashdot.

31 Oct 2026 9:50pm GMT

BBS-era "door" games are preserved by the site Break Into Chat, along with their history. Now the site's actually traced the origins of several ANSI art screens in the 1980s and "how different people later transformed the original images," starting from one of the most popular bulletin board systems in St. Louis, Missouri. Slashdot reader Kirkman14 writes: "Fire Escape" was curator of the authoritative list of bulletin board systems in St. Louis's area code and sysop of the area's most popular board. Like many sysops of that time, Fire Escape enlivened her bulletin board by finding and repurposing older ANSI art. Eventually her BBS had 18 different logon screens in its rotation, many of which featured flames or mushroom clouds or made liberal use of red and yellow. Break Into Chat follows the trail: Some, maybe even most, of Fire Escape's logon screens had actually been adapted from old school "public domain" ANSI art drawn in the late 1980s and early 1990s by folks such as Michael C. Ling, Lora Ruffner (aka "Ebony Eyes") and Violet Stymacks.... Stymacks was unusually generous with her ANSI art. When she first began drawing, she combed through Fidonet node lists looking for bulletin boards with interesting or inspiring names. When she found one, she would draw an ANSI screen that fit the board's theme, then send it to the sysop. Eventually, sysops began seeking her out, too. By late 1990, she claimed that 500 bulletin boards were using her screens. Three years later, that total had tripled, according to Boardwatch . I believe it - I have located more than 1,100 of her pieces so far. She was so prolific that it would be surprising if she hadn't reused or remixed her own work over the years... [D]id they intend for other people to do so? Or would they have considered such borrowing or adapting as "ripping" or just plain "stealing"? These questions have dogged the BBS, ASCII art, and ANSI art scenes from the beginning. A freelance writer named Patrick Grote grappled with this ethical dilemma in 1990. He had begun to publish archives of ANSI art that he had collected from various public messageboards and networks. But what were people allowed to do with the ANSI screens in these collections? Was it okay to modify them? "Tough call," Grote said. "I know some people copyright their screens by inserting a little '(C)' on it," Grote wrote in a README file included in these collections. "Is this 'true' copyrighting? I would say yes, but then again, I don't feel like having any legal action taken against me for using an ANSI screen. In my opinion, I would say leave the ones that say '(C)' alone, but make every effort to contact the artist and ask for permission...." When I corresponded with Fire Escape this year, she admitted her memory wasn't what it used to be, but felt certain that she had not asked any artists for permission because she didn't know who they were or how to reach them. "I figured if anyone had an issue, I'd just remove the screen," she said. "But no one ever said anything about it."

Read more of this story at Slashdot.

31 Oct 2026 8:50pm GMT

Companies like Google, Netflix, TikTok, and Meta may soon owe the French government, reports Tom's Hardware: France has approved a proposed tax that aims to tax the amount of internet data per gigabyte sent to French users in the country... According to minutes released by the National Assembly, members voted 11-10 in support of the motion on October 30 - which now means the new law has been added to the country's next budget, despite major opposition from the government side and the finance committee rapporteur. The latest amendment, introduced by socialist lawmaker Laurent Lhardit, could see content providers pay €0.055 (roughly $0.06) to the government for every gigabyte of content distributed to French users. With approximately 154 million users and counting in France, the proposal's authors say such a tax could generate around €10 billion ($11.2 billion) in annual revenue for the government. The said proposal, though yet to be passed as it must survive further parliamentary scrutiny, aims at companies that generate substantial internet traffic as opposed to taxing their advertising revenue, profits and subscriptions. Its explanatory notes particularly mention Google, Meta, Netflix, Amazon, and content delivery network Akamai as major potential contributors. Notably, TikTok and other similar platforms could fall under this broader scope depending on how these rules are applied. Internet service providers, including Orange Free and Liad, would be required to measure the volume of data and identify the companies responsible for sending it to French users. The Data will then be collected and submitted quarterly to France's tax administration under the supervision of telecommunications watchdog Arcep. The measure becomes law if it clears the remaining stages of France's budget process, the article points out, "with parliament scheduled to vote on the budget's first section in early November." "VideoLAN, the French nonprofit organization behind the VLC media player, warned that the proposed levy could cost it more than €1 million annually," reports CircleID. "Its response illustrates how traffic-based taxation could affect organizations distributing large volumes of data without corresponding commercial revenue."

Read more of this story at Slashdot.

31 Oct 2026 7:50pm GMT

A long flight home from feeding grounds messes with birds' internal clocks.

31 Oct 2026 11:15am GMT

The regulator says Tavneos was approved on the basis of manipulated study data. Should patients still have access to it?

31 Oct 2026 11:02am GMT

Sculpt OS 26.10 brings quite a few new features, like scalable cursors, support for UK keyboards, better webcam support, and more, but the real meat of this release is much tastier. First, Sculpt 26.10 is the first version based on Genode's custom microkernel instead of relying on a 3rd-party kernel. This kernel - designed from the ground up for the needs of Genode and Sculpt OS in particular - is not only more "micro" than any other of the microkernels supported by Genode, it also solves long-standing deficiencies concerning CPU scheduling and kernel-memory management. Sculpt OS finally stands on Genode's own footing! Finally, Sculpt OS 26.10 pays tribute to this year's overall theme of "building bridges" by featuring our software development kit (Goa SDK) running directly on Sculpt OS without virtualization. This entails a wealth of tooling including GCC, Binutils, Git, Sequoia, Expect, Curl, man, Make, and CMake having landed on Genode. Although still young and not time-tested yet, it shows what's possible today and allows us developers to gradually shift more and more development routine into this self-hosted environment, stressing the general-purpose qualities of Genode and motivating further optimizations. ↫ Sculpt OS release 26.10 announcement This new release also completes the transition from XML to Genode's own HID language for configuration, moves from VirtualBox 6 to 7, and upgrades a whole slew of its Linux-based drivers

31 Oct 2026 8:02am GMT

Raymond Chen published another story from the Windows development trenches, this time about what happens when you hold down the power button. If you hold a PC's power button for 12 seconds, it will turn off at the hardware level without notifying the operating system. This is a safety feature so that you can turn of the computer even if the operating system's "Shut down" command isn't working. After eight seconds of the power button being held down, the Windows kernel realizes that the user is trying to do a force-power-off of the system, and it quickly takes a kernel dump that can be uploaded to the Windows Error Reporting service the next time you turn the system on. ↫ Raymond Chen I'm a bit confused by these numbers, because I have never seen a PC take this long to power off when holding down the power button; usually it takes only a few seconds to do so, meaning Windows would never generate said kernel dump. I tried reading through the various ATX specification documents to find more information on this, but then I remembered I'm not an electrical engineer so I have no idea what I'm looking at. The baseline is that ATX always provides standby power to the motherboard, and pressing the power button shorts the power button pin to ground, telling the PSU to power on fully. Pressing the power button if the computer is running tells the operating system to initiate a shutdown (although you can change this behaviour), but if you hold the button down for a certain number of seconds, it forces a power-off. So far, so good; basic information. It seems that the length of time you need to hold down the power button to force a power-off is dependent on the motherboard in question, handled by a microcontroller or some other IC. Virtually every source I can find says this timing is set to about 4-5 seconds, which is quite a bit shorter than the number of seconds given by Chen. Perhaps motherboard manufacturers consider the 12 seconds to be too long, and just do their own thing, regardless what the ATX specification suggests? What further complicates matters is that Chen details how the kernel dumps created after pressing the power button for 8 seconds do, in fact, get sent to Microsoft once the computer turns on again. In fact, he is one of the people who gets to see these dumps and respond to them, so obviously they are indeed rolling in. Does this mean there's a huge number of computers out there that require you to hold down the power button for 12 seconds to force a shutdown that nobody's ever seen? These emergency kernel dumps are internally classified as "long power button hold" (LPBH) failures. One of the pieces of information recorded in these emergency kernel dumps is whether the screen consists entirely of black pixels. Those failures are sub-classified as "black screen LPBH", and they go to a special virtual team for analysis. (I happen to be a member of this black screen LPBH team.) ↫ Raymond Chen What's going on here? Obviously, I'm not going to doubt Chen, so there must be something here I don't quite understand or that I'm missing. The ATX specification might suggest 12 seconds, but could Windows perhaps adapt its kernel dump behaviour - dumping much sooner than 8 seconds - based on the motherboard it's running on, maybe through information provided by the chipset drivers? I would love it if someone more knowledgeable than me can help us unravel this small mystery.

31 Oct 2026 7:54am GMT

From curl 8.12 through 8.16, config files could slice variable values and include other config files without an explicit depth cap. Together, these features let curl simulate any two-counter Minsky program. Under the usual idealization of unbounded strings and resources, this construction was Turing-complete. Curl 8.17.0 added a five-level include cap that breaks this reduction. ↫ Nicolas Seriot Neat.

31 Oct 2026 7:10am GMT

The space agency solicited ideas for reboosting Hubble four years ago, but they didn't go anywhere.

31 Oct 2026 12:07am GMT

This is a story of how we got from something like this: Failed to deserialize BUILDINFO file: Parser failed with the following error: unknown ^ invalid makepkg build environment option expected `buildflags`, `ccache`, `check`, `color`, `distcc`, `sign`, `makeflags` To this: When the ALPM project started, the goal was fairly simple: Better tooling to interact with the low-level plumbing of Arch Linux Package Management (ALPM). This meant binaries to read/write individual file types, better error messages, extensive specifications and of course exports to common dataformats like JSON. The thing is, although some of us already had experience with low-level dataframe parsing, …

08 Oct 2026 12:00am GMT

Over the last few weeks, we have been doing research on the integration of our official distribution packages when installed on a target system. In this context we have been looking at the current uses of alpm-install-scriptlet(5) files and alpm-hooks(5) in around 120 package source repositories (alpm-source-repo(7)) to better understand the underlying functionality and use-cases these two integrations offer and target. In this article we are going to look at how these two systems work, how Arch Linux is currently using them and attempt to provide suggestions for when to use which. Learning about alpm-hooks(5) and alpm-install-scriptlet(5) files …

09 Aug 2026 12:00am GMT

Good morning from JetBrains Berlin office!

01 Jun 2026 12:00am GMT