v1.34.0
1.34.0 - 2026-08-19
Changed
-
The unpacked extension bundles are no longer carried in git.
dist/extension-chrome/and
dist/extension-firefox/are build output thatnpm run verifyregenerates on every commit
touchingsrc/— 1.9 MB of incompressiblecontent.jsper target, per commit, that nothing read:
the load-unpacked instructions and the release artifacts both come from a build. They are ignored
and built on demand;dist/aviary.user.jsanddist/aviary.meta.jsstay tracked because a
userscript manager polls them by raw URL.docs/INSTALL.mdnow says to build first, for both
browsers. -
Every release named in this file now has a tag on the commit that bumped its version. Nine
releases were tagged and thirty-one were documented, so most of the project's history could not be
checked out, diffed, or bisected by reference — which is the wrong gap for a project whose most
frequent question is "when did this selector break". Twenty-four tags were added, located by the
commit that changedpackage.jsonrather than by commit subject, since not every release commit
said "release". The two releases with no entry at all, 1.7.0 and 1.15.0, are written below
from their own commit ranges and labelled as reconstructed.
Added
- Copy a post's link for an alternate front-end. Library gains a Copy post links as choice
(X, fxtwitter, vxtwitter, fixupx, xcancel); pick anything but X and each post grows a Copy
link control that writes that post's address on the chosen host. Deliberately copy-time
rewriting rather than redirection: redirectingx.comnavigation is the shape everyone else
shipped and has since removed, because logging in through the alternate host now sets anx.com
cookie and the front-ends people redirected to have been architecturally dead since X removed
guest tokens. Nothing X rendered is modified, no navigation is redirected, and no request is
originated — only what you copy changes. Off by default, and the host list is closed so a typo
cannot produce a link to somewhere you did not mean.