Daily Summary (1pm UTC)

News and Events Forum summaries
908

Today on meta.discourse.org…

Key Stats

In the past 24 hours, there have been 30 new topics and 106 new posts across meta.discourse.org, drawing 103 likes. The top contributors by likes this period were:

Interesting Topics

#Announcements

  • PostgreSQL 18 upgrade for self-hosters — Chrisr announced the rollout of PostgreSQL 18 in the Discourse Docker image, with detailed instructions for single-container and data-container setups, plus warnings about disk space (the check now requires 2x the DB size in free space). Commenters hit issues ranging from pg_dump failing on single-CPU hosts (@nachocaballero, @Ivan_Rapekas) to upgrade-loop recovery paths (@chrisc); Chrisr fixed the core-count detection to use nproc --ignore=1. read more

ux

  • Where did the version information go? — Kjell and others questioned why the redesigned admin dashboard dropped version/technical info, with Ed_S feeling it’s “marketing-led” over engineering-led. Lilly observed the dashboard is now geared to “community managers,” and Mcwumbly explained the team’s intent to consolidate version details into the “Manage updates” page. read more

  • I don’t see the red line for last visit — Ed_S briefly feared the “red line” indicating unread posts had been removed, but Lilly and Canapin confirmed it still displays normally; NateDhaliwal noted a transient miss after a page refresh but it returned. read more

development

  • Clarifying the ‘posts read’ TL3 promotion logic — NateDhaliwal struggled to understand why the TL3 requirement multiplied posts by a percentage and took a minimum; Mcwumbly explained that tl3_requires_posts_read is a percentage bounded by a cap, making the math clear. read more

  • Now in Beta: Plugin to see TL3 Progress for TL2 users — EricGT raised a nuanced edge case: muted categories can inflate the “posts read” requirement. He proposed a category-by-category breakdown in the plugin to show eligible vs. read posts, which NateDhaliwal noted core itself lacks. read more

#Self-hosting

  • Any cheaper alternatives to Hetzner? — Lilly, Merefield, and Jagster dug into running Discourse on minimal hardware. Jagster shared real-world numbers from a 4-vCPU / 8GB server running a dual-container setup with 1000–1500 daily visitors and needing 4GB swap during rebuilds; Merefield suggested 3+ cores for dual-container comfort. read more

  • Configure a supported tracking branch to get Discourse software updates — Ghorbani questioned whether git pull remains necessary in the daily upgrade workflow. David confirmed it’s effectively redundant—launcher auto-detects and pulls the latest commit—though Ed_S prefers to play it safe and run it anyway. read more

#Praise

  • Dependent Plugin Settings are … AWESOME! — Merefield showcased the new dependent settings feature (settings visible only when relevant), calling it “:sparkles: fantastic” for reducing plugin config clutter and cognitive load. He shared pointers to the schema docs and examples from the Chatbot plugin’s settings.yml. read more

Support

  • Hola, me gustó el theme actual que tiene Discourse — Picho_Pelis asked about Meta’s branded theme; Canapin explained it’s not public, linking to prior discussion about the custom nature of Meta’s look. read more

  • Cannot view post preview in mobile composer? — FishHead reported that the rich text editor toggle fails on markdown like [color=red]. Chapoi said the plan is to improve the toggle and only re-instate the preview button if that proves insufficient, recommending the community Mobile Composer Preview component for now. read more

  • Unable to switch accounts—Sign In automatically logs into the previous account — FlowCaffe described getting locked out of an admin account in Chrome; Pfaffman explained the Discourse ID single-sign-in flow, suggesting a logout at id.discourse.com or impersonation via the Admin user page. read more

  • What happened to claiming reviewables? — Darkpixlz couldn’t find the “claim” button in the review queue. Lilly and Moin traced it to an admin site setting (now optional), and Darkpixlz confirmed that solved it. read more

#Feature

  • Add interface preferences to individually hide Suggested and Related topics — Akanora proposed two separate user-level toggles (hide Suggested / hide Related) to reduce clutter, explaining his choice might vary per-community; Mcwumbly asked probing follow-ups about real-world usage patterns. read more

#Plugin

  • Discourse Chatbot :robot: — Merefield published a comprehensive PR round-up for the Chatbot plugin (v2.4.1), covering new local reasoning strategies, a semantic blocked-question gate using embedding similarity, replacement of the unsafe SafeRuby evaluator with Dentaku, and adoption of Zeitwerk loading. read more

  • Discourse Workflows — Sam announced a new PR adding interaction API support to Discourse Workflows and invited testing in a trial environment; Eviepayne also left feature-gap notes (e.g., missing pagination in the HTTP request block). read more

