Four California dams are now being dismantled, reports the Arizona Republic: Sometime in January, work crews will start drilling a tunnel at the base of a concrete dam on the Klamath River, near the California-Oregon border. The tunnel will begin the process of drawing down the reservoir behind the dam, known as Copco-1, and prepare the site to remove the dam from the river. Time was, removing a dam in the West was unheard of. Dams were built to store water, generate electricity, manage the use of rivers for growers. But environmental activists started telling the story of how dams damage a river and its ecosystem, and Indigenous communities have told their stories of how dams took away traditional resources and food sources. And so, in recent years, we've seen more dams removed. In Arizona, the removal of a hydroelectric dam on Fossil Creek led to the restoration of a sparkling waterway and a habitat for fish, birds and other wildlife.
California's dam-removal project began in June, reports the Los Angeles Time, when the smallest of the four dams was torn down by crews using heavy machinery. "The other three dams are set to be dismantled next year, starting with a drawdown of the reservoirs in January." "The scale of this is enormous," said Mark Bransom, CEO of the nonprofit Klamath River Renewal Corp., which is overseeing dam removal and river restoration efforts. "This is the largest dam removal project ever undertaken in the United States, and perhaps even the world." The $450-million budget includes about $200 million from ratepayers of PacifiCorp, who have been paying a surcharge for the project. The Portland-based utility — part of billionaire Warren Buffett's conglomerate Berkshire Hathaway — agreed to remove the aging dams after determining it would be less expensive than trying to bring them up to current environmental standards.

The dams were used purely for power generation, not to store water for cities or farms. "The reason that these dams are coming down is that they've reached the end of their useful life," Bransom said. "The power generated from these dams is really a trivial amount of power, something on the order of 2% of the electric utility that previously owned the dams." An additional $250 million came through Proposition 1, a bond measure passed by California voters in 2014 that included money for removing barriers blocking fish on rivers.

Crews hired by the contractor Kiewet Corp. have been working on roads and bridges to prepare for the army of excavators and dump trucks. "We have thousands of tons of concrete and steel that make up these dams that we have to remove," Bransom said. "We'll probably end up with 400 to 500 workers at the peak of the work..."

In addition to tearing down the dams, the project involves restoring about 2,200 acres of reservoir bottom to a natural state.

Several scientists from NASA told the New York Times that the agency is planning to build houses on the moon by 2040. Forbes reports: The agency is set to return to the moon and is hoping its astronauts can stay long-term -- in a house built on the moon via a 3D printer. The idea is to build the house structure out of a special lunar concrete from the moon's surface, and NASA has found just the company to do it: Austin-based 3D printing company, ICON. In what's been dubbed Project Olympus, ICON

ICON created its first 350-square-foot prototype home in Austin in March 2018 with a proprietary machine called Vulcan. This year, it showcased its first model home at Wolf Ranch in Georgetown, Texas, which is part of its 3D-printed 100-home community project. The start-up first received funding from NASA in 2020, and in 2022 it announced an additional $60 million for a space-based construction system that can be used beyond earth. The idea is to send a 3D printer up to the moon via a rocket, and the printer completes its job from there. "We've got all the right people together at the right time with a common goal, which is why I think we'll get there," NASA's director of technology maturation, Niki Werkheiser told The New York Times. "Everyone is ready to take this step together, so if we get our core capabilities developed, there's no reason it's not possible."

NASA has expanded its contracts with Axiom Space and Collins Aerospace to design and develop new spacesuits, providing each company with an additional $5 million. Engadget reports: NASA has ordered a spacesuit from Axiom Space meant for use in Low Earth Orbit, specifically for spacewalks outside the International Space Station. The original contract for Axiom was for a spacewalking system that the Artemis III astronauts will wear on the lunar surface when they land on the moon. Axiom unveiled a prototype for its original order in March, showcasing a suit with joints that allow wearers to move around with ease and a helmet equipped with a light and an HD camera. Meanwhile, Collins Aerospace has received an order for a spacesuit meant for use on the lunar surface. The company was previously contracted to develop a spacewalking suit for use outside the ISS. In other words, each company has received a new order that mirrors the other's previous one.

Redundancy is an important part of space tech development. In this case, spacesuits meant for the same purpose developed by two different companies could ensure that astronauts will have something to use if the other one fails for any reason. That said, the new task orders are for the companies' initial "design modification work" -- they're essentially modifying their original suits for a new purpose -- and NASA wants to see them first before committing to their continued development. Axiom told SpaceNews that if NASA decides to push through with the new spacesuits' development, the full order will cost the agency $142 million over four years.

Google Chromebooks expire too soon, saddling taxpayer-funded public schools with excessive expenses and inflicting unnecessary environmental damage, according to the US Public Interest Research Group (PIRG) Education Fund. The Register reports: In a report on Tuesday, titled "Chromebook Churn," US PIRG contends that Chromebooks don't last as long as they should, because Google stops providing updates after five to eight years and because device repairability is hindered by the scarcity of spare parts and repair-thwarting designs. This planned obsolescence, the group claims, punishes the public and the world.

