- the client (1.3.0) sends one-way hashes of the device's ids at
sign-in; the server keys them again with a secret of its own
(data/device-key) and keeps them per account (lib/devices.js). a
sign-in without them is refused with 426 (AJ_REQUIRE_DEVICE=0 lets it
in), so 1.2 clients cannot sign in.
- hardware bans: every device an account used in the last 90 days.
any id but a network card blocks sign-in, sign-up and the game, on
any account. a network card match, ids that look altered, or a device
shared with a banned player raise hardware alerts instead.
- both panels: hardware ban and lift, the account's hardware ids,
search by hardware id, other accounts by device or address, a
timeline (bans, staff actions, reports, alerts), and hardware bans
and alerts in the bans tab.
- jam-a-grams and wall posts go into the chat log, the filtered ones
marked not sent. chat search filters by kind, by what the filter
stopped, and from a time back; each player's page lists their
jam-a-grams and wall posts, sent and received.
- account search runs on the server and ranks exact names first, then
names starting with the search; the admin panel no longer downloads
every account. hidden tabs only refresh the waiting counts in the
title. masterpieces can be searched by maker, approved ones too.
reports can show the reported player's chat at the time. links follow
the open tab and player.
- admin actions on accounts go into the moderator log.
- privacy policy covers hardware hashes and the new logs.
- lib/chatfilter.js reads its rules from lib/chat-filter.txt (reloaded
when it changes) and applies them to typed chat, jam-a-gram messages
and jammer wall posts. players cannot turn it off. a blocked message
reaches nobody, its sender sees the game's "inappropriate behavior"
warning, and blocked chat is kept in the chat log marked not sent.
- rules match words, prefixes and phrases, in order or anywhere, with
"?" for any word and "!" for exceptions, and see through stand-in
letters, drawn-out letters and spaced-out spelling. the example rules
block sexual talk aimed at someone while letting plain swearing
through; the slur section is left for the owner to fill in.
- secret valentine jam-a-grams are off: the client sends a normal card
without asking (buildVersion 56), and the server refuses a card asked
for as a secret valentine.
Ping on prod jumped to seconds because node's main thread was busy most
of every second.
- accounts.save(account, ...) names the changed accounts, which are
written within a second; the rest are looked at a few at a time
(10 ms a save for those in play, 5 ms for the others). One save under
prod-like load: 289 ms before, 16 ms after.
- an asset the CDN does not have gets a cacheable 404 and is logged once
- the proxy's own connections no longer count against the web cap, which
had node reset requests nginx had already let in
- a repeated client error is written once in ten minutes; the panel's
log buffer trims in batches
- the daily backup uses sqlite's online backup off the main thread
- stats graphs for the admin and moderator panels (lib/stats.js, public/stats-view.html)
- playtime, private unless shown on the card's bio tab; set on the account page
- search accounts by ip address, only against ban evasion; mods see no addresses and each search is logged
- privacy policy for the above (terms version 2026-10-17)
- the per-second save looks only at accounts in play, with a slow sweep of the rest
- items in several dens at once; chat filter hides slurs and threats by default
- sexual usernames refused; moderators may enter full rooms; guide login allowed
- 150-character chat box (client build 55)
- fixes: gifts, trades, dens, pets in dens, den recycling, special animals' colours,
jammer walls, settings switches; the buddy list sent at login
- the item giver, the rules screen and the art studio rework
Security workflow, on every push, pull request and weekly:
- invariants: no npm packages, no child_process/vm/eval in the server,
no web address outside .github/allowed-hosts.json in the server or in
the SWFs players load, no committed keys, all JavaScript parses
- secrets: TruffleHog over the pushed commits
- codeql: security-extended queries for the JavaScript and the workflows
Commit messages are checked against Conventional Commits; the commits
publish-public.sh makes are exempt. Actions are pinned to commit SHAs.
Co-Authored-By: Claude Opus 5.5 <[email protected]>