Open the original 1611 King James Bible, and between the Old and New Testaments you will find a section called the Apocrypha, including Tobit, Judith, Wisdom and Maccabees. Many readers who grew up with the KJV have never seen these books inside it. Their presence did not mean its publishers gave them the same authority as the other Scriptures, but it complicates the idea that Protestant Bibles always excluded them entirely. Catholic tradition receives several of these writings as Deuterocanonical Scripture, while Orthodox collections vary and often extend further. These differences grew through centuries of transmission and decisions about which writings the Church should receive as Scripture. The Bible’s familiar table of contents has a history of its own.

Google DeepMind researchers used agentic AI to mathematically prove, or “formally verify,” a number of the Signal protocol’s key cryptographic guarantees—a landmark development for the widely used cryptography and AI itself.

Conducted as a sort of proof-of-concept project in just four weeks, the work is significant in two ways. It serves as further independent validation of the cryptography that protects massive quantities of the world’s communications on platforms like the Signal app, Google Messages, and WhatsApp. And it demonstrates Google DeepMind’s formal verification capabilities using a new AI framework called AlphaProof Code. //

Proponents of formal verification have long referred to it as a sort of holy grail in software security, because it uses math to check and validate that software is functioning as intended—in other words, that it doesn’t have critical vulnerabilities.

Before the AI era, it was incredibly time-consuming for people to describe the characteristics of software they wanted to prove, turn these summaries into formulas, and then develop the proof. Agentic AI can significantly cut down the time of the latter project, enabling analyses like DeepMind’s Signal evaluation. But even this analysis was limited in scope—it did not, for example, formally verify the entire Signal mobile app—and DeepMind researchers emphasize that their findings are just one milestone in a larger process. //

The DeepMind analysis did not find any new vulnerabilities in the portions of the Signal protocol it looked at, but when the researchers used AlphaProof Code on older versions of Signal that contain known and long-fixed vulnerabilities, it correctly identified them and showed that the protocol could not be formally verified. The researchers are releasing the specification and proof they developed for the Signal protocol analysis to aid other formal verification work. //

The open question across the tech sector, though, is whether AI-automated formal verification can truly scale—and whether it can do so at a workable cost. DeepMind conducted the Signal analysis free of charge as a research project, and Google declined to share the cost of the analysis. The company also declined to comment on whether it has plans to release a commercial formal verification product or service.

1. Float Charging Voltage:
   The float charging voltage is set at a lower level, usually between 13.2 to 13.8 volts, to maintain the battery’s full state of charge without overcharging. This setting is essential for keeping lead-acid batteries in a ready-to-use state, especially in applications where they are not frequently used.

2. Temperature Compensation:
   Temperature compensation adjusts the charging voltage based on ambient temperature changes. As temperatures rise, the charging voltage should be decreased to prevent overcharging. Conversely, the voltage should be increased in colder conditions. This ensures optimal battery performance and longevity.

The recommended voltage for float charging lead-acid batteries is typically between 2.2 to 2.3 volts per cell. This charging method maintains the battery at a fully charged state without overcharging, ensuring longevity and optimal performance.

It was on the third day of August that Joe come off the assembly line, and on the fifth Laurine come into town, an' that afternoon I saved civilization. That's what I figure, anyhow. Laurine is a blonde that I was crazy about once—and crazy is the word—and Joe is a logic that I have stored away down in the cellar right now. I had to pay for him because I said I busted him, and sometimes I think about turning him on and sometimes I think about taking an ax to him. Sooner or later I'm gonna do one or the other. I kinda hope it's the ax. I could use a coupla million dollars—sure!—an' Joe'd tell me how to get or make 'em. He can do plenty! But so far I've been scared to take a chance. After all, I figure I really saved civilization by turnin' him off. //

It "It was a nice kinda world once," I says, bitter. "I could go home peaceful and not have belly-cramps wonderin' if a blonde has called up my wife to announce my engagement to her. I could punch keys on a logic without gazing into somebody's bedroom while she is giving her epidermis a air bath and being led to think things I gotta take out in thinkin'. I could—"

Then I groan, rememberin' that my wife, naturally, is gonna blame me for the fact that our private life ain't private any more if anybody has tried to peek into it.

"It was a swell world," I says, homesick for the dear dead days-before-yesterday. "We was playin' happy with our toys like little innocent children until somethin' happened. Like a guy named Joe come in and squashed all our mud pies."

In the May 2000 issue of Reason Magazine, award-winning science correspondent Ronald Bailey wrote an excellent article titled “Earth Day, Then and Now” to provide some historical perspective on the 30th anniversary of Earth Day. In that article, Bailey noted that around the time of the first Earth Day in the 1970, and in the years following, there was a “torrent of apocalyptic predictions” and many of those predictions were featured in his Reason article. Well, it’s now the 47th anniversary of Earth Day, and a good time to ask the question again that Bailey asked 17 years ago: How accurate were the predictions made around the time of the first Earth Day in 1970? The answer: “The prophets of doom were not simply wrong, but spectacularly wrong,” according to Bailey. Here are 18 examples of the spectacularly wrong predictions made around 1970 when the “green holy day” (aka Earth Day) started:

Scène de ballet, pour cordes, harpe et timbales, en mi majeur
Joseph Hellmesberger

In partnership with Hillsdale College, The Golden Thread Curriculum offers a rigorous, structured approach to the teaching of Western Civilization—one that restores coherence to history and equips students to understand the enduring questions, traditions, and tensions that run through the history of the West—from antiquity to the present.

THE NAZARENE
You know how he died.
Read how he lived.

Read free →
The whole first book is free. No account needed.

The life of Jesus as a novel, in four books, by EKO

Genes and archaeology are revealing how Bantu speakers spread across much of Africa. //

Scientists are extremely interested in the peoples who created this and other iron-powered societies across eastern and southern Africa. Research points to an adaptable and innovative group from western Africa as the masterminds. Known as Bantu speakers, these communities began gradually expanding across the continent’s southern half, starting from 6,000 to 4,000 years ago. In doing so, they introduced a fundamentally new, sedentary way of life—characterized by farming, raising livestock, pottery-making, and metalworking—to regions previously dominated by hunter-gatherer communities.

This migration transformed not only the region’s history and technology, but also its languages: Today, around 350 million Africans speak one of roughly 500 distinct Bantu tongues, from southern African Zulu to eastern African Swahili. And at least as many Africans—as well as many African Americans and Afro-Latinos—carry Bantu ancestry in their DNA. //

Linguists working in the 19th century started referring to the language family as Bantu, the plural of muntu, meaning “human being” in many Bantu tongues. Later linguists reasoned that the languages stemmed from an ancestral people who migrated across the continent from western Africa, which harbors the greatest diversity of Bantu languages (as would be expected for where the languages originated).

I was made aware of a small open source utility called scrutiny. It is very nice. Imperfect but a lot better than just running smart tests. It has small footprint and can help me see all disks from all systems in my home and lab in a single place.
I intend to add the how-to for anyone interested. I spent some hours over the week in getting to do what I wanted.
First, the project's home is here https://github.com/AnalogJ/scrutiny . Has 90% I'd say of the information needed. The remaining bits are the details for each type of system.
Second, this is a docker thingie that I'm not a fan of but the non-docker option is still a self-container utility in go language so it doesn't give me what I prefer like a front end and application I can configure independently. So I went with docker and using docker compose.

I used the mixed mode of hub & spoke. That is a "server" listening (the hub, using docker) and each system I want to monitor its disks are spokes, using the binary locally which sends the metrics to the hub.

ZNAS - Easiest and most beautiful NAS Management UI Ever

Why ZNAS?

Most NAS software is slow to install, slow to load, and buried under layers of configuration. ZNAS is the opposite.

• Up and running in minutes. Flash a USB stick and boot, or run one command on Debian or Ubuntu, then create your admin account in the browser.
• One binary, nothing else. No Docker, no Node, no Python runtime, no database. The whole portal, UI included, is a single file that starts in under a second.
• Storage, sharing and virtualization together. ZFS pools, SMB/NFS/iSCSI shares, VMs, containers and Compose stacks, all managed from the same place.
• Always current, never disruptive. Updates are signed, applied in one click and take effect in seconds, like a modern browser. The previous version stays as a fallback.
• Secure by design. HTTPS only, roles with fine-grained permissions, two-factor login, an audit trail of every action, and optional sudo hardening.
• Built for real homelabs. Manage several servers from one window, back VMs up to another box, watch your UPS, and get alerts wherever you want them.

1. Flash it to a USB stick, boot your NAS from it, and open the address shown on the screen. That's it.

2. Prefer a regular install? One command on Debian 13+ or Ubuntu 26.04+ sets up ZFS, a service account, the portal and its systemd service.

FreeCORE continues TrueNAS® CORE 13.3 as an independently maintained operating system for NAS appliances, with in-place upgrades to FreeCORE 15.0 and 15.1.