"The 31 million Chromebooks sold globally in the first year of the pandemic represent approximately 9 million tons of CO2e emissions," the report says. "Doubling the life of just Chromebooks sold in 2020 could cut emissions equivalent to taking 900,000 cars off the road for a year, more than the number of cars registered in Mississippi." The report says that excluding additional maintenance costs, longer lasting Chromebooks could save taxpayers as much as $1.8 billion dollars in hardware replacement expenses.

The US PIRG said it wants: Google to extend its ChromeOS update policy beyond current device expiration dates; hardware makers to make parts more available so their devices can be repaired; and hardware designs that enable easier part replacement and service. [...] According to US PIRG, making an average laptop releases 580 pounds of carbon dioxide into the atmosphere, amounting to 77 percent of the total carbon impact of the device during its lifetime. Thus, the 31 million Chromebooks sold during the first year of the pandemic represent about 8.9 million tons of CO2e emissions. "We think that Google should extend the automatic update expiration to 10 years after launch date," said Lucas Gutterman, who leads US PIRG's Designed to Last campaign. "There's just no reason why we should be throwing away a computer that still is otherwise functional just because it passes a certain date."

"We're asking Google to use their leadership among the OEMs to design the devices to last, to make some of the changes that we list, to have them be more easily repairable by actually producing spare parts that folks can buy at reasonable prices," he added. "And to design with modularity and repair in mind, so that you can, for example, use the plastic bezel on one Chromebook on the next version, rather than having to buy a whole new set of spare parts just because a clip has changed."

It's been just a year since Intel officially announced its Bitcoin-mining Blockscale ASICs, but today the company announced the end of life of its first-gen Blockscale 1000-series chips without announcing any follow-up generations of the chips. From a report: We spoke with Intel on the matter, and the company told Tom's Hardware that "as we prioritize our investments in IDM 2.0, we have end-of-lifed the Intel Blockscale 1000 Series ASIC while we continue to support our Blockscale customers."

Intel's statement cites the company's tighter focus on its IDM 2.0 operations as the reason for ending the Blockscale ASICs, a frequent refrain in many of its statements as it has exited several businesses amid company-wide belt-tightening. We also asked Intel if it planned to exit the Bitcoin ASIC business entirely, but the company responded, "We continue to monitor market opportunities." In the original announcement that the company would enter the blockchain market, then-graphics-chief Raja Koduri noted that the company had created a Custom Compute Group within the AXG graphics unit to support the Bitcoin ASICs and "additional emerging technology." However, Intel recently restructured the AXG group, and Koduri left the company shortly thereafter.

While Chrome 112 just shipped this week and Chrome 113 only in beta, there is already a big reason to look forward to that next Chrome web browser release: Google is finally ready to ship WebGPU support. From a report: WebGPU provides the next-generation high performance 3D graphics API for the web. With next month's Chrome 113 stable release, the plan is to have WebGPU available out-of-the-box for this new web graphics API. Though in that version Google is limiting it to ChromeOS, macOS, and Windows... Yes, Google says other platforms like Linux will see their roll-out later in the year. The WebGPU API is more akin to Direct3D 12, Vulkan, and Metal compared with the existing WebGL being derived from OpenGL (ES). From Google's blog post: WebGPU is a new API for the web, which exposes modern hardware capabilities and allows rendering and computation operations on a GPU, similar to Direct3D 12, Metal, and Vulkan. Unlike the WebGL family of APIs, WebGPU offers access to more advanced GPU features and provides first-class support for general computations on the GPU. The API is designed with the web platform in mind, featuring an idiomatic JavaScript API, integration with promises, support for importing videos, and a polished developer experience with great error messages.

This initial release of WebGPU serves as a building block for future updates and enhancements. The API will offer more advanced graphics features, and developers are encouraged to send requests for additional features. The Chrome team also plans to provide deeper access to shader cores for even more machine learning optimizations and additional ergonomics in WGSL, the WebGPU Shading Language.

SVB Financial, parent of Silicon Valley Bank, is in talks to sell itself, sources told CNBC's David Faber. From the report: Attempts by the bank to raise capital have failed, the sources said, and the bank has hired advisors to explore a potential sale. Large financial institutions are looking at a potential purchase of SVB. Shares of the bank fell 60% on Thursday after SVB announced a plan Wednesday evening to raise more than $2 billion in capital. The stock fell another 60% in premarket trading Friday before being halted for pending news. Under the terms of a plan released Wednesday, SVB was looking to sell $1.25 billion in common stock and another $500 million of convertible preferred shares. SVB also announced a deal with investment firm General Atlantic to sell $500 million of common stock, though that agreement was contingent on the closing of the other common stock offering, according to a securities filing. SVB is a major bank for venture-back companies, and cited cash burn from clients as one reason it was looking to raise additional capital.

