Davide Pesavento

@gentoo developer && @NamedData contributor && @NIST researcher

[Charlie Marsh @charliermarsh]

Today, we’re announcing the preview release of ty, an extremely fast type checker and language server for Python, written in Rust.

In early testing, it's 10x, 50x, even 100x faster than existing type checkers. (We've seen >600x speed-ups over Mypy in some real-world projects.)

[Mishaal Rahman @MishaalRahman]

Here's a first look at Android's upcoming all-in-one Terminal app, which downloads, configures, runs, and interfaces with an instance of Debian running a virtual machine!

Currently, the Debian images are hosted on a Googler's GitHub, but Google plans to host these images themselves soon. For more info on this Terminal app, see the replies👇

(Thanks to an anonymous dev for sharing this!)

[Sean Baxter @seanbax]

I wrote a proposal for memory safety in C++. It's in this month's WG21 mailing.

https://t.co/aeh9Q9YCeP

[Lucretiel 🦀 @Lucretiel]

I wrote a thread about why C++ move semantics are the way they are, and why Rust people can't be too arrogant about it because `Pin` is basically exactly the same story that 10 years from now people will be writing threads "Why did Rust ever allow this `Pin` thing to happen"

[Chelsea Komlo @chelseakomlo]

After 3 years and 12 drafts, the RFC for FROST is finally complete! We hope this makes implementing FROST easier with fewer bugs 🐛

Thank you to everyone who helped by reviewing FROST security, submitting comments, and implementing the draft, this truly was a team effort 🙌💪

https://t.co/jmW83bZDDp

[@ericniebler.bsky.social @ericniebler]

BREAKING: P2300 has been voted into C++26!

🎉

[Vittorio Romeo @supahvee1234]

"An Extensive Benchmark of C and C++ Hash Tables" by Jackson Allan
https://t.co/bGDkC6VjUj

[Vittorio Romeo @supahvee1234]

Fantastic new GCC release:
https://t.co/E4SKPNXKUu

Congratulations and heartfelt thanks to all the contributors!
#gcc #cpp #c

[SwiftOnSecurity @SwiftOnSecurity]

xz is a crushing microcosm of the toxic entitlement of users of open source projects who make demands but offer no assistance. And when assistance does come, it’s desperately appreciated.

by @robmen

https://t.co/C0lPCEDXXR

[Matthew Green @matthew_d_green]

So Apple has gone and updated the iMessage protocol to incorporate both forward security (very good!) and post-quantum cryptography. https://t.co/c7lidT3P9b

[Charlie Marsh @charliermarsh]

Announcing uv: an extremely fast Python package installer and resolver, written in Rust.

uv is designed as a drop-in alternative to pip, pip-tools, and virtualenv.

With a warm cache, uv installs are near-instant. Here, it's > 75x faster than pip and pip-tools.

[GitHub Changelog @GHchangelog]

GitHub Actions: Introducing the new M1 macOS runner available to open source! https://t.co/kT9cUVrbyq

[GitHub Changelog @GHchangelog]

GitHub Actions: macOS 14 (Sonoma) is now available https://t.co/WxN39hQu1X

[Mishaal Rahman @MishaalRahman]

Google is preparing a new "Storage Area Encryption" feature for a future release of Android that gives apps the ability to create "storage areas" that are accessible only after the device has been unlocked.

Storage areas are "transparently encrypted directories protected by screen lock bound keys" that provide "a level of protection above that of the Credential Encrypted storage which is the default for app data." These directories will be in a new top-level data directory, /data/storage_area. (Credential Encrypted storage is only available to apps after the initial unlock following a boot.)

It's a bit difficult to guess "why" they're adding this API just from the code changes in AOSP, so I'm throwing this out there to see if any security researchers might have an idea. One researcher guessed it could allow for SDKs to create their own dedicated place to store files or preferences that couldn't be accessed by apps integrated said SDK, but it doesn't look like this API makes that possible.

The code changes haven't been merged yet, so I'm not sure if this Storage Area Encryption API will make its way to Android 15 or Android 16.

[Mishaal Rahman @MishaalRahman]

Google announced last July that they would integrate the Message Layer Security (MLS) protocol into Google Messages and "support its wide deployment across the industry by open sourcing [their] implementation in the Android codebase."

Back in November, Google added the (Rust) crates for building OpenMLS, a Rust implementation of MLS, to AOSP. And last week, Google started work on a new Android Jetpack library (https://t.co/WIxzvZzYLZ:security-mls) to support building apps on top of the MLS protocol.

MLS is a protocol for encrypting messages in group chats that is "designed to be efficient, practical and secure" and, according to Google, "enables practical interoperability across services and platforms, scaling to groups of thousands of multi-device users." It has been approved by the IESG and is published as RFC9420.

[Ville Voutilainen @CplusplusVille]

GCC now has deduced this (I had no part in it, I'm just happy to play with it): https://t.co/qgb9E9DX6c
And yes, of course, also on godbolt: https://t.co/BazMP1fAdr

[John Burn-Murdoch @jburnmurdoch]

NEW: America is a rich country. Britain is a poor country with one wealthy region.

People love to compare the UK to Mississippi, but it’s far more informative to look at UK subnationally, too.

London ranks fairly well, the rest of the country does not 👉 https://t.co/xrIzwYGaCI

[Rui Ueyama @rui314]

I installed Xcode 15 Beta to try out the new Apple's linker. It seems that my mold/sold linker is still a bit faster than theirs, but the gap has now reduced to ~60% when linking the sold linker itself on my Mac Studio. Apple's new linker is in the same league as mine. Great job!

[निर्भीक चौहान @nirbheek]

For those of you wondering, Mold is still faster!

[MG @_MG_]

Love it