Calgarians Detail Life With an Electricity Load Limiter

Limiters cap amount of electricity households can use, making many appliances unusable. From a report: Josie Gagne was stumbling in the dark, sobbing while on the phone with an Enmax customer assistant, as she tried to locate the tiny orange button under the utility meter that would restore heat inside. It was the shock that got her. The young single mother with two kids under two returned home one winter day last year to find a note on her door from Enmax. She’d fallen behind on bills; the home was now on a limiter, capping her electricity. The furnace was off and at that point, she had no idea what a limiter even was. “I’m freaking out. I’m crying, thinking ‘What am I going to do?'” she said. “It’s the middle of winter, it’s still cold outside. How am I going to feed my children when my oven doesn’t work?”

Rising utility bills have community advocates worried the number of Calgarians facing this scenario will increase, and many don’t know what a load limiter is. It’s often the first step before disconnection. Several Calgary residents flagged the issue while sharing their utility bill experiences with CBC Calgary through text messaging, and on Calgary Kindness, a mutual aid Facebook group. They’ve shared their personal stories with CBC journalists so others know what to expect. Contributors said they were scared their fridge would lose power and their groceries would rot. They relied on air fryers, barbecues or a hot plate to make it through. The extra fees — $52 for the notice, $52 to remove the limiter — only made it worse. Plus, the black mark on their files means they often can’t get a contract with more favourable fixed rates. When the device is installed, a stove or anything else requiring 240 volts of electricity won’t work.

Read more of this story at Slashdot.

Android’s Messages, Dialer Apps Quietly Sent Text, Call Info To Google

Google’s Messages and Dialer apps for Android devices have been collecting and sending data to Google without specific notice and consent, and without offering the opportunity to opt-out, potentially in violation of Europe’s data protection law. From a report: According to a research paper, “What Data Do The Google Dialer and Messages Apps On Android Send to Google?” [PDF], by Trinity College Dublin computer science professor Douglas Leith, Google Messages (for text messaging) and Google Dialer (for phone calls) have been sending data about user communications to the Google Play Services Clearcut logger service and to Google’s Firebase Analytics service.

“The data sent by Google Messages includes a hash of the message text, allowing linking of sender and receiver in a message exchange,” the paper says. “The data sent by Google Dialer includes the call time and duration, again allowing linking of the two handsets engaged in a phone call. Phone numbers are also sent to Google.” The timing and duration of other user interactions with these apps has also been transmitted to Google. And Google offers no way to opt-out of this data collection. […] Both pre-installed versions of these apps, the paper observes, lack app-specific privacy policies that explain what data gets collected — something Google requires from third-party developers. And when a request was made through Google Takeout for the Google Account data associated with the apps used for testing, the data Google provided did not include the telemetry data observed.

Read more of this story at Slashdot.

Roku OS 11 Will Let You Set Your Own Photos as a Screensaver

Roku device owners will soon have a whole host of new personalization features, including all-new Photo Streams, with the Roku OS 11. From a report: Firstly, when Roku OS 11 rolls out to users in the weeks ahead, they’ll be able to change their screensaver to display their own photography or images with Photo Streams. Not only will Photo Streams allow users to display photos from their desktop or mobile device on Roku, but users will also be able to share Streams with other Roku device owners as well. Once a Stream is shared, other Roku owners will be able to add to it, allowing everyone to collaborate on a shared album. Roku OS 11 will also introduce a new “what to watch on Roku” menu, a personally curated hub added to the home screen menu that will suggest popular and recently released TV and movies.

Read more of this story at Slashdot.

Browser-in-the-Browser Attack Can Trick Even Savvy Users

apoc.famine shares a report from Ars Technica: Hundreds of thousands of sites use the OAuth protocol to let visitors login using their existing accounts with companies like Google, Facebook, or Apple. Instead of having to create an account on the new site, visitors can use an account that they already have — and the magic of OAuth does the rest. The Browser-in-the-Browser (BitB) technique capitalizes on this scheme. Instead of opening a genuine second browser window that’s connected to the site facilitating the login or payment, BitB uses a series of HTML and cascading style sheets (CSS) tricks to convincingly spoof the second window. The URL that appears there can show a valid address, complete with a padlock and HTTPS prefix. The layout and behavior of the window appear identical to the real thing.

