H_Fisher writes: Only one copy exists of the Wu-Tang Clan album Once Upon a Time in Shaolin, and it was owned by "Pharma Bro" Martin Shkreli. Now, NPR reports that this album has been sold by the U.S. government to an unnamed buyer in order to pay Shkreli's civil forfeiture judgment following his conviction for securities fraud. The album, which was originally sold for $2 million, exists only as one physical CD copy. It was seized along with other assets in 2018, and while the sale price and buyer weren't identified, Shkreli's attorney says that his client has now repaid the $7.4 million forfeiture judgement.

First Major League Baseball experimented with automated umpiring of balls and strikes in the minor leagues.

Now the Verge reports they're trying a time-saving tactic that might also make it harder to cheat: Baseball has a sign stealing problem — or at least, a technological one, seeing how reading another team's pitches is technically legal, but using Apple Watches or telephoto cameras and then suspiciously banging on trash cans is very much not. But soon the MLB may try fighting fire with fire: on August 3rd, it plans to begin testing an encrypted wireless communication device that replaces the traditional flash of fingers with button taps, according to ESPN.

The device, from a startup called PitchCom, will be tested in the Low-A West minor league first. As you'd expect from something that's relaying extremely basic signals, it's not a particularly complicated piece of kit: one wristband transmitter for the catcher with nine buttons to signal "desired pitch and location," which sends an encrypted audio signal to receivers that can squeeze into a pitcher's cap and a catcher's helmet.

The receivers use bone-conduction technology, so they don't necessarily need to be up against an ear, and might theoretically be harder to eavesdrop on. (Bone conduction stimulates bones in your head instead of emitting audible sound.)
"MLB hopes the devices will cut down on time spent by pitchers stepping off the rubber and changing signals," reports the Associated Press, noting another interesting new rule. "A team may continue to use the system if the opposing club's device malfunctions."

But don't worry about that, reports ESPN: Hacking the system, the company says, is virtually impossible. PitchCom uses an industrial grade encryption algorithm and transmits minimal data digitally, making it mathematically impossible for someone to decrypt intercepted transmissions, according to the company.

Slashdot reader Hmmmmmm shares a blog post from Stockfish announcing a lawsuit against ChessBase: The Stockfish project strongly believes in free and open-source software and data. Collaboration is what made this engine the strongest chess engine in the world. We license our software using the GNU General Public License, Version 3 (GPL) with the intent to guarantee all chess enthusiasts the freedom to use, share and change all versions of the program. Unfortunately, not everybody shares this vision of openness. We have come to realize that ChessBase concealed from their customers Stockfish as the true origin of key parts of their products (see also earlier blog posts by us and the joint Lichess, Leela Chess Zero, and Stockfish teams). Indeed, few customers know they obtained a modified version of Stockfish when they paid for Fat Fritz 2 or Houdini 6 -- both Stockfish derivatives -- and they thus have good reason to be upset. [ChessBase released Fat Fritz 2, described on their website as the "new number 1" chess engine "with a massive new neural network, trained by Albert Silver with the original Fat Fritz." They advertise Fat Fritz 2 as using novel strong ideas compared to existing chess engines, but in reality Fat Fritz 2 is just Stockfish with a different neural network and minimal changes that are neither innovative nor appear to make the engine stronger.] ChessBase repeatedly violated central obligations of the GPL, which ensures that the user of the software is informed of their rights. These rights are explicit in the license and include access to the corresponding sources, and the right to reproduce, modify and distribute GPLed programs royalty-free.

In the past four months, we, supported by a certified copyright and media law attorney in Germany, went through a long process to enforce our license. Even though we had our first successes, leading to a recall of the Fat Fritz 2 DVD and the termination of the sales of Houdini 6, we were unable to finalize our dispute out of court. Due to Chessbase's repeated license violations, leading developers of Stockfish have terminated their GPL license with ChessBase permanently. However, ChessBase is ignoring the fact that they no longer have the right to distribute Stockfish, modified or unmodified, as part of their products. Thus, to enforce the consequences of the license termination, we have filed a lawsuit. This lawsuit is broadly supported by the team of maintainers and developers of Stockfish. We believe we have the evidence, the financial means and the determination to bring this lawsuit to a successful end. We will provide an update to this statement once significant progress has been made.