Ryan Graves, former Lt. U.S. Navy and F/A-18F pilot who was the first active-duty fighter pilot to come forward publicly about regular sightings of UAP, says more data is needed about unidentified anomalous phenomena (UAP). "We should encourage pilots and other witnesses to come forward and keep the pressure on Congress to prioritize UAP as a matter of national security," writes Graves in an opinion piece for The Hill. An anonymous Slashdot reader shares an excerpt from his report: As a former U.S. Navy F/A-18 fighter pilot who witnessed unidentified anomalous phenomena (UAP) on a regular basis, let me be clear. The U.S. government, former presidents, members of Congress of both political parties and directors of national intelligence are trying to tell the American public the same uncomfortable truth I shared: Objects demonstrating extreme capabilities routinely fly over our military facilities and training ranges. We don't know what they are, and we are unable to mitigate their presence. The Office of the Director of National Intelligence (ODNI) last week published its second ever report on UAP activity. While the unclassified version is brief, its findings are sobering. Over the past year, the government has collected hundreds of new reports of enigmatic objects from military pilots and sensor systems that cannot be identified and "represent a hazard to flight safety." The report also preserves last year's review of the 26-year reporting period that some UAP may represent advanced technology, noting "unusual flight characteristics or performance capabilities."

Mysteriously, no UAP reports have been confirmed to be foreign so far. However, just this past week, a Chinese surveillance balloon shut down air traffic across the United States. How are we supposed to make sense of hundreds of reports of UAP that violate restricted airspace uncontested and interfere with both civilian and military pilots? Here is the hard truth. We don't know. UAP are a national security problem, and we urgently need more data.

Why don't we have more data? Stigma. I know the fear of stigma is a major problem because I was the first active-duty fighter pilot to come forward publicly about regular sightings of UAP, and it was not easy. There has been little support or incentive for aircrew to speak publicly on this topic. There was no upside to reporting hard-to-explain sightings within the chain of command, let alone doing so publicly. For pilots to feel comfortable, it will require a culture shift inside organizations and in society at large. I have seen for myself on radar and talked with the pilots who have experienced near misses with mysterious objects off the Eastern Seaboard that have triggered unsafe evasive actions and mandatory safety reports. There were 50 or 60 people who flew with me in 2014-2015 and could tell you they saw UAP every day. Yet only one other pilot has confirmed this publicly. I spoke out publicly in 2019, at great risk personally and professionally, because nothing was being done. The ODNI report itself notes that concentrated efforts to reduce stigma have been a major reason for the increase in reports this year. To get the data and analyze it scientifically, we must uproot the lingering cultural stigma of tin foil hats and "UFOs" from the 1950s that stops pilots from reporting the phenomena and scientists from studying it. Last September, the U.S. Navy said that all of the government's UFO videos are classified information and releasing any additional UFO videos would "harm national security."

guest reader writes: The Open Standards site contains a new paper from Bjarne Stroustrup titled A call to action: Think seriously about "safety"; then do something sensible about it.

Bjarne reacts to an NSA report about Software Memory Safety since the report excludes C and C++ as unsafe. Bjarne does not consider any of the report's choices for "safe" languages as superior to C++ for the range of uses he cares about.
From Bjarne's response: I have worked for decades to make it possible to write better, safer, and more efficient C++. In particular, the work on the C++ Core Guidelines specifically aims at delivering statically guaranteed type-safe and resource-safe C++ for people who need that without disrupting code bases that can manage without such strong guarantees or introducing additional tool chains. For example, the Microsoft Visual Studio analyzer and its memory-safety profile deliver much of the CG support today and any good static analyzer (e.g., Clang tidy, that has some CG support) could be made to completely deliver those guarantees at a fraction of the cost of a change to a variety of novel "safe" languages.
Bjarne also complains that in the NSA's document, "'safe' is limited to memory safety, leaving out on the order of a dozen other ways that a language could (and will) be used to violate some form of safety and security." There is not just one definition of "safety", and we can achieve a variety of kinds of safety through a combination of programming styles, support libraries, and enforcement through static analysis.... I envision compiler options and code annotations for requesting rules to be enforced. The most obvious would be to request guaranteed full type-and-resource safety.
Bjarne notes that if you work in application domains which prioritize performance over type safety, you could "apply the safety guarantees only where required and use your favorite tuning techniques where needed." Partial adoption of some of the rules (e.g., rules for range checking and initialization) is likely to be important. Gradual adoption of safety rules and adoption of differing safety rules will be important. If for no other reason than the billions of lines of C++ code will not magically disappear, and even "safe" code (in any language) will have to call traditional C or C++ code or be called by traditional code that does not offer specific safety guarantees.