While the method is convincing, it has a few weaknesses that should give savvy visitors a foolproof way to detect that something is amiss. Genuine OAuth or payment windows are in fact separate browser instances that are distinct from the primary page. That means a user can resize them and move them anywhere on the monitor, including outside the primary window. BitB windows, by contrast, aren’t a separate browser instance at all. Instead, they’re images rendered by custom HTML and CSS and contained in the primary window. That means the fake pages can’t be resized, fully maximized or dragged outside the primary window. All users should protect their accounts with two-factor authentication. One other thing more experienced users can do is right click on the popup page and choose “inspect.” If the window is a BitB spawn, its URL will be hardcoded into the HTML.

Read more of this story at Slashdot.

Scientists Say They Can Read Nearly the Whole Genome of an IVF-Created Embryo

sciencehabit shares a report from Science.org: A California company says it can decipher almost all the DNA code of a days-old embryo created through in vitro fertilization (IVF) — a challenging feat because of the tiny volume of genetic material available for analysis. The advance depends on fully sequencing both parents’ DNA and “reconstructing” an embryo’s genome with the help of those data. And the company suggests it could make it possible to forecast risk for common diseases that develop decades down the line. Currently, such genetic risk prediction is being tested in adults, and sometimes offered clinically. The idea of applying it to IVF embryos has generated intense scientific and ethical controversy. But that hasn’t stopped the technology from galloping ahead.
Predicting a person’s chance of a specific illness by blending this genetic variability into what’s called a “polygenic risk score” remains under study in adults, in part because our understanding of how gene variants come together to drive or protect against disease remains a work in progress. In embryos it’s even harder to prove a risk score’s accuracy, researchers say. The new work on polygenic risk scores for IVF embryos is “exploratory research,” says Premal Shah, CEO of MyOme, the company reporting the results. Today in Nature Medicine, the MyOme team, led by company co-founders and scientists Matthew Rabinowitz and Akash Kumar, along with colleagues elsewhere, describe creating such scores by first sequencing the genomes of 10 pairs of parents who had already undergone IVF and had babies. The researchers then used data collected during the IVF process: The couples’ embryos, 110 in all, had undergone limited genetic testing at that time, a sort of spot sequencing of cells, called microarray measurements. Such analysis can test for an abnormal number of chromosomes, certain genetic diseases, and rearrangements of large chunks of DNA, and it has become an increasingly common part of IVF treatment in the United States. By combining these patchy embryo data with the more complete parental genome sequences, and applying statistical and population genomics techniques, the researchers could account for the gene shuffling that occurs during reproduction and calculate which chromosomes each parent had passed down to each embryo. In this way, they could predict much of that embryo’s DNA.

The researchers had a handy way to see whether their reconstruction was accurate: Check the couples’ babies. They collected cheek swab samples from the babies and sequenced their full genome, just as they’d done with the parents. They then compared that “true sequence” with the reconstructed genome for the embryo from which the child originated. The comparison revealed, essentially, a match: For a 3-day-old embryo, at least 96% of the reconstructed genome aligned with the inherited gene variants in the corresponding baby; for a 5-day-old embryo, it was at least 98%. (Because much of the human genome is the same across all people, the researchers focused on the DNA variability that made the parents, and their babies, unique.) Once they had reconstructed embryo genomes in hand, the researchers turned to published data from large genomic studies of adults with or without common chronic diseases and the polygenic risk score models that were derived from that information. Then, MyOme applied those models to the embryos, crunching polygenic risk scores for 12 diseases, including breast cancer, coronary artery disease, and type 2 diabetes. The team also experimented with combining the reconstructed embryo sequence of single genes, such as BRCA1 and BRCA2, that are known to dramatically raise risk of certain diseases, with an embryo’s polygenic risk scores for that condition — in this case, breast cancer.

Read more of this story at Slashdot.

Apple’s New Studio Display Has 64GB of Onboard Storage

New submitter Dru Nemeton shares a report from 9to5Mac: Apple’s new Studio Display officially hit the market on Friday, and we continue to learn new tidbits about what exactly’s inside the machine. While Apple touted that the Studio Display is powered by an A13 Bionic inside, we’ve since learned that the Studio Display also features 64GB of onboard storage, because who knows why… […] as first spotted by Khaos Tian on Twitter, the Studio Display also apparently features 64GB of onboard storage. Yes, 64GB: double the storage in the entry-level Apple TV 4K and the same amount of storage in the entry-level iPad Air 5. Also worth noting: the Apple TV 4K is powered by the A12 Bionic chip, so the Studio Display has it beat on that front as well. Apple hasnâ(TM)t offered any explanation for why the Studio Display features 64GB of onboard storage. It appears that less than 2GB of that storage is actually being used as of right now.