Since 2006 Baldrson (Slashdot reader #78,598) has been part of the team verifying "The Hutter Prize for Lossless Compression of Human Knowledge," an ongoing challenge to compress a 100-MB excerpt of Wikipedia (approximately the amount a human can read in a lifetime).

"The intention of this prize is to encourage development of intelligent compressors/programs as a path to Artificial General Intelligence," explains the project's web site. 15 years ago, Baldrson wrote a Slashdot post explaining the logic (titled "Compress Wikipedia and Win AI Prize"): The basic theory, for which Hutter provides a proof, is that after any set of observations the optimal move by an AI is find the smallest program that predicts those observations and then assume its environment is controlled by that program. Think of it as Ockham's Razor on steroids.
The amount of the prize also increases based on how much compression is achieved. (So if you compress the 1GB file x% better than the current record, you'll receive x% of the prize...) The first prize was awarded in 2006. And now Baldrson writes with the official news that this Spring another prize was claimed after reaching a brand new milestone: Artemiy Margaritov's STARLIT algorithm's 1.13% cleared the 1% improvement hurdle to beat the last benchmark, set by Alexander Rhatushnyak. He receives a bonus in proportion to the time since the last benchmark was set, raising his award by 60% to €9000. [$10,632 USD]

Congratulations to Artemiy Margaritov for his winning submission!

Long-time Slashdot reader RoccamOccam shares "an interesting take on SQL and its issues from Jamie Brandon (who describes himself as an independent researcher who's built database engines, query planners, compilers, developer tools and interfaces).

It's title? "Against SQL." The relational model is great... But SQL is the only widely-used implementation of the relational model, and it is: Inexpressive, Incompressible, Non-porous. This isn't just a matter of some constant programmer overhead, like SQL queries taking 20% longer to write. The fact that these issues exist in our dominant model for accessing data has dramatic downstream effects for the entire industry:

- Complexity is a massive drag on quality and innovation in runtime and tooling
- The need for an application layer with hand-written coordination between database and client renders useless most of the best features of relational databases

The core message that I want people to take away is that there is potentially a huge amount of value to be unlocked by replacing SQL, and more generally in rethinking where and how we draw the lines between databases, query languages and programming languages...

I'd like to finish with this quote from Michael Stonebraker, one of the most prominent figures in the history of relational databases:

"My biggest complaint about System R is that the team never stopped to clean up SQL... All the annoying features of the language have endured to this day. SQL will be the COBOL of 2020..."
It's been interesting to follow the discussion on Twitter, where the post's author tweeted screenshots of actual SQL code to illustrate various shortcomings. But he also notes that "The SQL spec (part 2 = 1732) pages is more than twice the length of the Javascript 2021 spec (879 pages), almost matches the C++ 2020 spec (1853) pages and contains 411 occurrences of 'implementation-defined', occurrences which include type inference and error propagation."

His Twitter feed also includes a supportive retweet from Rust creator Graydon Hoare, and from a Tetrane developer who says "The Rust of SQL remains to be invented. I would like to see it come."

Reactions are starting to come in for GitHub's new Copilot coding tool, which one site calls "a product of the partnership between Microsoft and AI research and deployment company OpenAI — which Microsoft invested $1 billion into two years ago." According to the tech preview page: GitHub Copilot is currently only available as a Visual Studio Code extension. It works wherever Visual Studio Code works — on your machine or in the cloud on GitHub Codespaces. And it's fast enough to use as you type. "Copilot looks like a potentially fantastic learning tool — for developers of all abilities," said James Governor, an analyst at RedMonk. "It can remove barriers to entry. It can help with learning new languages, and for folks working on polyglot codebases. It arguably continues GitHub's rich heritage as a world-class learning tool. It's early days but AI-assisted programming is going to be a thing, and where better to start experiencing it than GitHub...?"

The issue of scale is a concern for GitHub, according to the tech preview FAQ: "If the technical preview is successful, our plan is to build a commercial version of GitHub Copilot in the future. We want to use the preview to learn how people use GitHub Copilot and what it takes to operate it at scale." GitHub spent the last year working closely with OpenAI to build Copilot. GitHub developers, along with some users inside Microsoft, have been using it every day internally for months.

[Guillermo Rauch, CEO of developer software provider Vercel, who also is founder of Vercel and creator of Next.js], cited in a tweet a statement from the Copilot tech preview FAQ page, "GitHub Copilot is a code synthesizer, not a search engine: the vast majority of the code that it suggests is uniquely generated and has never been seen before."

To that, Rauch simply typed: "The future."

Rauch's post is relevant in that one of the knocks against Copilot is that some folks seem to be concerned that it will generate code that is identical to code that has been generated under open source licenses that don't allow derivative works, but which will then be used by a developer unknowingly...
GitHub CEO Nat Friedman has responded to those concerns, according to another article, arguing that training an AI system constitutes fair use: Friedman is not alone — a couple of actual lawyers and experts in intellectual property law took up the issue and, at least in their preliminary analysis, tended to agree with Friedman... [U.K. solicitor] Neil Brown examines the idea from an English law perspective and, while he's not so sure about the idea of "fair use" if the idea is taken outside of the U.S., he points simply to GitHub's terms of service as evidence enough that the company can likely do what it's doing. Brown points to passage D4, which grants GitHub "the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time." "The license is broadly worded, and I'm confident that there is scope for argument, but if it turns out that Github does not require a license for its activities then, in respect of the code hosted on Github, I suspect it could make a reasonable case that the mandatory license grant in its terms covers this as against the uploader," writes Brown. Overall, though, Brown says that he has "more questions than answers."
Armin Ronacher, the creator of the Flask web framework for Python, shared an interesting example on Twitter (which apparently came from the game Quake III Arena) in which Copilot apparently reproduces a chunk of code including not only its original comment ("what the fuck?") but also its original copyright notice.

OpenStreetMap, the Wikipedia-for-maps organisation that seeks to create a free and open-source map of the globe, is considering relocating to the EU, almost 20 years after it was founded in the UK by the British entrepreneur Steve Coast. From a report: OpenStreetMap Foundation, which was formally registered in 2006, two years after the project began, is a limited company registered in England and Wales. Following Brexit, the organisation says the lack of agreement between the UK and EU could render its continued operation in Britain untenable. "There is not one reason for moving, but a multitude of paper cuts, most of which have been triggered or amplified by Brexit," Guillaume Rischard, the organisation's treasurer, told members of the foundation in an email sent earlier this month.

One "important reason," Rischard said, was the failure of the UK and EU to agree on mutual recognition of database rights. While both have an agreement to recognise copyright protections, that only covers work which is creative in nature. Maps, as a simple factual representation of the world, are not covered by copyright in the same way, but until Brexit were covered by an EU-wide agreement that protected databases where there had been "a substantial investment in obtaining, verifying or presenting the data." But since Brexit, any database made on or after 1 January 2021 in the UK will not be protected in the EU, and vice versa.

There are some big announcements on DuckDuckGo's blog at SpreadPrivacy.com:

• "Our apps have been downloaded more than 50 million times over the last 12 months, more than all prior years combined...

• "Spurred by the increase in DuckDuckGo app usage, over the last 12 months our monthly search traffic increased 55% and we grew to become the #2 search engine on mobile in many countries including in the U.S., Canada, Australia, and the Netherlands. (StatCounter/Wikipedia)."

• "We don't track our users so we can't say for sure how many we have, but based on market share estimates, download numbers, and national surveys, we believe there are between 70-100 million DuckDuckGo users."

• "We're excited to start rolling out additional privacy features to our all-in-one privacy bundle. In a few weeks, DuckDuckGo Email Protection will be available in beta which will give users more privacy without having to get a new inbox. Later this summer, app tracker blocking will be available in beta for Android devices, allowing users to block app trackers and providing more transparency on what's happening behind the scenes on their device. Before the end of the year, we also plan to release a brand-new desktop version of our existing mobile app which people can use as a primary browser."

They're now pulling in over $100 million a year in revenue, "giving us the financial resources to continue growing rapidly," and at the end of 2020 they also landed a "mainly secondary investment" of over $100 million from a long list of investors (which included Tim Berners-Lee as well as Freada Kapor Klein and Mitch Kapor).

One thing they're doing with their money is spreading the word about online privacy — by purchasing billboard, radio, and TV ads in 175 different markets across the U.S., with more marketing blitzes now planned soon for Europe and other countries around the world.

Long-time Slashdot reader schwit1 shares an interesting report from Science Alert: Thunderstorms that roil across the Southern Great Plains of the US are amongst the strongest of such storms on Earth... Their intensity and frequency have been increasing, yet our best climate models still struggle to predict just how and when they'll arise.

To help refine climate models for the Southern Great Plains, paleoclimatologist Christopher Maupin from Texas A&M University and colleagues used oxygen and hydrogen isotopes to track the ferocity of past storms. Water molecules based on elements wielding an additional neutron or two tend to require a little more energy to vaporize, and release more energy as they condense. This leaves a clear signature in the ratios of isotopes separated by rainfall under various conditions. By comparing the results of analyses taken today with historic ratios of hydrogen and oxygen isotopes found trapped by stalactites in Texan caves, the researchers developed an accurate picture of weather events in the past...

Using another set of isotopes, this time measuring those of uranium and thorium, the team dated the stalactites and stalagmites to around the last Ice Age, 30-50 thousand years ago. Measuring the shifts in oxygen and hydrogen isotopes down their lengths allowed the researchers to see the storms cycled from weakly to strongly organized, roughly every thousand years. The more strongly organized the complex of storms becomes, the more intense and damaging they are. They discovered these changes in thunderstorm intensities coincided with well-known, abrupt shifts in global climate, known as Dansgaard-Oeschger events.

The researchers also found these intensity increases coincide with a reduction in rain in southwestern US and greater atmospheric upwelling in the Santa Barbara Basin area. They believe the observed pattern suggests an increased frequency or intensity of the giant global atmospheric waves that drive the weather, called Rossby waves, may be providing the extra lift needed to fuel these greater storms. "Modern anthropogenic climate forcing has increasingly favored an amplification of these synoptic factors," the team wrote in their paper.

"This work will help predict trends of storms in the future," explained geoscientist Courtney Schumacher.

The Record reports: The Wikimedia Foundation has banned the administrator of the Croatian version of Wikipedia after an investigation revealed that together with other admins, they edited and distorted content on the site with radical right views. This group had de-facto control of the website between 2011 and 2020, the Wikimedia Foundation said in a report published earlier this month... This included:

- Claiming that Hitler attacked Poland and started World War II after the Poles committed genocide against Germans.
- Redefining a World War II concentration camp as a labor camp...
- Pushing opinions that EU decision-making endangers Croatia's sovereignty.
- Claiming that the EU had used propaganda to trick Croatian citizens into joining the European Union...
Since 2013 the dubious edits had been spotted by users and the Croatian press, according to the article — but other Croatian Wikipedia editors failed, multiple times, to wrest away control of the site's moderation.

"The Wikimedia Foundation got involved last year after it was discovered that the administrator of Croatian Wikipedia had been using sockpuppet accounts to manipulate discussions and staff elections on the site..." The Wikimedia Foundation's report on the abuses of this team also points to possibly similar far-right-based editing on Wikipedia's Serbian version as well. This is the second major Wikipedia scandal in the past year. In September 2020, the Wikimedia Foundation said it found and banned a public relations firm that had created and used a network of sockpuppet accounts to edit the site on behalf of some of its customers.

Slashdot reader thegarbz writes: While a lot of focus has been on the TPM requirements for Windows 11, Microsoft has since updated its documentation to provide a complete list of supported processors. At present the list includes only Intel 8th Generation Core processors or newer, and AMD Ryzen Zen+ processors or newer, effectively limiting Windows 11 to PC less than 4-5 years old.

Notably absent from the list is the Intel Core i7-7820HQ, the processor used in Microsoft's current flagship $3500+ Surface Studio 2. This has prompted many threads on Reddit from users angry that their (in some cases very new) Surface PC is failing the Windows 11 upgrade check.
The Verge confirms: Windows 11 will only support 8th Gen and newer Intel Core processors, alongside [Intel's 2016-era] Apollo Lake and newer Pentium and Celeron processors. That immediately rules out millions of existing Windows 10 devices from upgrading to Windows 11... Windows 11 will also only support AMD Ryzen 2000 and newer processors, and 2nd Gen or newer [AMD] EPYC chips. You can find the full list of supported processors on Microsoft's site...

Originally, Microsoft noted that CPU generation requirements are a "soft floor" limit for the Windows 11 installer, which should have allowed some older CPUs to be able to install Windows 11 with a warning, but hours after we published this story, the company updated that page to explicitly require the list of chips above.

Many Windows 10 users have been downloading Microsoft's PC Health App (available here) to see whether Windows 11 works on their systems, only to find it fails the check... This is the first significant shift in Windows hardware requirements since the release of Windows 8 back in 2012, and the CPU changes are understandably catching people by surprise.

Microsoft is also requiring a front-facing camera for all Windows 11 devices except desktop PCs from January 2023 onwards.
"In order to run Windows 11, devices must meet the hardware specifications," explains Microsoft's official compatibility page for Windows 11.

"Devices that do not meet the hardware requirements cannot be upgraded to Windows 11."

The Hubble Space Telescope was launched into low-earth orbit in 1990 with an even older computer. Over the next 13 years it received upgrades and repairs from astronauts on five different visits from America's Space Shuttle.

But now in 2021, "NASA continues to work on resolving an issue with the payload computer on the Hubble Space Telescope," reports SciTechDaily — though "The telescope itself and science instruments remain in good health." The operations team will be running tests and collecting more information on the system to further isolate the problem. The science instruments will remain in a safe mode state until the issue is resolved...

The computer halted on Sunday, June 13. An attempt to restart the computer failed on Monday, June 14. Initial indications pointed to a degrading computer memory module as the source of the computer halt. When the operations team attempted to switch to a back-up memory module, however, the command to initiate the backup module failed to complete. Another attempt was conducted on both modules Thursday evening to obtain more diagnostic information while again trying to bring those memory modules online. However, those attempts were not successful.

Long-time Slashdot reader thegreatbob writes: The old RAD/content authoring system, ToolBook, appears to be entering the final phase of its EOL process. Sumtotal/Skillsoft (the current owner, under which meaningful development effectively ceased) 'may' refuse software activations after the end of 2021, and does not provide a format-compatible replacement. Similarly, they are halting their support services, and will not allow contracts to be renewed.

This may have significant ramifications for the education/training sector, and I have reason to believe that the body of the work dependent on this software is significantly larger than one might expect out of a wayward VisualBasic competitor from the 90s.

The software, which was offered for sale until relatively recently (I'm unsure of the date of cutoff), has not received an update since 2014, nor a major version update since 2011. As such, I'd like to increase the visibility of this particular EOL, in the hopes that interested parties will take notice and have an opportunity to begin the process of moving their courseware out of this format...

If one has never encountered this software before, it is "interesting", to say the least, as is the history of Asymetrix (one of Paul Allen's ventures) and later Sumtotal Systems, through 90s and early 2000s. If one does not care to look into it, it can be thought of as some sort of bizarro-world amalgam of features from Visual Basic and HyperCard.

Long-time Slashdot reader wildstoo writes: In a blog post on Thursday, GitHub security researcher Kevin Backhouse announced that Polkit, a Linux system service included in several modern Linux distros that provides an organized way for non-privileged processes to communicate with privileged ones, has been harbouring a major security bug for seven years.

The bug, assigned (CVE-2021-3560) allows a non-privileged user to gain administrative shell access with a handful of standard command line tools. The bug was fixed on June 3, 2021 in a coordinated disclosure.
"It's used by systemd," GitHub's blog post points out, "so any Linux distribution that uses systemd also uses polkit..."

"It's very simple and quick to exploit, so it's important that you update your Linux installations as soon as possible. Any system that has polkit version 0.113 (or later) installed is vulnerable. That includes popular distributions such as RHEL 8 and Ubuntu 20.04."

prz writes: PGP just hit its 30th birthday. Before 1991, the average person had essentially no tools to communicate securely over long distances. That changed with PGP, which sparked the Crypto Wars of the 1990s. "Here we are, three decades later, and strong crypto is everywhere," writes PGP developer Phil Zimmermann in a blog post. "What was glamorous in the 1990s is now mundane. So much has changed in those decades. That's a long time in dog years and technology years. My own work shifted to end-to-end secure telephony and text messaging. We now have ubiquitous strong crypto in our browsers, in VPNs, in e-commerce and banking apps, in IoT products, in disk encryption, in the TOR network, in cryptocurrencies. And in a resurgence of implementations of the OpenPGP protocol. It would seem impossible to put this toothpaste back in the tube."

He continues: "Yet, we now see a number of governments trying to do exactly that. Pushing back against end-to-end encryption. [...] The need for protecting our right to a private conversation has never been stronger. Many democracies are sliding into populist autocracies. Ordinary citizens and grassroots political opposition groups need to protect themselves against these emerging autocracies as best as they can. If an autocracy inherits or builds a pervasive surveillance infrastructure, it becomes nearly impossible for political opposition to organize, as we can see in China. Secure communications is necessary for grassroots political opposition in those societies."

"It's not only personal freedom at stake. It's national security," says Zimmermann. "We must push back hard in policy space to preserve the right to end-end encryption."

Slashdot reader AleRunner writes: Ubuntu has announced that, with immediate effect Ubuntu's IRC channels are moving to libera.chat. The move follows a "hostile takeover" of Ubuntu's namespace by Freenode's new management that appears to be happening to many other distributions including Gentoo as well as other projects that have used Freenode [including channels associated with the programming languages Raku, Elixir, and Haskell].

For Ubuntu, and many other FOSS projects, Freenode has long been one of the major official forms of communication... With IRC channels often used for important system advice, and project communication, this becomes not just an inconvenience but even a security problem. For this reason Ubuntu's replacement network, libera.chat has a more clearly open organisational structure than Freenode had before being taken over.
"All told, it appears something like 700 irc.freenode.net channels have been seized and re-permissioned," reports The Register, "supposedly because the channels mentioned Libera Chat in violation of Freenode's advertising policy."

Wednesday Freenode owner Andrew Lee posted a blog post explaining that "in retrospect, we should have handled the action of closing down channels slightly differently..."

"The intent of doing this was not an attempt of a hostile takeover nor hijack like many people are saying. Since certain projects were disrupting their users' ability to chat on freenode via mass kicks, force closures, spam, we decided to enact this policy in those places which were deemed in violation and could cause an issue later...

"We believe we should have done this in a much more communicative way to circulate the right message and keep things transparent which of course did not happen. As we move forward I'd like to fully assure you that we will be working in complete commitment to restore projects, namespaces and channels that were closed on accident as a part of this event and we welcome them to use freenode as before as their very own homebase.

"Lastly, there are no excuses for this, and I'm willing to admit that I was wrong with Tuesday's move and apologize for the inconvenience that may have caused."

So, what would it feel like to fall into a black hole? From a report: "Well, at the moment you crossed the horizon, you wouldn't feel anything -- there would be nothing dramatic," Peter Galison, co-founder of the Black Hole Initiative at Harvard University, says over the phone. Huh. Doesn't sound too bad. "But inevitably, you would be pulled towards the centre," he continues. "There's no going back; everything that falls into a black hole just keeps falling; there's no resisting that pull and things don't end well."

Ah. Go on. "Physicists have an expression called 'spaghettification' because if you were falling in feet first, your feet would be more attracted towards the centre than your head, and your sides would be pushed towards your middle and this process would extend and compress you." Right. So, terrifying, then. Especially when Galison adds with cosmic understatement: "In the long term that's not a good survival event." We are talking about his documentary film, Black Holes: The Edge of All We Know, four years in the making and available on Netflix from 1 June, which follows two scientific collaborations to understand the most mysterious objects in the universe. Among the highlights is being a fly on the wall as the late Stephen Hawking tries to figure them out.

It is Hawking's voice, that instantly recognisable computer speech synthesiser, that opens the film: "A black hole is stranger than anything dreamed up by science fiction writers. It's a region of space where gravity is so strong that nothing can escape. Once you are over the edge, there's no way back." City-sized black holes form when certain stars run out of fuel to burn and collapse under the force of their own gravity. Supermassive black holes -- millions or billions of times bigger than our sun -- are found at the centre of almost every galaxy including our own, the Milky Way.

mnemotronic writes: Igor Gamow, inventor of the "Gamow bag," a portable hyperbaric chamber for treatment of altitude or Acute Mountain Sickness (AMS), has died. He is credited or co-credited with other inventions, including prosthetics for amputees. His career at the University of Colorado in Boulder was marred by accusations from multiple sources of sexual predation. He is one of only three tenured professors ever to be fired by CU Boulder since its founding in 1876.

New submitter StellarThoughts writes: Scientists analyzed the second ever known interstellar object, a comet known as 2I/Borisov, and found some very unlikely results. Molecules of nickel and iron were being vaporized and drifting from the surface. Typically, nickel and iron vaporize when comets streak near the sun or aim directly for it, reaching temperatures exceeding 800 degrees Fahrenheit. And instead, this comet was a toasty -135 degrees F.

Comparing data with 20 other comets of varying chemical composition within the solar system, they spewed nickel and iron much like 2I/Borisov. Scientists have a few theories, including: "One possibility is that harsh ultraviolet light from the sun might break apart nickel-containing molecules in the comets." Scientists believe these traces were missed for so long because of the supposed unlikelihood of gaseous metals at such a low temperature.

RockDoctor (Slashdot reader #15,477) writes: For a number of years the administrative process for giving asteroids names has had a worsening logjam. Important or "interesting" bodies (such as `Oumuamua, the first definitely interstellar object identified) would still get names rapidly assigned, but in the background myriads of unspectacular objects would persist with "names" based on their discovery date like "1981 GD1". Which is adequate for managing databases, but less than satisfactory for most humans.

A new publication from the "Working Group for Small Body Nomenclature", combines what used to be several steps into one stage. So now one can easily find that "1981 GD1" has the name "Rutherford", to commemorate one of the major scientists of the 20th century.

No doubt there will be complaints of an over-concentration on figures from Classical legend (22 of 179 names assigned), but eventually that mine will play out. Professional and amateur astronomers (34 and 30 names) are, unsurprisingly, the largest groups commemorated. Other scientists get a good showing (16, Rutherford included), along with memorials to teachers, observatories and universities. One architect and one astronaut (there isn't a bar on memorialising living persons) also get mentions, and modest numbers of sports stars, musicians and other cultural figures pad out the list. Chinese, Japanese and Taiwanese contributors have a significant input to this batch, along with a number of South American contributions and a fair number from smaller countries (Paul Erdos, for example, in the {dead+ white+ mathematical eccentrics} category). And one entry which I can only class as a joke — 1990 QX19 gets a name which should have been used years ago. Obviously you'll need to RTFA to see the joke, but RTFA-ing is an un-Slashdot activity.

Future numbers of the Bulletin will publish new batches of assigned names, and work away on the backlog. You still need to be the discoverer of a "small body" to submit a name proposal, but that step of the process is also under review. With about 22,000 of the currently-recognised million-plus objects with well-characterised orbits, there is no realistic prospect of running out any time soon — they are being found faster than they get named. But eventually you too could name a pathetic little mudball for someone you despise. Won't that be fun?