Ignoring the safety issues would hurt large sections of the C++ community and undermine much of the other work we are doing to improve C++.
The article also contains the following references for consideration:
- Design Alternatives for Type-and-Resource Safe C++.
- Type-and-resource safety in modern C++.
- A brief introduction to C++'s model for type- and resource-safety.
- C++ Core Guidelines, safety profiles.

Watch a rare launch of SpaceX's massive Falcon Heavy rocket livestreamed on SpaceX's YouTube channel.

"Nearly five years have passed since the massive Falcon Heavy rocket made its successful debut launch in February 2018," writes Ars Technica.

"Since then, however, SpaceX's heavy lift rocket has flown just three additional times." Why? It's partly because there is simply not all that much demand for a heavy lift rocket. Another factor is that SpaceX has increased the performance of its Falcon 9 rocket so much that it can complete a lot of the missions originally manifested on the Falcon Heavy. However the main reason for the low cadence has been due to a lack of readiness of payloads for the new rocket, particularly from the US Department of Defense. But now this trickle of Falcon Heavy launches may turn into a flood. [Sunday's launch is the first of potentially five launches this year]

SpaceX completed a hot fire test of the rocket on Tuesday, and declared that the vehicle was ready for liftoff. The rocket will use a brand new core stage, and side-mounted boosters that have flown into space one time, as side-mounted boosters on the USSF-44 Falcon Heavy mission that launched on November 1 2022.
What's it carrying? Space.com writes: The main payload is a military communications satellite called Continuous Broadcast Augmenting SATCOM 2, which the Falcon Heavy will send to geostationary orbit, about 22,200 miles (35,700 kilometers) above Earth. Also flying Saturday is a rideshare spacecraft called Long Duration Propulsive ESPA (LDPE)-3A, a payload adapter that can hold up to six small satellites, according to EverydayAstronaut.com. LDPE-3A will carry five Space Force payloads on USSF-67. Among them are "two operational prototypes for enhanced situational awareness and an operational prototype crypto/interface encryption payload providing secure space-to-ground communications capability," Space Force officials said in an emailed statement on Friday....

If all goes according to plan, the two side boosters will come back to Earth shortly after liftoff on Sunday, making vertical touchdowns at Cape Canaveral Space Force Station, which is next door to NASA's Kennedy Space Center. The central booster will not return, instead ditching into the Atlantic Ocean....

USSF-67 is part of a busy week for SpaceX. The company also plans to launch 51 of its Starlink internet satellites to low Earth orbit atop a Falcon 9 on Thursday, January 19.

Guess what's finally entering America's public domain today? Appropriately enough, it's Marcel Proust's 1927 novel Remembrance of Things Past.

Also entering the public domain today are thousands of other books, plus the music and lyrics of hundreds of songs, and even several silent movies.

Fritz Lang's sci-fi classic Metropolis enters the public domain today — and so does the Laurel & Hardy comedy Battle of the Century (which culminates with one of Hollywod's first pie fights), according to Duke University's Center for the Study of the Public Domain: This is actually the second time that Metropolis has gone into the US public domain. The first was in 1955, when its initial 28-year term expired and the rights holders did not renew the copyright. Then in 1996 a new law restored the copyrights in qualifying foreign works. Metropolis, along with thousands of other works, was pulled out of the public domain, and now reenters it after the expiration of the 95-year term, with the once missing scenes available for anyone to reuse.
They also note that some material is in the public domain from the beginning, including government works like the images from the James Webb telescope.

But for other works, today is a big and important day, writes the Associated Press: Alongside the short-story collection "The Case-Book of Sherlock Holmes," books such as Virginia Woolf's "To The Lighthouse," Ernest Hemingway's "Men Without Women," William Faulkner's "Mosquitoes" and Agatha Christie's "The Big Four" — an Hercule Poirot mystery — will become public domain as the calendar turns to 2023. Once a work enters the public domain it can legally be shared, performed, reused, repurposed or sampled without permission or cost.

The works from 1927 were originally supposed to be copyrighted for 75 years, but the 1998 Copyright Term Extension Act delayed opening them up for an additional 20 years. While many prominent works on the list used those extra two decades to earn their copyright holders good money, a Duke University expert says the copyright protections also applied to "all of the works whose commercial viability had long subsided."

"For the vast majority — probably 99% — of works from 1927, no copyright holder financially benefited from continued copyright. Yet they remained off limits, for no good reason," Jennifer Jenkins, director of Duke's Center for the Study of the Public Domain, wrote in a blog post heralding "Public Domain Day 2023." That long U.S. copyright period meant many works that would now become available have long since been lost, because they were not profitable to maintain by the legal owners, but couldn't be used by others. On the Duke list are such "lost" films like Victor Fleming's "The Way of All Flesh" and Tod Browning's "London After Midnight...."
Also entering the public domain today:


- Willa Cather's Death Comes for the Archbishop
- A. A. Milne's Now We Are Six (illustrations by E. H. Shepard)
- Franklin W. Dixon's The Tower Treasure — the first Hardy Boys book
- Herman Hesse's Steppenwolf (German version)
- The song "My Blue Heaven"
- Songs by Duke Ellington and Louis Armstrong
- Alfred Hitchcock's early silent movie The Lodger


The UK-based newspaper the Observer adds: For those readers who do not reside in the US, there is perhaps another reason for celebrating today, because copyright terms are longer in the US than they are in other parts of the world, including the EU and the UK. And therein lies a story about intellectual property laws and the power of political lobbying in a so-called liberal democracy.... The term was gradually lengthened in small increments by Congress until 1976, when it was extended by 19 years to 75 years and then in 1998 by the Sonny Bono Act. So, as the legal scholar Lawrence Lessig puts it, "in the 20 years after the Sonny Bono Act, while 1 million patents will pass into the public domain, zero copyrights will pass into the public domain by virtue of the expiration of a copyright term"....

[T]he end result is that American citizens have had to wait two decades to be free to adapt and reuse works to which we Europeans have had easy access....

The issue highlighted by Public Domain Day is not that intellectual property is evil but that aspects of it — especially copyright — have been monopolised and weaponised by corporate interests and that legislators have been supine in the face of their lobbying. Authors and inventors need protection against being ripped off. It's obviously important that clever people are rewarded for their creativity and the patent system does that quite well. But if a patent only lasts for 20 years, why on earth should copyright last for life plus 70 years for a novel?

NASA is exploring whether SpaceX's Crew Dragon spacecraft can potentially offer an alternative ride home for some crew members of the International Space Station after a Russian capsule sprang a coolant leak while docked to the orbital lab. Reuters reports: NASA and Russia's space agency, Roscosmos, are investigating the cause of a punctured coolant line on an external radiator of Russia's Soyuz MS-22 spacecraft, which is supposed to return its crew of two cosmonauts and one U.S. astronaut to Earth early next year. But the Dec. 14 leak, which emptied the Soyuz of a vital fluid used to regulate crew cabin temperatures, has derailed Russia's space station routines, with engineers in Moscow examining whether to launch another Soyuz to retrieve the three-man team that flew to ISS aboard the crippled MS-22 craft. If Russia cannot launch another Soyuz ship, or decides for some reason that doing so would be too risky, NASA is weighing another option.

"We have asked SpaceX a few questions on their capability to return additional crew members on Dragon if necessary, but that is not our prime focus at this time," NASA spokeswoman Sandra Jones said in a statement to Reuters. It was unclear what NASA specifically asked of SpaceX's Crew Dragon capabilities, such as whether the company can find a way to increase the crew capacity of the Dragon currently docked to the station, or launch an empty capsule for the crew's rescue. But the company's potential involvement in a mission led by Russia underscores the degree of precaution NASA is taking to ensure its astronauts can safely return to Earth, should one of the other contingency plans arranged by Russia fall through.

An anonymous reader quotes a report from Ars Technica: Last month, a Texas-based company announced that it had successfully deployed the largest-ever commercial communications satellite in low-Earth orbit. This BlueWalker 3 demonstration satellite measures nearly 65 square meters, or about one-third the size of a tennis court. Designed and developed by AST SpaceMobile, the expansive BlueWalker 3 satellite is intended to demonstrate the ability of standard mobile phones to directly connect to the Internet via satellite. Large satellites are necessary to connect to mobile devices without a ground-based antenna. [...] Since BlueWalker3's launch in September, astronomers have been tracking the satellite, and their alarm was heightened following its antenna deployment last month. According to the International Astronomical Union, post-deployment measurements showed that BlueWalker 3 had an apparent visual magnitude of around 1 at its brightest, which is nearly as bright as Antares and Spica, the 15th and 16th brightest stars in the night sky.

For a few years, astronomers have been expressing concerns about megaconstellations, such as SpaceX's Starlink satellites. While these are more numerous -- there are more than 3,000 Starlink satellites in orbit -- they are much smaller and far less bright than the kinds of satellites AST plans to launch. Eventually, AST plans to launch a constellation of 168 large satellites to provide "substantial" global coverage, a company spokesperson said. Even one is enough for astronomers, however. "BlueWalker 3 is a big shift in the constellation satellite issue and should give us all reason to pause," said Piero Benvenuti, a director at the International Astronomical Union.

The organization of astronomers is also concerned about the potential for radio interference from these "cell phone towers in space." They will transmit strong radio waves at frequencies currently reserved for terrestrial cell phone communications but are not subject to the same radio quiet zone restrictions that ground-based cellular networks are. This could severely impact radio astronomy research -- which was used to discover cosmic microwave background radiation, for example -- as well as work in related fields. Astronomers currently build their radio astronomy observatories in remote areas, far from cell tower interference. They are worried that these large, radio-wave transmitting satellites will interfere in unpopulated areas. "We are eager to use the newest technologies and strategies to mitigate possible impacts to astronomy," AST said in a statement to Ars. "We are actively working with industry experts on the latest innovations, including next-generation anti-reflective materials. We are also engaged with NASA and certain working groups within the astronomy community to participate in advanced industry solutions, including potential operational interventions."