Activity by the Team Group

  • Chrisr posted the flagship PostgreSQL 18 upgrade guide, then worked through the comments: correcting the disk-space check to 2x DB size, fixing the single-CPU pg_dump job count bug, and explaining how to postpone or recover from failed upgrades. read more

  • Mcwumbly provided the canonical explanation of the TL3 “posts read” percentage calculation and cap, and offered a thoughtful breakdown of why the admin dashboard now targets “community manager” vs. “sysadmin” hats, directing users to the “Manage updates” page for version info. read more | read more

  • Chapoi responded to UI feedback in two threads: confirming the rich-text-editor preview toggle is being improved (with a third-party component as a temporary patch) and clarifying that the Welcome Banner is intentionally hidden on small screens, including a CSS snippet to override it. read more | read more

  • David clarified that ./launcher automatically pulls the latest discourse_docker commit, making a manual git pull unnecessary in standard workflows. read more

  • Sam acknowledged Daily Summary feedback and committed to a validation rework (“may take a week or 2”), and also shepherded a new Workflows PR adding interaction API support. read more | read more

  • Tgxworld stepped in on the Spanish-language install thread to tell Picho_Pelis that a recently pushed bug had been fixed and a launcher rebuild app should resolve the postgresql.conf failure. read more

  • Pfaffman diagnosed an account-switching lockout caused by Discourse ID single sign-on, suggesting logout at id.discourse.com or admin impersonation as workarounds. read more

Between the PostgreSQL 18 migration drama, a flood of Chatbot PRs, and a detour into music theory, it seems even the most technical days on meta can still end with a tune! :musical_notes:

909

Today on meta.discourse.org…

It’s been an action-packed 24 hours on the meta. From a major self-hosting upgrade to AI API additions and even some off‑topic music talk, the community has been buzzing. Here’s the daily digest.

Key Stats

  • 178 new posts and 46 new topics were created in the last day.
  • 249 likes were given across those posts.

Top users by posts and likes:

Interesting Topics

#Announcements

The big news of the day was the PostgreSQL 18 upgrade for self‑hosters, announced by Chrisr. The upgrade is now in the Docker image and requires ~2x database size free disk space. Many users shared their experience: Richie watched the migration live with a shell command, Sandra.Mccollum hit a snag that was resolved by manual steps, and Pfaffman reported successful upgrades via his dashboard. The thread also covers workarounds for single‑CPU hosts and changing locale provider read more.

In the same category, the emphasized admin dashboard redesign is attracting feedback. Kjell misses the quick access to version info and disk space, and Lilly simply reverted to the old dashboard on her sites. Mcwumbly points to a related discussion about the missing version info read more.

Finally, Sam announced the Gemini Interactions API support in Discourse AI. The new provider adds tool call streaming, code execution, and Google Maps integration, replacing the legacy generateContent API for new setups read more.

#Praise

A short but sweet topic celebrated the new dependent plugin settings feature. Merefield demonstrated how these settings hide irrelevant configuration options in Chatbot, calling it “really chef’s kiss”. NateDhaliwal asked for docs, and Merefield linked to the official schema and specs read more.

#Feature

The username template parameter in AI personas was merged into core. Falco merged the PR, but Sam later warned about potential system prompt churn in multi‑user chains. He also noted that some hosted models currently discard the name field and that a patch is in the works read more.

Another feature request, suppress notifications for tag changes from Steradiant, quickly received a pointer from Moin to existing site settings disable_tags_edit_notifications and disable_category_edit_notifications, as well as the bulk tagging modal’s notification checkbox read more.

Support

Several users reported problems after the PG18 update. Sandra.Mccollum’s site initially went down; she fixed it by manually updating PostgreSQL and libvips inside the container, and later successfully upgraded her second site via CLI instead of the web UI read more. Ed_S suggested that the web‑based updater may only do a single rebuild, which might not be enough for a DB major version bump read more.

In another thread, Scavin asked about database cleanup before the PG18 upgrade. Ed_S clarified that the needed free space is now 2x, and Falco noted that tables like ai_api_audit_logs have retention settings, while incoming_links and topic_views are meant to be kept forever read more.

On the mobile front, FishHead cannot view post preview in the mobile composer because the rich text editor doesn’t support some Markdown extensions like color tags. Chapoi acknowledged the limitation and said the toggle might be improved, or the preview button reinstated later read more.

A more exotic support issue involved using a Unix socket between Caddy and Discourse, leading to PG::InvalidTextRepresentation errors. Willy shared his config, Falco diagnosed a proxy misconfiguration, and Willy eventually suspected a stale socket after rebuilds read more.

