The proxies page grouped by a filter and by a click: a "Members only" chip
narrowed the list to the group in view, and clicking a card or a list row
joined the node to that group or took it out. Both are gone. Membership is
always asked for now: the node menu's Add to proxy group submenu lists every
group the core knows and marks the ones the node is already in, its Remove
from proxy group submenu lists the groups the node belongs to, and the batch
bar puts the same question for the whole selection. The in-use member picker
left with them - the dashboard's group card still picks the member the group
routes through - and the model state that only served it is gone.
Selection reaches both views: every node card carries a checkbox beside its
name, and the batch bar (select all, the count of selected nodes, test
latency, add to and remove from a group, delete, export) now sits above the
cards and not only above the list. Export asks where the sharing links go:
the clipboard as before, or a file named export- and the moment it was taken
(lib/download.ts). On a phone the bar keeps only test latency and folds the
rest into a More actions menu, whose export entries are flattened a level.
The dashboard's group card names the group it shows and switches it in place:
its header is the app bar's group button beside the words "Proxy group", and
its "Add nodes" button is "Add or remove nodes", which the title of the group
editor follows.
Six locales carry the new strings and drop the eighteen keys of the retired
group filter, the add-to-group dialog, the dashboard buttons and other
leftovers, and the six quick-start pages follow the renamed buttons.
v2rayA dropped allowInsecure years ago: VMess, VLESS and Trojan links carrying it
are parsed and the flag ignored, and a self-signed server is reached by pinning
its certificate. The three native protocols added in May brought the switch back
in their own config, service objects and forms. It goes everywhere: the core's
dialers verify or pin (the proto field 5 is reserved), the service no longer
parses, stores or exports allow_insecure for them, the forms lose the switch,
the codec ignores the parameter, and the quick-start docs say so in six locales.
Certificate pinning stays as it was.
The proxies page carried a second toolbar of group features: the group chips,
New group, the in-use member picker and the group settings/delete menu. The
app bar's group button already lists, creates, configures and deletes groups,
and the dashboard's group card already picks the member in use and edits the
members, so the row goes. Membership from the nodes page stays as node
actions: the card and its menu toggle the current group, and the batch bar's
Add to group / Remove from group open a menu of groups. The dashboard's
"Edit group" button is "Add nodes". Six quick-start pages follow.
useHotkeys: a window keydown listener for a page's life, silent while a dialog
is up or the user is typing (only Ctrl/Cmd+S reaches the page from a field).
Proxies: Ctrl/Cmd+A selects every listed node in the list view, Escape clears,
"/" goes to the search. Settings: Ctrl/Cmd+S saves what changed. Logs: "/"
goes to the search. Dialogs with a text area (import, subscription, excluded
domains, whitelist IPs, TUN processes, route scripts): Ctrl/Cmd+Enter submits;
the GFWList link field submits on Enter. The RoutingA editor already had
Ctrl+S and Tab. The quick-start docs list them in six locales.
The proxies page listed the subscriptions above the nodes behind a fold, and on
a phone its toolbar, the fold, the node toolbar and the group row stacked into
a wall of buttons. Subscriptions are a destination of their own now: the cards,
Auto-update and Import a subscription, sharing the proxies model. The bottom
bar keeps Material's five (dashboard, proxies, subscriptions, settings, logs);
on a phone the docs are a button in the app bar next to the groups and the
menu, and under 440 px the bar shows the logo without the wordmark so the
status pill and the three buttons fit (measured at 320 to 430; the wordmark is
back from 440, where it has room). The rail and the drawer list all six. The
quick-start docs say so in six locales.
The Release_to_AUR job of _release.yml moves to _release_aur.yml (workflow_call,
input tag); the release calls it as before, after GitHub_Release and only with
publish_downstream. release_aur.yml runs it alone from workflow_dispatch, for the
case where the release went through and only the AUR step failed, as with 2.5.5.
833af7dc replaced 'git add .SRCINFO .INSTALL && git commit -a' with 'git add -A',
which also staged the installer_archlinux_*.pkg.tar.zst that updpkgsums downloads
into aur/v2raya-bin; the AUR hook rejected the 2.5.5 push (maximum blob size
488.28KiB exceeded). 'git add -u' stages the PKGBUILD and .SRCINFO changes and
the .INSTALL deletion, and nothing new.
Settings had a Multiplex switch and a concurrency field, validated and stored,
that no template code read. VMess outbounds get mux.enabled and the
concurrency when the switch is on, which is what the help text promised
("vmess only"). The core accepts the result (run -test).
The DNS help button linked v2fly's documentation of a different DNS
implementation; the docs button opens the transparent proxy page, whose DNS
section describes the core's module. The SS and Trojan forms offered a
"backend" of "system default" or "v2ray / xray", both the same core since
2.4.6; the link parameter v2raya-backend is still parsed and re-emitted.
Strings that still named v2ray-core, "v2ray / xray" or a wiki: six locales
(the core is v2raya_core; the invalid-service message, the SS plugin help,
the transparent-proxy hint, the TUN example, the custom inbound tag hint),
the --v2ray-bin, --core-startup-timeout and --plugin-manager descriptions
and their copies in the OpenRC confd files (the plugin manager is called
with --stage=parse|configuration, --link and --v2raya-confdir, not with
life-cycle stages), two comments that forbade or excused the current design,
the package descriptions that listed SSR, the AUR Go minimum (go.mod says
1.26), the systemd Documentation= and the installer's shortcut that pointed
at the wiki and the docs site, and the README sentence on network requests,
which left out the weekly release check and the NTP query on VMess failure.
copyfile, the empty ports/ss.go stub, parseDnsAddr and DnsRouting (the DNS
config is generated for the core's module now), the Inter font and the
switch-menu icon of the old GUI, the docs-site dispatch workflow (the site is
retired; the docs are in the app), the unused v2ray_arch in the docker helper,
the root .gitignore rule for a web directory that moved, and the .dockerignore
patterns for binary and test names that no longer exist. The skipped
TestFillEmpty asserts what FillEmpty does instead of what it once did.
The six locales' transparent-proxy pages explain --redirect-respect-bound-device
after the excluded prefixes; the flag table on the parameters page already lists
it. The "(geosite)" suffix on the local GFWList date is a locale string.
--redirect-respect-bound-device was the first field of Params, so it led
--help, --report config and the /etc/default/v2raya the packages generate
from it; it now follows --ipv6-support. Its description says what it does
in the user's terms (SO_BINDTODEVICE, NetworkManager's connectivity
checks) and what it needs (kernel 5.7, cgroup v2). When SO_NETNS_COOKIE
is missing the error says the kernel is too old instead of ENOPROTOOPT.
cilium/ebpf moves to the direct require block, as go mod tidy puts it.
Currently, if system /usr/share/v2raya/geosite.dat is used, v2raya will
not post error, but will display "none" for local GFWList date.
Since v2rayA reads this compatible file, we should display a date for
it, so that user is not confused.
Assisted-by: GPT-5.6-terra
A menu button by the brand folds the standard drawer; the rail that
replaces it is the one the medium window already uses, with the same
menu button at the top to unfold. The choice is kept in localStorage.