AST is "committed to avoiding broadcasts inside or adjacent to the National Radio Quiet Zone in the United States [...] as well as additional radioastronomy locations," adds Ars.

As subtropical storm Nicole moved across the Atlantic Ocean toward Florida on Monday afternoon, NASA confirmed that its Artemis I mission would remain at the launch pad along the state's east coast. Ars Technica reports: The risks to these large and costly vehicles are non-zero, however, and appear to be rising as Nicole starts to strengthen. The space agency's primary concern from tropical systems is winds. Much of the rocket's structure is pretty robust, such as its tank-like solid rocket boosters. But there are sensitive elements prone to damage from debris and wearing effects due to high winds inside a tropical system. According to the SLS rocket's chief engineer, John Blevins, the rocket can withstand wind gusts up to 74.1 knots. Knots are a term used in meteorology and maritime navigation and are equal to 1 nautical mile per hour. In this case, the SLS rocket can withstand gusts up to 85 mph, or 137 km/h. Wind "gusts" are different from sustained winds. These are short-term bursts of wind, as opposed to sustained winds over one minute or longer.

On Monday, at the time NASA announced its decision to remain at the launch pad as Nicole approached Florida, there was just a 4 percent chance of such winds at Kennedy Space Center. NASA, therefore, was willing to take a calculated risk by staying at the pad. One reason for remaining outside was, somewhat ironically, wear and tear. The process of rolling the Artemis I mission four miles back and forth, between the Vehicle Assembly Building and launch pad, puts a lot of stress on the vehicle. When it computes risk factors for the Artemis I launch vehicle, NASA has a certain budget for rollouts. The rocket has now been out to the pad on four separate occasions since this spring. While NASA has not confirmed this, according to a source, NASA has just one remaining roll in its budget. This does not mean the rocket will fall apart with additional roundtrips, it's just that additional movements would incrementally increase the risk of damage.

NASA may also simply not have had time to move inside the protective confines of the Vehicle Assembly Building. It takes a couple of days to prep the rocket to roll back. By Monday, it may have already been too late because to roll back before Nicole's arrival would probably have meant doing so no later than Tuesday night. Asked whether NASA really had no choice but to remain at the pad, a spokesperson for the agency, Rachel Kraft, was non-committal. "The team reviewed the forecast and determined the rocket will remain at the pad," she said on Monday. The problem for NASA is that Nicole is now expected to transition into a tropical storm and come ashore just south of Kennedy Space Center as a Category 1 hurricane. "The corresponding odds for hurricane-force winds -- at or above the safety limit established by NASA for its rocket -- are now up to 10 percent," reports Ars. "This is higher than the forecast that prompted a rollback during Ian."

A company called Subsea Cloud is planning to have a commercially available undersea datacenter operating off the coast of the US before the end of 2022, with other deployments planned for the Gulf of Mexico and the North Sea. The Register reports: Subsea, which says it has already deployed its technology with "a friendly government faction," plans to put its first commercial pod into the water before the end of this year near Port Angeles, Washington. The company claims that placing its datacenter modules underwater can reduce power consumption and carbon dioxide emissions by 40 percent, as well as lowering latency by allowing the datacenter to be located closer to metropolitan areas, many of which are located near the coast. However, according to Subsea founder Maxie Reynolds, it can also deploy 1MW of capacity for as much as 90 percent less cost than it takes to get 1MW up and running at a land-based facility.

The Port Angeles deployment, known as Jules Verne, will comprise one 20ft pod, which is similar in size and dimensions to a standard 20-foot shipping container (a TEU or Twenty-foot Equivalent Unit). Inside, there is space for about 16 datacenter racks accommodating about 800 servers, according to Subsea. Additional capacity, if and when required, is delivered by adding another pod. The pod-to-shore link in this deployment provides a 100Gbps connection. As it is a commercial deployment, Jules Verne will be open for any prospective clients or partners to come and check it out, virtually or otherwise, according to Reynolds. It will be sited in shallow water, visible from the port, whereas the Njord01 pod in the Gulf of Mexico and the Manannan pod in the North Sea are expected to be deeper, at 700-900ft and 600-700ft respectively.

The Subsea pods are kept cool by being immersed in water, which is one reason for the reduced power and CO2 emissions. Inside, the servers are also immersed in a dielectric coolant, which conducts heat but not electricity. However, the Subsea pods are designed to passively disperse the heat, rather than using pumps as is typical in submersion cooling in land-based datacenters. But what happens if something goes wrong, or a customer wants to replace their servers? According to Subsea, customers can schedule periodic maintenance, including server replacement, and the company says that would take 4-16 hours for a team to get to the site, bring up the required pod(s), and replace any equipment.

