Anybody else having trouble with v4.5.9?

My test upgrade, upgrading from v4.5.8 and following the non-docker directions from the release notes, failed on the precompile stage with:

$ RAILS_ENV=production bundle exec rails assets:precompile
I, [2026-04-15T17:45:42.657379 #67936] INFO -- : [dotenv] Loaded .env.production
Building with Vite ÿ
yarn run v1.22.19
$ /usr/home/mastodon/live/node_modules/.bin/vite build --mode production
vite v7.3.2 building client environment for production...
transforming...
✓ 1901 modules transformed.
info Visit yarnpkg.com/en/docs/cli/run for documentation about this command.
✗ Build failed in 11.89s
error during build:
[vite-plugin-pwa:build] [plugin vite-plugin-pwa:build] assets/worker-!~{001}~.js (323:31): There was an error during the build:
Could not load /usr/home/mastodon/live/app/javascript/mastodon/features/emoji/worker.ts?worker&inline (imported by app/javascript/mastodon/features/emoji/index.ts): Transform failed with 5 errors:
assets/worker-!~{001}~.js:323:31: ERROR: Transforming destructuring to the configured target environment ("chrome64", "edge79", "es2020", "firefox67", "safari12" + 2 overrides) is not supported yet
assets/worker-!~{001}~.js:1133:8: ERROR: Transforming destructuring to the configured target environment ("chrome64", "edge79", "es2020", "firefox67", "safari12" + 2 overrides) is not supported yet
assets/worker-!~{001}~.js:5721:13: ERROR: Transforming destructuring to the configured target environment ("chrome64", "edge79", "es2020", "firefox67", "safari12" + 2 overrides) is not supported yet
assets/worker-!~{001}~.js:5816:8: ERROR: Transforming destructuring to the configured target environment ("chrome64", "edge79", "es2020", "firefox67", "safari12" + 2 overrides) is not supported yet
assets/worker-!~{001}~.js:5817:10: ERROR: Transforming destructuring to the configured target environment ("chrome64", "edge79", "es2020", "firefox67", "safari12" + 2 overrides) is not supported yet
Additionally, handling the error in the 'buildEnd' hook caused the following error:
Could not load /usr/home/mastodon/live/app/javascript/mastodon/features/emoji/worker.ts?worker&inline (imported by app/javascript/mastodon/features/emoji/index.ts): Transform failed with 5 errors:
assets/worker-!~{001}~.js:323:31: ERROR: Transforming destructuring to the configured target environment ("chrome64", "edge79", "es2020", "firefox67", "safari12" + 2 overrides) is not supported yet
assets/worker-!~{001}~.js:1133:8: ERROR: Transforming destructuring to the configured target environment ("chrome64", "edge79", "es2020", "firefox67", "safari12" + 2 overrides) is not supported yet
assets/worker-!~{001}~.js:5721:13: ERROR: Transforming destructuring to the configured target environment ("chrome64", "edge79", "es2020", "firefox67", "safari12" + 2 overrides) is not supported yet
assets/worker-!~{001}~.js:5816:8: ERROR: Transforming destructuring to the configured target environment ("chrome64", "edge79", "es2020", "firefox67", "safari12" + 2 overrides) is not supported yet
assets/worker-!~{001}~.js:5817:10: ERROR: Transforming destructuring to the configured target environment ("chrome64", "edge79", "es2020", "firefox67", "safari12" + 2 overrides) is not supported yet
file: assets/worker-!~{001}~.js:323:31

Transforming destructuring to the configured target environment ("chrome64", "edge79", "es2020", "firefox67", "safari12" + 2 overrides) is not supported yet
321 | * @param callbacks Additional callbacks.
322 | */
323 | function openDB(name, version, { blocked, upgrade, blocking, terminated } = {}) {
| ^
324 | const request = indexedDB.open(name, version);
325 | const openPromise = wrap(request);

Transforming destructuring to the configured target environment ("chrome64", "edge79", "es2020", "firefox67", "safari12" + 2 overrides) is not supported yet
1131 | }
1132 | module.exports = requireCommon()(exports$1);
1133 | const { formatters } = module.exports;
| ^
1134 | formatters.j = function(v) {
1135 | try {

Transforming destructuring to the configured target environment ("chrome64", "edge79", "es2020", "firefox67", "safari12" + 2 overrides) is not supported yet
5719 | )
5720 | );
5721 | for (const [locale, loaded] of locales) {
| ^
5722 | if (loaded) {
5723 | loadedLocales.add(locale);

Transforming destructuring to the configured target environment ("chrome64", "edge79", "es2020", "firefox67", "safari12" + 2 overrides) is not supported yet
5814 | self.postMessage("ready");
5815 | function handleMessage(event) {
5816 | const {
| ^
5817 | data: { locale, path }
5818 | } = event;

(continued..)

#mastodon #mastoadmin

PSA: I have just cleaned a set of russian misinfo spambots from this instance.

⚠️ We moderate registrations, and have invites enabled. ⚠️

This is how they got in:

• 8 days ago (mar 29) they requested an account. The request did not appear LLM generated. The request was topical enough to meet our flexible informal threshold, and read as clumsy English.
• 6 days ago (apr 1) I reviewed and approved the account.
• Their signup email accounts were from the emailondeck tempmail provider. Each domain was different. I only bother looking at the email domain if there are other red flags. (A lot of people who choose us are technical with their own email domains. Random domains don't stand out.)
• They signed up from an IPv6 address and only ever connected from 1 IP.
• They made 0 posts from this account. They did not set a bio. They did not set a PFP.
• They created 1 invite code for 5 uses.
• 5 days ago this invite code was used to make 1 account. They did not post anything, nor did they set a bio or PFP.
• That second account, and all other accounts, used IPv4. They also only connected from 1 IP.
• Over the next 4 days, the final 4 accounts via that invite code were made.
• These accounts set bios that were a few random words and an emoji. They made the non-hashtag variety of posts the misinfo accounts make; bland word salad poetry. They boosted a bunch of other posts to try look normal.
• All IPs involved have been labelled by spur.us as OPEN_ROUTABLE_PROXY and the IPv4 ones were also labelled as TOR_PROXY.
• The admin interface identifies the posts as using clients called "ssl", "scsi", "ib".

The cleanup procedure:

• Ban the accounts immediately.
• Deactivate the invite code immediately.
• Review other recently created accounts and invite codes.
• Write this all down for future reference.

Notes:

It's easy to be complacent when you've got account creations moderated or by invite codes.

Chances are that if I had not noticed, each of the active accounts may have created their own invite code. and there would have been another 20 or more of them.

#fediblock #mastoadmin

We've successfully MEGA-upgraded our Mastodon server to v4.6.0-alpha.6+mementomods-2026-04-05, along with Mastodon Bird UI 4.0.0-alpha.6 (nightly).

This update includes today's latest daily build with 163 new commits from upstream since mementomods-2026-03-21.

What's new in Mastodon core - These are the changes Mastodon Team have introduced us in the latest nightly version we are running:

✨️ New features

- Profile redesign is now live (feature flag removed) — new layout with "Follows you" badge, split fields, rearranged number fields, featured tab, account featured tags nudge, alt text on avatars/headers
- Collections are now fully federated — remote account support, new page design, compact buttons, topic suggestions, tag linked FeaturedCollection objects over ActivityPub
- Email subscriptions on profiles — visitors can subscribe to public posts via email with MX record validation
- Profile editing — new API with character counter, field inline messages, avatar/header description uploads, visual fixes
- Support for FEP-2c59 and multiple keypairs for remote accounts
- Media description length limit increased from 1500 to 10,000 characters for remote attachments
- Improved relative time display when post time is in the future
- Disable extraneous Devise strategies option via `DISABLE_DEVISE_TWO_STRATEGIES`

🔧 Fixes & improvements

- Fix signature verification when key ID is an `acct:` URI
- Fix refreshing keys from stale actors on signature verification error
- Fix regressions in notifications caused by translation wrapper element
- Fix jump when loading more media gallery items
- Fix being unable to disable sound for quote update notification
- Fix Webfinger endpoint not handling new AP ID scheme
- Improve resilience of `tootctl maintenance fix-duplicates` command
- Improve contrast for `text-warning` and `text-success` design tokens

📦 Dependency updates

- Rails 8.1.3, Vite 8.0.3, TypeScript 6, Yarn 4.13.0, Ruby version 4.0.2
- Drop support for Ruby 3.2

🐦‍⬛ Mastodon Bird UI 4.0.0-alpha.6 (nightly)

- Fix translate button color not matching link color
- Fix extra border-left showing up in mobile devices
- Fix focusable background color standing out too much for account name
- Fix install script for Mastodon 2026-03-21 `common.scss` removal
- Fully modularize `_base.scss` into 40+ focused module files
- Fix Browsersync CSS hot reload by stripping CSP headers from proxied responses
- Support new profile page structure
- Remove calendar icon for "Joined" field no longer in new profile
- Style new profile page components and fix profile button colors
- Update theme tokens with latest design system tokens (upstream PR #38387)
- Remove select hack fixed in upstream
- Fix install script for new profile subdirectories

🔧 mementomods fork fixes

- Restored role badge colors lost in the profile redesign (reported upstream: github.com/mastodon/mastodon/i…)
- Fixed search reference page: migrated from removed `injectIntl` to `useIntl` hook, removed non-functional search operators

Source code: github.com/mementomori-social/…

As always, if you notice anything unusual or buggy, please reach out to me or any of the admins. Enjoy your time here, and feel free to message me with any questions or thoughts.

If anything feels off, please let us know!

#MementoMoriSocial #Mastodon #MastoAdmin

Just finished optimizing and checking things after being away from this machine in particular for a while. Our server stack could theoretically handle 5k more registered users and about 1500-2000 monthly active users before we'd need to start thinking about scaling up.

Right now, we have 889 users and around 410 monthly active ones and we're running at roughly 25-30% capacity. Plenty of space to grow.

We're federating with nearly 42000 other servers, which is actually the heaviest part of running an instance, not the local users. Every boost, reply, and follow across the fediverse adds work for our servers.

It was never my intention to grow this server this much or even have this many users, but now we have regular people, authors, political parties, organizations, YouTubers, and more. I'm still amazed about this. Yet I'm keeping a low profile because, even though we have our own admin team, at the end of the day this is still my hobby project organized by me and my wife.

That said, I've done my best to keep things as flexible as possible, and our finances are stable. I'm really glad my "hobby project" has brought so much joy to so many people.

If you know someone looking for a Mastodon home, we've got room 🏠

#MementoMoriSocial #MastoAdmin