One unexciting possibility is that the A13 Bionic chip used inside the Studio Display is literally the exact same A13 Bionic chip that was first shipped in the iPhone 11. As you might remember, the iPhone 11 came with 64GB of storage in its entry-level configuration, meaning Apple likely produced millions of A13 Bionic chips with 64GB of onboard storage. What do you think? Will Apple ever tap into the A13 Bionic chip and 64GB storage inside the Studio Display for something more interesting?

Read more of this story at Slashdot.

Linux Random Number Generator Sees Major Improvements

An anonymous Slashdot reader summarizes some important news from the web page of Jason Donenfeld (creator of the open-source VPN protocol WireGuard):

The Linux kernel’s random number generator has seen its first set of major improvements in over a decade, improving everything from the cryptography to the interface used. Not only does it finally retire SHA-1 in favor of BLAKE2s [in Linux kernel 5.17], but it also at long last unites ‘/dev/random’ and ‘/dev/urandom’ [in the upcoming Linux kernel 5.18], finally ending years of Slashdot banter and debate:

The most significant outward-facing change is that /dev/random and /dev/urandom are now exactly the same thing, with no differences between them at all, thanks to their unification in random: block in /dev/urandom. This removes a significant age-old crypto footgun, already accomplished by other operating systems eons ago. […] The upshot is that every Internet message board disagreement on /dev/random versus /dev/urandom has now been resolved by making everybody simultaneously right! Now, for the first time, these are both the right choice to make, in addition to getrandom(0); they all return the same bytes with the same semantics. There are only right choices.

Phoronix adds:
One exciting change to also note is the getrandom() system call may be a hell of a lot faster with the new kernel. The getrandom() call for obtaining random bytes is yielding much faster performance with the latest code in development. Intel’s kernel test robot is seeing an 8450% improvement with the stress-ng getrandom() benchmark. Yes, an 8450% improvement.

Read more of this story at Slashdot.

Sleeping With the Light On May Be Harmful To You

“Exposure to even moderate ambient lighting during nighttime sleep, compared to sleeping in a dimly lit room, harms your cardiovascular function during sleep and increases your insulin resistance the following morning,” announced Northwestern Medicine, citing a new study recently published in the Proceedings of the National Academy of Sciences.

The Washington Post reports:
Researchers at Northwestern University had two groups of 10 young adults sleep in differently lit rooms. One group slept in rooms with dim light for two nights; the other slept one night in a room with dim night and the next in a room with moderate overhead light — about the equivalent of an overcast day. Participants wore heart monitors at night. In the morning, they did a variety of glucose tests.

Both groups got the same amount of sleep but their bodies experienced very different nights. Both groups responded well to insulin the first night, when they both slept in dim lighting. On the second night, however, the group sleeping in brighter lighting didn’t respond as well to insulin. The dim light sleepers’ insulin resistance scores fell about 4 percent on the second night, while the bright sleepers’ rose about 15 percent. Their heart rates were faster on the bright night, too.

“[J]ust a single night of exposure to moderate room lighting during sleep can impair glucose and cardiovascular regulation, which are risk factors for heart disease, diabetes and metabolic syndrome,” concludes senior study author Dr. Phyllis Zee. “It’s important for people to avoid or minimize the amount of light exposure during sleep.”
From Northwestern’s announcement:
There is already evidence that light exposure during daytime increases heart rate via activation of the sympathetic nervous system, which kicks your heart into high gear and heightens alertness to meet the challenges of the day. “Our results indicate that a similar effect is also present when exposure to light occurs during nighttime sleep,” Zee said….

An earlier study published in JAMA Internal Medicine looked at a large population of healthy people who had exposure to light during sleep. They were more overweight and obese, Zee said. “Now we are showing a mechanism that might be fundamental to explain why this happens. We show it’s affecting your ability to regulate glucose,” Zee said.

Read more of this story at Slashdot.

Researchers Discover a New (intermediate and Tetragonal) Form of Ice

Researchers at the University of Nevada, Las Vegas were trying to understand how water might behave under the high pressures inside distant planets.
But along the way the team discovered a new form of ice, reports Phys.org, “redefining the properties of water at high pressures.”

Solid water, or ice, is like many other materials in that it can form different solid materials based on variable temperature and pressure conditions, like carbon forming diamond or graphite. However, water is exceptional in this aspect as there are at least 20 solid forms of ice known to us.