An anonymous reader quotes a report from Ars Technica: Unlike Intel Macs, Apple silicon Macs were designed to run only Apple's software. But the developers on the Asahi Linux team have been working to change that, painstakingly reverse-engineering support for Apple's processors and other Mac hardware and releasing it as a work-in-progress distro that can actually boot up and run on bare metal, no virtualization required. The Asahi Linux team put out a new release today with plenty of additions and improvements. Most notably, the distro now supports the M1 Ultra and the Mac Studio and has added preliminary support for the M2 MacBook Pro (which has been tested firsthand by the team) and the M2 MacBook Air (which hasn't been tested but ought to work). Preliminary Bluetooth support for all Apple silicon Macs has also been added, though the team notes that it works poorly when connected to a 2.4GHz Wi-Fi network because "Wi-Fi/Bluetooth coexistence isn't properly configured yet."

There are still many other things that aren't working properly, including the USB-A ports on the Studio, faster-than-USB-2.0 speeds from any Type-C/Thunderbolt ports, and GPU acceleration, but progress is being made on all of those fronts. GPU work in particular is coming along, with a "prototype driver" that is "good enough to run real graphics applications and benchmarks" already up and running, though it's not included in this release. The Asahi team has said in the past that it expects support for new chips to be relatively easy to add to Asahi since Apple's chip designers frequently reuse things and don't make extensive hardware changes unless there's a good reason for it. Adding basic support for the M2 to Asahi happened over the course of a single 12-hour development session, and just "a few days" of additional effort were needed to get the rest of the hardware working as well as it does with M1-based Macs.

The amount of cryptocurrency flowing into privacy-enhancing mixer services has reached an all-time high this year as funds from wallets belonging to government-sanctioned groups and criminal activity almost doubled, researchers reported on Thursday. ArsTechnica: Mixers, also known as tumblers, obfuscate cryptocurrency transactions by creating a disconnect between the funds a user deposits and the funds the user withdraws. To do this, mixers pool funds deposited by large numbers of users and randomly mix them. Each user can withdraw the entire amount deposited, minus a cut for the mixer, but because the coins come from this jumbled pool, it's harder for blockchain investigators to track precisely where the money went. Some mixers provide additional obfuscation by allowing users to withdraw funds in differing amounts sent to different wallet addresses. Others try to conceal the mixing activity altogether by changing the fee on each transaction or varying the type of deposit address used. Mixer use isn't automatically illegal or unethical. [...].

"Mixers present a difficult question to regulators and members of the cryptocurrency community," researchers from cryptocurrency analysis firm Chainalysis wrote in a report that linked the surge to increased volumes deposited by sanctioned and criminal groups. "Virtually everyone would acknowledge that financial privacy is valuable, and that in a vacuum, there's no reason services like mixers shouldn't be able to provide it. However, the data shows that mixers currently pose a significant money laundering risk, with 25 percent of funds coming from illicit addresses, and that cybercriminals associated with hostile governments are taking advantage." Cryptocurrency received by these mixers fluctuates significantly from day to day, so researchers find it more useful to use longer-term measures. The 30-day moving average of funds received by mixers hit $51.8 million in mid-April, an all-time high, Chainalysis reported. The high-water mark represented almost double the incoming volumes at the same point last year. What's more, illicit wallet addresses accounted for 23 percent of funds sent to mixers this year, up from 12 percent in 2021.

An anonymous reader quotes a report from Ars Technica: Earlier this year, news broke of the first experimental xenotransplantation: A human patient with heart disease received a heart from a pig that had been genetically engineered to avoid rejection. While initially successful, the experiment ended two months later when the transplant failed, leading to the death of the patient. At the time, the team didn't disclose any details regarding what went wrong. But this week saw the publication of a research paper that goes through everything that happened to prepare for the transplant and the weeks following. Critically, this includes the eventual failure of the transplant, which was triggered by the death of many of the muscle cells in the transplanted heart. But the reason for that death isn't clear, and the typical signs of rejection by the immune system weren't present. So, we're going to have to wait a while to understand what went wrong.
[...]
After death, the team performed an autopsy on the transplanted heart. They found that it had nearly doubled in weight, largely because of fluid (and some red blood cells) leaking out of blood vessels in the absence of clotting. There was significant death of heart muscle cells, but that was scattered across the heart, rather than being a general phenomenon. Critically, most of the indications of a strong immune rejection were missing. The presence of an apparent pig cytomegalovirus was worrying, but the researchers indicate there's some question about whether the tests that picked it up might have been recognizing a closely related human virus -- one that's often associated with organ transplant problems.

So, for now, it's not clear what happened with this transplant or what the significance of the apparent viral infection is. Obviously, the team has lots of material to work with to try to figure out what went on, and there's a long, long list of potential experiments to do with it. And there are also additional xenotransplant trials in the works, so it may not be long before we have a better sense of whether this was something specific to this transplant or a general risk of xenotransplantation.

The nonprofit online news site Virginia Mercury investigated their state police departments' "real-time location warrants," which are "addressed to telephone companies, ordering them to regularly ping a customers' phone for its GPS location and share the results with police." Public records requests submitted to a sampling of 18 police departments around the state found officers used the technique to conduct more than 7,000 days worth of surveillance in 2020. Court records show the tracking efforts spanned cases ranging from high-profile murders to minor larcenies.... Seven departments responded that they did not have any relevant billing records, indicating they don't use the technique. Only one of the departments surveyed, Alexandria, indicated it had an internal policy governing how their officers use cellphone tracking, but a copy of the document provided by the city was entirely redacted....

Drug investigations accounted for more than 60 percent of the search warrants taken out in the two jurisdictions. Larcenies were the second most frequent category. Major crimes like murders, rapes and abductions made up a fraction of the tracking requests, accounting for just under 25 of the nearly 400 warrants filed in the jurisdictions that year.
America's Supreme Court "ruled that warrantless cellphone tracking is unconstitutional back in 2012," the article points out — but in practice those warrants aren't hard to get. "Officers simply have to attest in an affidavit that they have probable cause that the tracking data is 'relevant to a crime that is being committed or has been committed'.... There's been limited public discussion or awareness of the kinds of tracking warrants the judiciary is approving." "I don't think people know that their cell phones can be converted to tracking devices by police with no notice," said Steve Benjamin, a criminal defense lawyer in Richmond who said he's recently noticed an uptick in cases in which officers employed the technique. "And the reality of modern life is everyone has their phone on them during the day and on their nightstand at night. ... It's as if the police tagged them with a chip under their skin, and people have no idea how easily this is accomplished."
The case for these phone-tracking warrants?

• The executive director of the Virginia Association of Chiefs of Police tells the site that physical surveillance ofen requires too many resources — and that cellphone tracking is safer. "It may be considered an intrusive way of gathering data on someone, but it's certainly less dangerous than physical tracking."
• A spokesperson for the Chesterfield County police department [responsible for 64% of the state's tracking] argued that "We exist to preserve human life and protect the vulnerable, and we will use all lawful tools at our disposal to do so." And they added that such "continued robust enforcement efforts" were a part of the reason that the county's still-rising number of fatal drug overdoses had not risen more.

The site also obtained bills from four major US cellphone carriers, and reported how much they were charging police for providing their cellphone-tracking services:

• "T-Mobile charged $30 per day, which comes to $900 per month of tracking."
• "AT&T charged a monthly service fee of $100 and an additional $25 per day the service is utilized, which comes to $850 per 30 days of tracking..."
• "Verizon calls the service 'periodic location updates,' charging $5 per day on top of a monthly service fee of $100, which comes to $200 per 30 days of tracking."
• "Sprint offered the cheapest prices to report locations back to law enforcement, charging a flat fee of $100 per month."

Thanks to Slashdot reader Beerismydad for sharing the article!

An anonymous reader quotes a report from Ars Technica: There is hope for users of Google's "legacy" free G Suite accounts. Last week, Google announced a brutal policy change -- it would shut down the Google Apps accounts of users who signed up during the first several years when the service was available for free. Users who had a free G Suite account were given two options: start paying the per-user monthly fee by July 2022 or lose your account. Naturally, this move led to a huge outcry outside (and apparently inside) Google, and now, the company seems to be backing down from most of the harsher terms of the initial announcement. First, Google is launching a survey of affected G Suite users -- apparently, the company is surprised by how many people this change affected. Second, it's promising a data-migration option (including your content purchases) to a consumer account before the shutdown hits.

The support page detailing the shutdown has quietly been updated (for some reason, Google is not making a big deal of the changes yet). First, if (and only if) you're signed in with a free G Suite account, you'll see a link to this survey, which is aimed at free G Suite admins with 10 users or fewer using the service for "non-business" purposes. Google says users filling out the survey will receive "updates on more options for your non-business legacy account in the coming months." It's a sign that Google had no idea how many people this change would affect, and now, the company wants to hear from you.

The ideal situation, if the custom domain option has to shut down, would be the option to port your free G Suite account to a consumer Google account, with all the purchases, data, email, and other features intact. You would naturally have to pick a new account name and email address, but minimal disruption to other services would seem like the least Google could do, and it sounds like the company is building something like that. There's now a new section on the support page titled: "If I don't want to upgrade to a paid subscription, can I transfer my data?" [...] This is the option everyone has been asking for, as it specifically references "non-Google Workspace paid content," which presumably would mean all your app, game, and media purchases made through Google Play and YouTube. The support article doesn't offer any additional details yet, only saying to wait for further updates, but Google promises the option will be ready before July, which is when the account disruptions start happening.