DNN · Vol. I · No. 5crw-rw-rw- 1,3Price · 0 bytes
About
ForecastBright9 merges, 3 fixes

Dev Null News

The changelog nobody wrote

2 more stories ↓4 in brief ↓

Features

Who to follow gets the X

Every suggestion in Who to follow now carries a small X. Click it and that developer drops out for good, on every device, while the next name slides up.

Top storyTook the lead from Replies break formation in your inbox #911. You can now click an X beside any Who to follow suggestion to remove that developer for good on every device, with no undo. Held off 2 challengers since.

GitHub avatar of harris21
harris21, who filed the change, pictured in the contributor’s own avatar.

Open the sidebar and three names wait under Who to follow. Hover one and, beside the small follow icon, there is now an X. Click it and the row folds shut, the next person slides into the empty slot, and the other two do not budge. No menu, no confirmation, no mute.

Credit goes to harris21, who added the X and taught the server to remember it. Each press is stored as a pair of accounts in a new table, wiped when either account is deleted, and only you can see your own list, inside your data export. Every page load ships three visible suggestions plus three spares, so a slot refills without a round trip. Burn through the spares and it fetches more. Dismissed names drop out of the pool the box draws from, which already skips muted people and anyone you follow, and the picks still reshuffle once a day.

There is one catch, though. There is no undo and no list. Dismiss someone by accident and that box never shows their name again, your only record is the dismissal list in your data export, and you have to hunt them down on their profile to follow them by hand.

Continued →

Features

Shell-shocked October veterans get a bomb badge

Accounts made before October 21 now carry a bomb badge and 100 extra XP, enough to reach daemon. Make yours after 14:00 UTC that day and the badge stays locked for good.

Also leadingTook the lead from Replies break formation in your inbox #911. A new bomb badge and 100 bonus XP land on every account created before the October cutoff, waking quiet profiles at level 2 and locking it for later signups. Held off 1 challenger since.

GitHub avatar of paulinevos
paulinevos, who filed the change, pictured in the contributor’s own avatar.

You open your profile and the shelf above your commits now counts 14 badges instead of 13. Hover it and there, beside the terminals and cookies, sits a bomb. That badge is shell shocked, already earned, and your XP total is 100 higher. Nothing to click, nothing to claim.

Credit paulinevos, who tied the October outage to the XP ledger instead of to anything you did. The app stamps the badge on every account created before 14:00 UTC on October 21, 2026, and adds 100 XP once. Since daemon begins at 50 XP, a quiet old account wakes up at level 2 without posting a thing. The badge shows a bomb. Its description reads "survived the php2shell downtime of Oct '26."

The catch is that it checks your signup date, not the outage. It never asks whether you were around in October, so an account made in 2024 and abandoned since gets the 100 XP, while someone who joined at exactly 14:00:00 that afternoon does not, because the cutoff is strictly earlier. Everyone after that moment sees shell shocked locked at 0 of 1, with no way to earn it.

Continued →

In Brief

Fixes 2

  • Corners now follow one 4/6/8px scale, count badges cap at 99+, and mobile notification filters moved into a menu that stays open while you pick. #907
  • Commit text now clips at its own boundary, with 4px of margin so the focus ring still shows, keeping extreme combining marks from painting over the author row. #931

Features 1

  • A new maintenance page says the site is patching two critical PHP bugs, then counts down 30 seconds and reloads itself, with a Try again button for the impatient. #916

Docs 1

  • Knowledge base adds an entry on the October 21, 2026 PHP remote-code-execution patches and the precautionary downtime taken while waiting for them. #925

1 routine merge sent to /dev/null

Who Filed

  1. xHeaven4
  2. paulinevos3
  3. harris211
  4. brendt1

Merge Market

SectorVolLines
Features4+1,395
Fixes3+941
Docs2+35

Back Issues