Google details new 24-hour process to sideload unverified Android apps (Ars Technica)

Ars Technica describes
the ritual
that will be required before a future Android device will
deign to install apps from somewhere other than the Play Store. It is not
for the impatient.

Here are the steps:

  • Enable developer options by tapping the software build number in About
    Phone seven times
  • In Settings > System, open Developer Options and scroll down to
    “Allow Unverified Packages.”
  • Flip the toggle and tap to confirm you are not being coerced
  • Enter device unlock code
  • Restart your device
  • Wait 24 hours
  • Return to the unverified packages menu at the end of the security delay
  • Scroll past additional warnings and select either “Allow temporarily”
    (seven days) or “Allow indefinitely.”
  • Check the box confirming you understand the risks.
  • You can now install unverified packages on the device by tapping the
    “Install anyway” option in the package manager.

Radicle 1.7.0 released

Version
1.7.0
(“Daffodil”) of the Radicle peer-to-peer, local-first code
collaboration stack has been released. Some of the changes in this
release include improved I/O usage, the ability to block nodes at the
connection level, and clearer errors for rad id
updates. See the release notes for a full list of changes and bug
fixes.

[$] Development tools: Sashiko, b4 review, and API specification

The kernel project has a unique approach to tooling that avoids many
commonly used development systems that do not fit the community’s scale and
ways of working. Another way of looking at the situation is that the kernel
project has often under-invested in tooling, and sometimes seems bent on
doing things the hard way. In recent times, though, the amount of effort
that has gone into development tools for the kernel has increased, with
some interesting results. Recent developments in this area include the
Sashiko code-review system, a patch-review manager built into b4, and a new
attempt at a framework for the specification and verification of kernel
APIs.

Btrfs Performance From Linux 6.12 To Linux 7.0 Shows Regressions

Last week I provided a look at the EXT4 and XFS performance from Linux 6.12 LTS through Linux 7.0 in its current development form. As mentioned in that article and as requested by many Phoronix readers, benchmarks have since wrapped up looking at how the Btrfs copy-on-write file-system performance has evolved since that late 2024 period and all major Linux kernel releases past that Long Term Support version.