Pulse 01 — Relaunch
What this publication is, what it will not do, and the three things we most need help with.
4 entries · 1 editorial · 2 calls · 1 note
Edited periodical
No community activity to show yet — so we are not going to fake any.
PerlCoders relaunched in 2026. Rather than render empty forum categories or a zero next to a heart icon, here is what actually helps right now.
What helps
Three things, in order of usefulness.
- 01 Submit a correction Especially on anything the Timeline marks unverified. A primary source for one of those six entries is the single most useful thing you can send us.
- 02 Submit an artifact Old scripts, screenshots, mailing-list captures — with rights information. One Archive entry has no established purpose at all.
- 03 Ask a question Answered in a Pulse issue or commissioned as a guide, with attribution if you want it.
What Pulse deliberately does not have
No member count, no reaction count, no view count, no leaderboard and no activity feed. Those fields
do not exist in the content model. If a future release adds community metrics they will come from
real recorded events and carry the same verification discipline as everything else on the site.
Issues
One issue so far.
Pulse publishes when there is something to say, not on a schedule that would force filler.
Discussion happens on GitHub.
We are not building a forum in this release. Discussions live where they are public, archived and searchable without an account we control — and article comment threads are backed by the same place.
PerlCoders editorial·opened the first thread
Which six Timeline entries would you source first?
Sourced corrections can be filed in the public GitHub repository. GitHub is linked, not embedded, so no third-party code runs when an article loads.
Public correction trail: GitHub issues.