#Community Building

A lively discussion on the drop in community activity for support forums was sparked by HAWK’s AI agent analysis. He argued that communities with direct audience relationships are better insulated from search volatility. Nickdb and Tris20 chimed in on AI hallucinations, while Nathank shared that he uses ask.discourse.org for quick answers and only returns to meta for complex questions read more.

In the same category, HAWK also posted about scalable engagement models like webinars and office hours, asking for other one‑to‑many formats. Mcwumbly highlighted how feature announcements are usually made by the people who built them, which invites direct community feedback read more.

enterprise

The discussion on scalable engagement was cross‑posted under enterprise (same topic as above). We grouped it under #Community Building, but since it’s also tagged enterprise, we’ll mention it here: HAWK’s topic drew practical advice on turning internal knowledge into reusable community sessions read more.

#Self-Hosting

Ghorbani asked about the necessity of git pull before rebuilds in the classic switching‑between‑release‑channels guide. David explained that the launcher automatically updates itself, and Ed_S added that manually running git pull is harmless. The OP was updated to reflect modern “channel” terminology read more.

ux

The interface for adding users to groups on mobile is borderline non‑functional, as Stephtara demonstrated with screenshots. Chapoi confirmed a larger redesign is planned but provided an immediate fix in a PR read more.

Closely related, Moin raised that the version information has disappeared from the admin dashboard. While the info exists in the browser console, he argued it should be available in safe mode as well, and Lilly wondered why the update page wasn’t a sufficient replacement read more.

Mcwumbly started a topic on improving the “update Discourse” page, inviting ideas. Asa contributed a detailed breakdown of status states, a version card, and a proposal to distinguish between “up to date”, “a few commits behind”, and “security update” read more.

development

A quick tip for theme developers: Andrew_Rowe asked how to inject HTML only on one page. Awesomerobot shared a Glimmer component using the router service and defaultHomepage() to conditionally render in the outlet read more.

#Plugin

The Discourse Chatbot had a major update to v2.4.1, as summarized by Merefield: new local reasoning strategies, a semantic blocked‑question gate, and a move from SafeRuby to Dentaku for calculations. He also highlighted a security fix for SafeRuby vulnerabilities read more.

Another plugin, Resenha, got a quick fix for an error when deleting voice rooms. Satonotdead reported the 500, Falco merged a PR, and the user confirmed the fix solved it read more.

Activity by the Team Group

  • Chrisr played a central role in the PostgreSQL 18 upgrade announcement and follow‑up. He explained the disk space requirements, corrected the 3x to 2x, addressed single‑CPU host issues with nproc --ignore=1, and gave guidance on postponing the update post 1, post 6, post 30.

  • Falco merged the PR for the username template parameter in AI personas post 5, clarified retention recommendations for database tables post 3, and fixed the Resenha deletion bug post 80. He also commented on the Caddy/Unix socket issue post 3.

  • Sam announced the Gemini Interactions API post 1 and contributed to the discussion on the username parameter, warning about potential system‑prompt thrashing post 8. He also acknowledged plans to improve the daily summary feature post 298.

  • Mcwumbly shared insights on scalable engagement models post 2, provided a link to the version info discussion post 47, started a topic on improving the update page post 1, and clarified the intent behind an update history view post 3. He also moved a discussion to a better category post 5.

  • David answered questions in the release channel switching guide, explaining that the launcher auto‑updates itself and that manual git pull is rarely needed post 39, post 45.

  • Zogstrip helped with two bug reports: he asked for additional context in the deletion of categories failure post 2 and acknowledged a fix for the grace period edits media review bypass post 3. He also noted that deeper changes to the review system would require more planning post 5.

  • Tgxworld provided a quick “please rebuild again” response to the installation failure topic after a recent bug was fixed post 3.

  • Awesomerobot shared a GLimmer component for conditional HTML injection post 2, gave advice on password resets with unknown emails post 2, and fixed the invite restricted issue with a combined PR post 3.

  • Martin responded to concerns about the new unified topic list view, explaining how unread counts are still available and offering to discuss a user preference for showing replies only post 39.

  • Chapoi was busy on mobile UX: he acknowledged the group‑adding interface problem and pointed to a PR post 3, commented on the missing preview in the composer post 19, reported a fix for the overflow in the activity‑by‑category section post 3, and explained the welcome banner behavior on mobile post 4.

Yesterday we saw everything from upgrading PostgreSQL to jamming on jazz piano — proving that this community can talk tech and tune‑ups in the same breath, with rhythm and harmony to spare! :musical_note: