new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Tauri · Plugins and security · all subjects

webview & configuration

7 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

WebKit2GTK version for Tauri 2.0

Tauri v2.0 uses WebKit2GTK–4.1 on Linux, requiring the new WebKit2GTK package with API version 4.1 instead of 4.0.

WebKit2GTK 4.1 installation on Arch Linux

To install WebKit2GTK 4.1 on Arch Linux or Manjaro, run: sudo pacman -S webkit2gtk-4.1

WebKit2GTK 4.1 installation on Debian/Ubuntu

To install WebKit2GTK 4.1 on Debian or Ubuntu, run: sudo apt install libwebkit2gtk-4.1-dev

WebKit2GTK 4.1 installation on Fedora

To install WebKit2GTK 4.1 on Fedora, run: sudo dnf install webkit2gtk4.1-devel

WebKit2GTK 4.0 vs 4.1 soup library difference

WebKit2GTK-4.0 uses soup2, while WebKit2GTK-4.1 uses soup3. Applications that do not use soup2-specific APIs should continue to work fine when upgrading.

Reason for WebKit2GTK 4.1 migration in Tauri v2.0

The WebKit2GTK 4.1 upgrade enables flatpak support, as the GNOME runtime uses webkit2gtk-4.1. Additionally, upgrading to soup3 fixes subtle bugs present in soup2.

Tauri v1.x unaffected by WebKit2GTK migration

Users on Tauri 1.x do not need to make any changes due to the WebKit2GTK 4.1 migration; it only affects Tauri 2.0 alpha versions starting from alpha.3.

Give your agent this brain