Today on meta.discourse.org…
Key Stats
In the last 24 hours, Meta saw 200 new posts across 61 new topics, with 240 likes given across the returned activity. The most active contributors were:
| User | Posts | Likes |
|---|---|---|
| NateDhaliwal | 11 | 22 |
| Scoresby | 14 | 18 |
| Chapoi | 12 | 18 |
| Merefield | 10 | 16 |
| Moin | 9 | 14 |
| Andrew_Rowe | 6 | 11 |
| Nickdb | 3 | 9 |
| Ed_S | 9 | 8 |
| Satonotdead | 9 | 7 |
| Awesomerobot | 4 | 7 |
Interesting Topics
#Community Building
-
Scoresby floated a bold idea: a
forum moderated by moneywhere posting, replying, and upvoting all carry small fees, with visibility ranked by community investment. Nickdb warned about creating a financial divide, Merefield argued that charging people to create content would scare off contributors, and Ed_S pointed to Metafilter’s $5 sign-up fee as evidence that a nominal barrier can encourage civility. The thread evolved into a broader discussion about token economies, spam resistance, and whether “Discoin” could ever work. read more -
Satonotdead shared striking data showing Reddit’s citation share inside ChatGPT collapsed from 3.83% to 0.52% in a matter of days, sparking conversation about what that means for support-forum traffic and the shifting web ecosystem. Merefield summed it up with a
. read more
#Announcements
-
The unified new view for the topic list continued to draw feedback. Damian_Boon initially thought
/latesthad changed, but Moin confirmed only/newwas affected. Mbauman offered a detailed critique, arguing the merged “new topics + unread replies” view intermingles individual tracking state with global topic creation state, and linked back to the original “new new” experiment that was reverted three years ago. read more -
Chapoi moved AI title suggestions into the composer helper and defended the consolidation in AI title suggestions move to composer helper. Jaroslav.Kovar and Jagster pushed back, noting that the hidden star icon used to be a visual cue and the new flow adds too much friction. Chapoi acknowledged the extra steps, explained the old implementation was noisy and costly, and teased future improvements where users “do not need to click anything at all.” read more
-
The redesigned admin dashboard received sysadmin feedback from Skodde, who asked for a selectable main block with classic Version and Backups information that doesn’t require the Docker Manager plugin. Chapoi confirmed something along those lines is already in the works. read more
-
Lindsey announced that Zoom webinars can now run as livestream events in the Discourse Events plugin, letting members watch the presentation, RSVP, join via Zoom, and keep chatting in Discourse after the event ends. read more
#Plugin
-
NateDhaliwal published the See TL3 Progress plugin, which shows TL2 users a progress bar toward TL3, optional detailed requirement breakdowns, TL3 warnings, and hints about muted topics. Lilly spotted a missing summary in the plugin listing, NateDhaliwal fixed it, and the plugin is now ready for broader use. read more
-
In Discourse Workflows, J.Jaffeux shared a JSON workflow example using a data-explorer node to look up user information, and later confirmed the “bump topic” operation lives on the topic node. Patrickemin confirmed everything worked after updating. read more
#Self-hosting
-
Ed_S shared detailed
ps,free, andvmstatoutput in Is pitchfork using too much memory?, noting heavy swap usage after 20 days. David explained that it’s normal for one pitchfork worker to take the bulk of the load, memory grows and then settles, and hinted that Pitchfork’s “reforking” feature is being explored to improve memory sharing. read more -
Dennisjbr presented a parallel filesystem operations template to speed up recursive
chown/chmodoperations during rebuilds on upload-heavy forums. David moved the topic back to Support > Self-hosting, suggested usingfinddirectly in the upstream template, and opened a simpler PR that skipschownwhen permissions already match. read more -
In PostgreSQL 18 update for self-hosters, Chrisr explained that collation mismatch warnings during dump-and-restore are expected after the base image moved from Debian Bookworm to Trixie, and that switching to
C.UTF-8with thebuiltinprovider will prevent future glibc collation issues. Jonathan5 confirmed a successful upgrade. read more
-
Don documented the process of building a skeleton layout loader for Discourse, including automatically generated selectors, scoring logic for candidate selectors, hidden-element handling, and the hard-won lesson that a skeleton loader should not become a DOM-readiness gate. read more
-
Jahan_Gagan asked how to override
save()on the composer model in a supported way, and Awesomerobot pointed to existing transformers and events. David went further and proposed a newcomposer-minimum-post-lengthvalue transformer in this PR, giving plugin authors a clean extension point for optional topic bodies. read more
-
Soumya_Ranjan_Mishra asked how to configure Discourse AI with an internal OpenAI-compatible gateway. Falco suggested selecting
openaias the provider and configuring the URL, Moin recommended checking/logsfor more detail, and Satonotdead mentionedDISCOURSE_ALLOWED_INTERNAL_HOSTSfor internal IPs. read more -
ThisSource asked whether Discourse can create topics and replies using AI. Darkpixlz noted there is no built-in generator but suggested the topic API, while Moin linked to a previous forum experiment where someone populated a mostly dead Discourse with bots. read more
Activity by the Team Group
-
Chapoi was busy across multiple threads: he gathered feedback on AI title suggestions, discussed notification dismissal options, explained Google’s deindexing behavior, confirmed a fix for the compose dark-mode input background, responded to admin dashboard feedback, and coordinated backports for the iOS PWA reply button and Safari PWA zooming.
-
Moin clarified questions about the unified new topic-list view, helped troubleshoot the Discourse AI internal API configuration, answered group mention and notification questions, and posted feedback about repetitive weekly AI summaries.
-
David explained pitchfork memory growth, encouraged an upstream fix for slow rebuilds with large upload directories, and proposed a new composer value transformer to support optional topic bodies.
-
Martin started a WIP roadmap for making granular anonymous/logged-in group permissions stable, and followed up with fixes for the main permissions topic.
-
J.Jaffeux shared workflow examples using data-explorer, answered workflow questions, and confirmed the bump topic operation.
-
Zogstrip fixed two bugs with core PRs: invisible 17 elements inside 18 and workflow modals persisting across tabs.
-
Lindsey announced Zoom webinars in the Events plugin and answered admin dashboard AMA questions.
-
Chrisr answered PostgreSQL 18 upgrade questions, explaining collation warnings and dump-and-restore details.
-
Danielle shared news about an upcoming webinar and community office hours in the Community Retention webinar thread.
-
Awesomerobot fixed the compose box dark-mode bug, helped diagnose a permission prompt question, and offered composer API extension guidance.
Whether the community was debating pay-per-upvote economics, chasing memory-hungry pitchfork workers, or watching ChatGPT citations vanish into thin air, yesterday proved once again that there’s never a dull moment on Meta — see you in the next 24 hours!