An independently maintained operating system for NAS appliances, on FreeBSD® 15 with OpenZFS.

My squadron ops officer had a peculiar view of this inspection, however. As one of the Seagull (have to throw rocks at them to make them fly) brothers I mentioned earlier in the book, he flew very little and absolutely would not fly in command with ASEV evaluators. His mantra said this was a reservist inspection and they should carry the load, not the technicians. //

A few weeks after that I dropped by Base Personnel to review the OER to see what kind, and level, of endorsements I had received. In reading the front of the form, however, I saw the statement citing my flying in command for ASEV had been removed.

A tough call
The next time I was in the squadron I stepped into the ops officer’s office and brought this to his attention. “I can’t find the sentence about me flying in command with ASEV,” I said.

He frowned and nodded his head to imply he had had to make a difficult decision and said: “I know, Jay, it was a tough call but I had to remove that sentence. It would have made all the other ARTS [especially him] look bad.”

Stunned, I couldn’t even speak, and didn’t.

I turned, walked down the hall to another office, and called Larry Mercker at Westover.

“Larry,” I said, “I’m ready to move, is that position still open?”

It was, and off I would go to Westover for the next five years as ADO.”

Romance pour alto et orchestre op.85
Max Bruch

L'œuvre
Romance pour alto et orchestre, en fa majeur (Op. 85)

Tempo di Mazurka
Alexander Müller

L'œuvre
Tempo di Mazurka, pour piano

System mails generated by your Plesk server, such as bounce notices from MAILER-DAEMON@hostname.example.com, cron output from root@hostname.example.com, or Plesk notifications, often land in the spam folder, even though normal user mailboxes (e.g. info@example.com) deliver fine.

This happens because your server’s hostname is a subdomain of your main domain, and your main domain’s DMARC policy is silently inherited by every subdomain that does not publish its own. Without dedicated authentication for the hostname, self-generated system mail fails DMARC alignment and is quarantined by your own authentication stack.

This article walks through the root cause, the one-DNS-record fix that solves the visible symptom for most admins, and the full authentication setup for getting non-bounce system mail to genuinely pass DMARC.

The quick fix: override subdomain inheritance

Add a dedicated DMARC record for your server hostname with p=none:

_dmarc.hostname.example.com.  IN  TXT  "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"

This overrides apex inheritance for the hostname subdomain only. Your main domain DMARC policy stays strict, your user mailboxes stay protected, but system mail from the hostname stops being quarantined.

This single record solves the symptom for most admins. No Plesk changes are required. No server configuration is required. //

If you also want cron output and Plesk notifications (not just bounces) to genuinely pass DMARC, continue to the complete fix below. If you just want your system mail out of spam, you can stop here.

Open the panel.ini editor using the command:

 plesk conf panel.ini

Using the Plesk Panel Interface:

1. Install the Panel.ini Editor from the Extensions menu in Plesk.
2. Open Panel.ini Editor at Extensions > My Extensions.
3. In Panel.ini Editor, switch to the Editor tab. If the editor is empty, do the following...
4. Edit the content and click Save

Plesk administrator can specify a custom email address to be used as a mail relay. The email address will be used as the sender address for all Plesk email notifications enabled in the Tools & Settings > Notifications menu.

To adjust the settings, perform the following:

1. Log into Plesk
2. Edit the Plesk panel.ini file by adding the lines below there:

   [notification]
   senderAddress=<custom email address>

Balada d floripondios du Concierto de Otoño
Arturo Márquez

L'œuvre
Concierto de Otoño. Concerto pour trompette et orchestre

Tailscale’s download page doesn’t list if it’s available for FreeBSD. But it does work on FreeBSD (tested on Release 14). Here’s how:

Install the package:

 pkg install tailscale

Edit /etc/rc.conf to add tailscaled_enable="YES"
or

service tailscaled enable

Run service tailscaled start. If you get an error, reboot.

After reboot, run tailscale login.

Copy the url, copy paste in a browser and approve the connection. ////

XigmaNAS:

Copy /usr/local/bin/tailscale, /usr/local/bin/tailscaled and /usr/local/etc/rc.d/tailscaled to local storage from working full version of FreeBSD.

Use script to copy symlinks into /usr/local/bin and /usr/local/etc/rc.d/ after bootup.

Configuration and State Storage

The default configuration file locations for Tailscale on FreeBSD is /var/db/tailscale/ for state files and configuration settings. Additionally, logs can be found in /var/log/tailscale.