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

http/permissions

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

HTTP plugin permissions configuration

HTTP plugin permissions are configured in src-tauri/capabilities/default.json. The configuration includes a permissions array with objects containing identifier (e.g. 'http:default'), allow array (with url patterns to permit), and deny array (with url patterns to block). Example: identifier 'http:default' with allow [{ 'url': 'https://*.tauri.app' }] and deny [{ 'url': 'https://private.tauri.app' }].

Upload plugin permission scope default

The default permission scope for the upload plugin is `upload:default`. This must be added to the `permissions` array in the capabilities configuration file (e.g., `src-tauri/capabilities/default.json`) to enable the plugin's functionality.

Give your agent this brain