A team of scientists working in UNLV’s Nevada Extreme Conditions Lab pioneered a new method for measuring the properties of water under high pressure. The water sample was first squeezed between the tips of two opposite-facing diamonds — freezing into several jumbled ice crystals. The ice was then subjected to a laser-heating technique that temporarily melted it before it quickly re-formed into a powder-like collection of tiny crystals. By incrementally raising the pressure, and periodically blasting it with the laser beam, the team observed the water ice make the transition from a known cubic phase, Ice-VII, to the newly discovered intermediate, and tetragonal, phase, Ice-VIIt, before settling into another known phase, Ice-X….

While it’s unlikely we’ll find this new phase of ice anywhere on the surface of Earth, it is likely a common ingredient within the mantle of Earth as well as in large moons and water-rich planets outside of our solar system. The team’s findings were reported in the March 17 issue of the journal Physical Review B…. The work also recalibrates our understanding of the composition of exoplanets, UNLV physicist Ashkan Salamat added. Researchers hypothesize that the Ice-VIIt phase of ice could exist in abundance in the crust and upper mantle of expected water-rich planets outside of our solar system, meaning they could have conditions habitable for life.

Thanks to long-time Slashdot reader fahrbot-bot for sharing the story…

Read more of this story at Slashdot.

‘Biggest Change Ever’ to Go Brings Generics, Native Fuzzing, and a Performance Boost

“Supporting generics has been Go’s most often requested feature, and we’re proud to deliver the generic support that the majority of users need today,” the Go blog announced this week. *

It’s part of what Go’s development team is calling the “biggest change ever to the language”.

SiliconANGLE writes that “Right out of the gate, Go 1.18 is getting a CPU speed performance boost of up to 20% for Apple M1, ARM64 and PowerPC64 chips. This is all from an expansion of Go 1.17’s calling conventions for the application binary interface on these processor architectures.”

And Go 1.18 also introduces native support for fuzz testing — the first major programming language to do so, writes ZDNet:

As Google explains, fuzz testing or ‘fuzzing’ is a means of testing the vulnerability of a piece of software by throwing arbitrary or invalid data at it to expose bugs and unknown errors. This adds an additional layer of security to Go’s code that will keep it protected as its functionality evolves — crucial as attacks on software continue to escalate both in frequency and complexity. “At Google we are committed to securing the online infrastructure and applications the world depends upon,” said Eric Brewer, VIP infrastructure at Google….
While other languages support fuzzing, Go is the first major programming language to incorporate it into its core toolchain, meaning — unlike other languages — third-party support integrations aren’t required.

Google is emphasizing Go’s security features — and its widespread adoption. ZDNet writes:

Google created Go in 2007 and was designed specifically to help software engineers build secure, open-source enterprise applications for modern, multi-core computing systems. More than three-quarters of Cloud Native Computing Foundation projects, including Kubernetes and Istio, are written in Go, says Google. [Also Docker and Etc.] According to data from Stack Overflow, some 10% of developers are writing in Go worldwide, and there are signs that more recruiters are seeking out Go coders in their search for tech talent….. “Although we have a dedicated Go team at Google, we welcome a significant amount of contributions from our community. It’s a shared effort, and with their updates we’re helping our community achieve Go’s long-term vision.
Or, as the Go blog says:

We want to thank every Go user who filed a bug, sent in a change, wrote a tutorial, or helped in any way to make Go 1.18 a reality. We couldn’t do it without you. Thank you.

Enjoy Go 1.18!

* Supporting generics “includes major — but fully backward-compatible — changes to the language,” explains the release notes. Although it adds a few cautionary notes:

These new language changes required a large amount of new code that has not had significant testing in production settings. That will only happen as more people write and use generic code. We believe that this feature is well implemented and high quality. However, unlike most aspects of Go, we can’t back up that belief with real world experience. Therefore, while we encourage the use of generics where it makes sense, please use appropriate caution when deploying generic code in production.

While we believe that the new language features are well designed and clearly specified, it is possible that we have made mistakes…. it is possible that there will be code using generics that will work with the 1.18 release but break in later releases. We do not plan or expect to make any such change. However, breaking 1.18 programs in future releases may become necessary for reasons that we cannot today foresee. We will minimize any such breakage as much as possible, but we can’t guarantee that the breakage will be zero.

Read more of this story at Slashdot.