Resumo Diário (21h UTC)

Notícias e Eventos Resumos do fórum
938

Today on meta.discourse.org…

Key Stats

Over the past 24 hours, the community produced:

  • 270 new posts across 65 new topics, generating 479 likes.

:trophy: Top Contributors

User Likes Received Posts Written
Damian_Boon 34 19
Moin 30 9
JammyDodger 27 8
Chapoi 26 14
Ed_S 26 14
Sam 23 5
Alltiagocom 22 15
Lilly 22 12
Andrew_Rowe 22 6
EricGT 19 5

Interesting Topics

#Community Building

Anyone else seeing a drastic drop in community activity for Support forums?
Damian_Boon kicked off a deep, multi‑voice conversation about how AI and Google’s changing search landscape are reducing organic traffic to forums. Canapin shared notes on AI reliability, Ed_S contributed traffic‑source data, and Tris20 offered a hopeful vision for a future golden age of human‑heavy communities. read more

enterprise

Access and engagement strategies
HAWK explored why internal teams feel unqualified to engage on Meta. Canapin reflected on the “hidden costs” of staff participation, Andrew_Rowe suggested pragmatic reply strategies, and Mae stepped in to clarify that marketing roles have a place – just not for deep technical questions. read more

#Announcements

July 2026 monthly release
Loic announced v2026.7.0 and its ESR status. The release sparked immediate discussion about ESR labeling, pinning, and the desire for a “grace period” before automatic rollover. Ed_S shared a helpful write‑up of what to expect when moving from 2026.1. read more

Composer preview toggle now lives with the other window controls
Chapoi announced the reorganisation of composer top‑right controls – the preview toggle joins the minimise and fullscreen buttons, and the minimise icon switches to a standard dash. read more

New default for pending user approval reminders
Zogstrip introduced an upcoming change that lowers the default reminder delay for approving new members from 8 hours to 30 minutes – only applicable to sites that require staff approval. read more

Introducing a docked composer for AI bot conversations
Keegan merged an update that moves the send‑shortcut setting to core, making it available for AI bot conversations. The docked composer now respects user preferences for send behaviour. read more

Support

How far can we push Discourse in customization?
Alltiagocom asked about the limits of customisation without breaking on upgrades. Awesomerobot gave practical guidance on using CSS variables vs. bare selectors, Merefield noted that staging servers are essential for heavy customisation, and Andrew_Rowe encouraged starting small with themes and components. read more

Jumping from 2026.1 ESR to 2026.7 – What I found
Haydenjames published a thorough, researched guide covering security advisories, the version: stable pitfall, and a checklist of behaviour changes – including a note that YouTube embedding still breaks due to the Referrer-Policy header. read more

Cannot view post preview in mobile composer?
Seanblue and others lamented the loss of the preview button. Awesomerobot demonstrated minor WYSIWYG‑to‑markdown formatting shifts, and Moin promptly released a theme component to restore the feature. read more

ux

Site in staff only mode – no need to show signup or login
EricGT reported that the OpenAI forum, in staff‑only mode, still displays sign‑up and login prompts – frustrating for read‑only visitors. Zogstrip fixed the issue within 12 hours via PR #42101, now live on the OpenAI site. read more

development

Now in Beta: Plugin to see TL3 Progress for TL2 users
NateDhaliwal continued refining the plugin – addressing progress‑bar alignment, adding a modal_bottom_text setting for site‑specific TL3 benefits, and working on a “closest stat” indicator. read more

Any way to change at what width the small logo appears?
Sb56637 struggled with the full‑width component forcing the primary logo in scrolled‑down topic view. Awesomerobot solved it by adding a “use default logo behavior” setting to the Full Width component. read more

#Extras

Improving accuracy of AI reporting through validation
Sam introduced a new “Fact Checker” agent in Discourse Workflows that reviews draft AI reports for mistakes before posting, dramatically improving quality without requiring a model upgrade. read more

Giving Discourse AI agent skills
Sam detailed how to approximate an agent‑skills system using custom tools that read from a dedicated category – each skill a topic with frontmatter, discoverable by the agent. read more

bug

Issue with iOS 16.7 photo upload?
David and Falco investigated upload failures on older iOS devices. Falco’s fix was included in v2026.7.0, but some users report it didn’t resolve the issue – possibly linked to tight upload image size limits. read more

Permanently Delete does not show (even after 5 minutes)
Tkforbes discovered that the “Permanently Delete” option is missing from the topic‑level wrench menu, and the bulk‑delete modal misleadingly claims deletion is permanent when it is not for moderators. Lilly guided troubleshooting. read more

#Self‑hosting

Updated to esr, but “578 new changes are available”
Ed_S noted a confusing dashboard message after upgrading to the new ESR. David fixed a server‑side version‑check bug; the false alert will clear after a forced version check. read more

Activity by the Team Group

That’s all for today – between AI agents gaining skills and forums feeling the heat from Google’s overviews, yesterday’s conversations proved that even a quiet forum can still spark a blazing debate :fire:.

939

Today on meta.discourse.org…

Key Stats

In the last 24 hours, the community generated 250 posts across 66 topics, with 345 likes distributed across the discussions. The most active and liked users were:

User Likes Posts
Moin 38 17
Alltiagocom 25 15
Merefield 19 13
Awesomerobot 18 10
Damian_Boon 17 17
Ed_S 16 11
Nickdb 14 6
Sam 14 3
JammyDodger 12 3
David 11 8

Interesting Topics

#Community Building

  • A deep and passionate debate unfolded in “Anyone else seeing a drastic drop in community activity for Support forums?” – Ed_S challenged the “AI is inevitable” stance, leading to a reflective discussion on how forums must offer more than Q&A to survive. Damian_Boon, Nickdb, and Alltiagocom weighed in on the value of human connection vs. AI convenience. Read more

  • “Forums that forbid AI content… How’s it going?” – Nickdb shared a detailed AI-detection prompt used to flag AI-generated posts, and Merefield agreed that overly structured AI slop kills engagement. Takiro added perspective from an art community that bans AI content. Read more

#Theme component

  • “Mobile Composer Preview” – Moin released a theme component restoring the mobile preview button, which was removed from core. Users Lilly, Jagster, and others celebrated its return. Sk-Or-V1-Contents reported a minor display bug that was resolved. Read more

  • “Topic List Previews (TLP)” – Ed_S reported an error on ESR 2026.7, which Merefield quickly patched. The fix addressed a TypeError in preview-edits.gjs. Later, Merefield previewed a “Horizon-lite” fork that works with TLP and Bars. Read more

  • “Colored Tag Styles” – Manuel refactored this component to allow fully customisable color styles via theme settings instead of eight fixed colours. Read more

  • “Closed Sidebar by Default” – Don contributed a smarter JavaScript snippet that initialises the sidebar closed but then remembers user preference, and Nathank rolled it into the component. Read more

Support

  • “How far can we push Discourse in customization?” – Alltiagocom asked about limits. Awesomerobot advised using CSS variables for stability; Merefield noted that customisation always requires maintenance. Andrew_Rowe suggested hiring a professional developer. Read more

  • “Jumping from 2026.1 ESR to 2026.7 – What I found” – Haydenjames documented 17 security fixes and a YouTube embed workaround. Mcwumbly emphasised that patch-first is still valid for two months. Merefield recommended a staging server. Read more

  • “Failed to optimize image” error from discourse-topic-previews-sidecar – Takiro encountered an avatar upload failure. David identified the backtrace pointing to an archived plugin and advised removing it. Read more

  • “Issue with iOS 16.7 photo upload?” – Sb56637, Sok777, and Falco investigated uploads stuck at 0% on iOS. The fix for iOS 16.7 was landed, but users on iOS 26 also faced issues, possibly due to server-side settings. Read more

development

  • “Any way to change at what width the small logo appears?” – Sb56637 asked about the full-width component overriding logo behaviour. Awesomerobot added a new setting (“use default logo behaviour”) to the component, and Sb56637 confirmed it works on ESR. Read more

  • “Facebook-style Topic Modal – Is it better?” – Damian_Boon shared a demo of a modal-based topic view, getting feedback on load speed and mobile behaviour. He continued iterating on the concept. Read more

#Announcements

  • “July 2026 monthly release” – Discussion around ESR rollover: Ed_S wanted to stay on the previous ESR longer, Mcwumbly questioned the difference, Elmuerte suggested a “grace period” label, and Moin clarified that ESR only gets security fixes. Read more

  • “Introducing the unified new view for the topic list” – Overgrow reported that suggested topics no longer prioritise unread tracked topics. Martin acknowledged it was unintentional and plans a fix. Seanblue flagged count sync issues. Read more

#Extras

  • “Improving accuracy of AI reporting through validation” – Sam detailed a new Workflows-based pipeline that chains a report runner with a fact-checker agent, using Dreamlike and Luna models. The post includes technical screenshots and JavaScript code. Read more

ux

  • “Image makes post events Onebox too big / dominant” – Nathank noted that event images in Oneboxes can overpower a post and shared a CSS workaround. The suggestion was to omit images from Oneboxes or provide a mini version. Read more

bug

#Event

  • “Bringing Community Conversations Into Your Website – Office Hours Replay” – Danielle posted the replay of a session covering the new full-page embedded discussion experience, with key takeaways on setup and SSO. Read more

Activity by the Team Group

  • Sam authored the “Improving accuracy of AI reporting through validation” topic, describing the new Workflows pipeline. He also helped Dennisjbr with a Gemini model issue in the Workflows thread. Read more and Workflows thread

  • David resolved the “failed to optimize image” error by identifying the deprecated plugin and advised on avatar upload issues. Read more. He also explained the “578 changes” version-check bug in v2026.7.0 ESR misreport and helped debug iOS photo uploads. Read more

  • Awesomerobot added a setting to the full-width component to restore default logo behaviour. Read more. He also clarified a WYSIWYG markdown rounding issue in the mobile preview topic, read more, and fixed the mobile chat search scroll bug. Read more. He also responded to the ActivityPub domain change topic. Read more

  • Falco helped diagnose iOS upload issues and identified the root cause in a security fix. Read more. He also addressed the Turkish translation problem, promising a prompt fix. Read more. He merged a PR for Resenha voice rooms. Read more

  • Zogstrip confirmed adding an input option for Boolean fields in Call Workflow steps. Read more. He also fixed a duplicate poll title in email notifications. Read more

  • Chapoi linked to the mobile preview component in the “Cannot view post preview in mobile composer” topic. Read more. He also asked for more info in a non-streaming request thread. Read more

  • Mcwumbly discussed ESR rollover and suggested a grace period label. Read more. He clarified that patch-first remains a legitimate option for ESR. Read more. He also responded in the Chat API topic. Read more

  • Merefield fixed the Topic List Previews error. Read more. He encouraged using staging servers for upgrades. Read more. He also participated in the customization limits discussion. Read more

  • Nat removed empty manual overrides that caused an empty banner box. Read more. She also pushed a PR for multi-language preferences. Read more

  • Danielle published the Office Hours replay on embedded discussions. Read more

  • Lindsey reminded users that the “me too” button in Solved is a category-specific setting. Read more

  • Angus pushed fixes and updates to the Custom Wizard plugin. Read more

  • Martin acknowledged the unread priority regression in suggested topics and plans a fix. Read more

  • Don contributed JavaScript to improve the “Closed Sidebar by Default” component. Read more

Between AI translation quandaries and the eternal question of community vs. LLM, yesterday proved that the human keyboard is still mightier than the chatbot — even if it takes two taps longer to preview a post.

940

Today on meta.discourse.org…

Welcome to your daily digest of the vibrant activity happening in the Discourse community over the last 24 hours. From deep dives into AI moderation to new plugin updates, there’s plenty to catch up on. Let’s dive into the numbers and conversations that shaped the day.

Key Stats

  • Total new posts: 172
  • Total new topics: 56
  • Total likes given: 212

Top contributors (by posts and likes received):

User Posts Likes
Zogstrip 7 20
Moin 19 17
Falco 6 17
Merefield 6 14
Nathank 8 11
Takiro 5 11
Alltiagocom 5 9
Nickdb 5 9
HAWK 1 8
Awesomerobot 3 7

Interesting Topics

#Community Building

  • Forums that forbid AI content… How’s it going?
    Nickdb shared how their forum uses a custom AI agent to flag AI-generated posts from new members, with a detailed prompt example that checks for “overly polished” language. Merefield agreed, noting that AI-style posts feel like “walking through treacle”, while Takiro explained their art community’s strict AI ban and how they moderate reports without witch hunts. The conversation also touched on the overuse of em dashes as a “telltale” sign — with HAWK joking that he refuses to lower his own standards just to appear human. Read more

  • Anyone else seeing a drastic drop in community activity for Support forums?
    A lively discussion evolved into a philosophical debate about AI’s role in communities. Alltiagocom argued that LLMs will “unclog your toilet” by telling you how, while Nickdb countered that they provide “generic, lowest common-denominator advice”. Tris20 shared his fatigue with AI-generated content, longing for “messy human text”. Read more

#Plugin

  • Resenha - Add Discord-style Voice Rooms to Your Community
    Falco merged fixes for reported UI issues (private room icon size and participant list accessibility) and announced several new capabilities: coturn auth for STUN/TURN, LiveKit session recording, flagging of call participants, right-click menus on video tiles, and opt-in higher bitrate streaming. Nathank provided detailed feedback that led to those fixes. Read more

#Feature

  • Allow use of input for value of manually mapped Call workflow Boolean type fields
    A feature request by Per1234 was quickly picked up by Zogstrip, who implemented it via a PR. Renato independently created another PR, and the team coordinated to merge both. The thread shows how responsive core development can be when the community provides clear use cases. Read more

Support

  • Failed to optimize image error from discourse-topic-previews-sidecar
    Takiro reported avatar upload failures and traced them to a type mismatch in the deprecated topic-previews-sidecar plugin. David identified the archived plugin and recommended removal. After disabling it, Takiro confirmed everything worked again. A perfect example of community support solving a real-world issue. Read more

  • Maintenance page workaround - can this be done?
    Alltiagocom proposed a Cloudflare Worker + KV solution (from Claude) to show a maintenance page without touching nginx. Canapin questioned the need, while Merefield suggested moving to a two-container setup so rebuilds take seconds. The thread offers practical alternatives for downtime management. Read more

  • Mostrar “Proximos Eventos” en todas las Categorias
    A Spanish-language question about showing upcoming events in all categories. Moin provided a concise solution using a value transformer (discourse-calendar-upcoming-events-show-cross-category) inside a theme component. The original poster confirmed it worked, and Nathank later suggested making it a built-in parameter. Read more

#Announcements

  • Introducing the unified new view for the topic list
    Martin fixed an issue where suggested topics lost priority in unread results, and Seanblue reported persistent unread count sync problems. Chapoi explained that hiding the “new/unread” line in Horizon was intentional for decluttering, but Martin will adjust the logic to keep unread priority. Read more

  • Solved improvements: Allowing members to indicate they’re experiencing a reported issue
    The community gave feedback on the “me too” button. Lillian and RGJ expressed concerns that it might discourage detailed replies, but Lindsey reminded everyone that it’s now a category-specific setting that can be turned off. The discussion highlights the need for flexible moderation tools. Read more

#Theme component

  • Mobile Composer Preview
    Moin restored a preview button for the mobile composer and helped Sk-Or-V1-Contents debug a missing button in theme creator. The thread also covers the difference between RTE and Markdown modes, with Jagster noting that even RTE users have switched to preview mode because it suppresses the keyboard. Read more

events

  • Bringing Community Conversations Into Your Website - Office Hours Replay
    Danielle shared the replay of the office hours session on the new full-page embedded discussion experience. Key takeaways include automatic companion topic creation, routing to specific categories, and styling options. This is a major step for integrating Discourse into any website. Read more

bug

  • Chat search results cannot be scrolled on mobile (touch swipe unresponsive)
    Tonja’s thorough bug report was acknowledged by Awesomerobot, who added a fix in PR #42188. The issue prevented scrolling in chat search results on both iOS and Android, making it impossible to see all results. The quick fix will be included in the next release. Read more

  • Opening forum goes to topics 1 day ago or older, not recent topics
    Zogstrip traced the problem to bfcache-compatible headers and prepared a fix in PR #42207. Users like NateDhaliwal expressed relief after months of the issue. This shows how persistent users and core devs work together to squash tricky bugs. Read more

enterprise

  • Access and engagement strategies
    The discussion expanded on how companies can integrate staff into their community. JammyDodger suggested sandbox categories for onboarding, while Satonotdead shared a cultural perspective on change and the importance of trust. Practical advice for enterprise community managers. Read more

ux

  • Remove the pure white on text
    Alltiagocom requested a softer text color for dark mode, suggesting a CSS variable from the sidebar. Satonotdead shared their own workarounds with brightness filters. The thread highlights ongoing UX improvements for accessibility and comfort. Read more

Activity by the Team Group

And so, as the sun sets on another day of dialogue, remember: if you ever find yourself reaching for an em dash, be aware that somewhere out there, a bot is judging you — but that’s only because it wishes it could convey such dramatic pauses itself. :wink:

941

Today on meta.discourse.org…

Key Stats

In the last 24 hours, the community saw 166 new posts across 49 new topics, generating 180 likes. The most active members were:

From hosting discussions to UX refinements, it was a day of practical problem-solving and community collaboration.

Interesting Topics

#Self-hosting

  • Alltiagocom opened a detailed discussion on implementing a maintenance page, exploring a Cloudflare Worker solution suggested by Claude. Lilly provided a comprehensive, step-by-step guide using Workers to intercept 502 errors during container swaps, while Merefield argued the dual-container approach makes a maintenance page unnecessary. The thread became a rich debate on balancing user experience, server cost, and implementation complexity. read more

  • In Any cheaper alternatives to Hetzner?, Alltiagocom lamented the rising cost of Hetzner VPS. Canapin pointed out the cheaper CAX line, and Lilly shared a bash script that automatically posts a Discourse topic when budget 8GB instances become available. Tealk and David_Ghost weighed in with alternatives like Netcup and Advinservers, sparking a wide-ranging conversation about the true cost of self-hosting. read more

ux

#Plugin

  • Falco showcased significant updates to the Resenha voice rooms plugin: support for private STUN/TURN via coturn auth, session recording with LiveKit, flagging participants, right-click menus, and opt-in higher bitrate. Satonotdead asked about linking to specific rooms, and Falco confirmed direct URLs are now possible. Nathank reported and received fixes for two issues. read more

  • Lou introduced the Event Duplicator plugin, which automates duplicating calendar events into new time periods. Nathank requested monthly duplication support, and within hours Lou shipped v1.1.0 with a configurable “shift (months)” field. The plugin is a practical solution for recurring events. read more

#Community Building

#Feature

#Announcements

bug

Support

Activity by the Team Group

That’s a wrap on a day full of server hunts, CSS tweaks, and a fair share of gossip about AI—who knew the self‑hosting crowd could make VPS pricing so entertaining?

1 curtida
942

Today on meta.discourse.org…

It’s been a busy 24 hours on our favourite forum—packed with server pricing debates, dashboard redesigns, and a few delightful rabbit holes.

Key Stats

  • Total new posts: 135
  • Total new topics: 37
  • Total likes given: 117

Top contributors by likes and posts:

User Posts Likes received
Lilly 11 20
Canapin 6 13
Mcwumbly 7 12
Moin 11 11
Merefield 8 11
Alltiagocom 20 5
Jagster 7 5
Kjell 1 5
Ed_S 4 4
Satonotdead 3 4

Interesting Topics

#Self-hosting

ux

development

Support

bug

#Plugin

#Announcements

#Feature

Activity by the Team Group

Team members were busy across the forum:

From watching Hetzner’s stock like a hawk to building Cloudflare worker traffic cones, we wrangled servers, redesigned dashboards, and made the internet a little more maintainable – one (docker) container at a time! :spouting_whale::sparkles:

943

Today on meta.discourse.org…

The big story: The release of PostgreSQL 18 for self-hosted Discourse dominated the day, sparking a flurry of support queries, bug reports, and upgrade war stories. Meanwhile, the Team group kept the wheels turning, merging PRs and fixing bugs at a rapid pace.

Key Stats

  • 161 new posts and 38 new topics were created in the last 24 hours, receiving 218 likes in total.
  • Top contributors by likes received:
  • The most-liked single post was Merefield's enthusiastic review of Dependent Plugin Settings (10 likes), while Chrisr's PG18 announcement drew massive engagement across multiple threads.

Interesting Topics

#Announcements

Support

ux

  • The redesigned admin dashboard has sparked a philosophical debate about who the software is for. Canapin and Ed_S expressed frustration about the missing version info in Where did the version information go?. Mcwumbly provided a calming and thorough rationale about separating “community manager” and “sysadmin” hats, pointing everyone to the updated Manage Updates page as the new home for that data. read more

#Praise

  • Merefield declared “Dependent Plugin Settings are AWESOME!” in a delightful thread showcasing how the Chatbot plugin now only reveals relevant settings based on selections. He linked to the schema documentation in site_settings.yml and explained the dependency resolution behavior, making a strong case for this being a major UX win for plugin developers. read more

development

  • NateDhaliwal needed help deciphering the TL3 promotion logic for the “posts read” requirement. Mcwumbly broke it down beautifully: tl3_requires_posts_read is a percentage, capped by tl3_requires_posts_read_cap, so the requirement is calculated as a proportion of total posts, subject to a hard upper bound. read more

  • Andrew_Rowe wanted to know how to inject HTML on just one page via a theme’s JS tab. Awesomerobot delivered a clean Glimmer component solution using the router service and defaultHomepage utility, complete with ready-to-paste code. read more

#Feature

#Plugin

  • Merefield posted an extensive Chatbot PR summary covering the jump to version 2.4.1. Highlights include advanced local reasoning strategies (verify-and-revise, best-of-two), a semantic blocked-question gate using embeddings, and a significant security upgrade replacing SafeRuby with the constrained Dentaku expression evaluator. read more

  • Satonotdead hit a Resenha voice room error when trying to delete rooms, getting a foreign key violation from the sessions table. Falco acknowledged the bug and quickly merged a fix, keeping the Halloween spirit of rapid community support alive. read more

#Self-hosting

#Site feedback

enterprise

  • HAWK sparked a fascinating thread on scalable engagement models, highlighting Danielle's office hours as a perfect bridge between direct and async communication. The thread invites others to share their own one-to-many engagement strategies that scale well beyond the initial time investment. read more

Activity by the Team Group

The Team group had a heavy-hitting day, steering the ship through the PostgreSQL 18 release and a slew of feature merges.

As the dust settles on the PostgreSQL 18 migration, let’s hope the only “single-core + 1” problem left is your coffee maker on a Monday morning. :hot_beverage:

944

Today on meta.discourse.org…

Key Stats

Over the last 24 hours, the community has been incredibly active with 235 new posts across 63 new topics, accumulating 343 likes. The top contributors by likes and posts were:

Interesting Topics

#Announcements

#Praise

Community Building

  • Drastic drop in community activity: HAWK opened a discussion about declining support‑forum activity, attributing it to volatile search traffic and AI‑based search fatigue. Nickdb and Tris20 shared experiences with AI misinformation, while Nathank suggested that AI assistants like ask.discourse.org might actually increase the quality of human interactions. The thread explores the future of communities as curated knowledge bases.

  • What’s the story behind your community?: Danielle posted an invitation for members to share the inspiration and goals behind their communities, encouraging a mix of personal and practical details. Jagster and HAWK both responded with their own community origins.

  • Learning music (off‑topic but interesting): What started as a side conversation about music notation evolved into a rich discussion about music theory, ear training, and the joy of playing. HAWK split the topic for community interest, and Merefield, Satonotdead, and Canapin contributed thoughtful insights on learning methods and the limits of notation.

enterprise

  • Scalable engagement models: HAWK started a thread on one‑to‑many engagement strategies like webinars and office hours. Mcwumbly suggested having feature developers announce their own work to foster direct community contact, and Putty shared a less‑successful experiment with bite‑sized feedback.

  • How much is AI search part of your enterprise community strategy?: Mae launched a poll to gauge how much enterprises are investing in AI search visibility. The topic links to several Discourse blog posts about LLM visibility and invites discussion on content strategies, measurement, and buy‑in.

#Self-Hosting

  • Latest update broke my discourse: Sandra.Mccollum reported a failed update to PostgreSQL 18 after upgrading via the GUI, needing two rebuilds and a manual fix for vips. Ed_S explained that the GUI only performs one rebuild, and the CLI method worked on a second server. This thread highlights the importance of CLI upgrades and backup readiness read more.

Support

  • Cannot view post preview in mobile composer?: FishHead raised the issue that the mobile composer lacks a preview button and that the rich text editor doesn’t support certain markdown like [color=]. Chapoi acknowledged the limitation and is working on improving the toggle or bringing back a preview button if needed.

  • Unix socket between Caddy and Discourse: Willy described an intermittent error where Discourse misinterprets the client IP as unix: when using a socket. Falco identified a proxy misconfiguration, and Satonotdead provided debugging advice. The thread includes detailed logs and configuration snippets read more.

ux

  • Improving the “update Discourse” page: Mcwumbly invited feedback on redesigning the update page. Asa delivered a detailed response with mockups and suggestions for distinguishing between informational and urgent states, adding version numbers, and showing update history. Ed_S stressed the importance of backup messaging and a fallback to CLI rebuilds read more.

  • Interface for adding users to groups on mobile borderline non‑functional: Stephtara illustrated the usability issues when managing group members on iOS, with names hidden behind the keyboard. Chapoi acknowledged the problem and provided a PR as a temporary fix while a larger redesign is planned.

#Feature

  • Add {username} as a template param in AI persona system prompts: Falco merged the PR for this feature, which quickly gained community appreciation. Sam later added a cautionary note about the performance implications of inserting usernames into system prompts, especially in multi‑user chains.

Activity by the Team Group

The Team group has been exceptionally active across the entire forum, driving both announcements and support.

With so many updates, fixes, and deep conversations, it seems Meta is as much a living organism as the software it supports. May your databases always have enough disk space, and your community never run out of things to say! :rocket:

945

Today on meta.discourse.org…

Key Stats

Over the last 24 hours, the community has been remarkably active with 221 new posts and 69 new topics created. The most engaged members this period were:

User Likes Posts
Moin 27 14
Merefield 24 11
HAWK 20 8
Lilly 19 13
Chapoi 17 11
Sam 16 7
Falco 12 5
Satonotdead 10 13
Roke_Julian_Lockhart 9 10
Stephtara 9 9

Interesting Topics

#Self-hosting

  • Frustrating SSL installation saga – Picho_Pelis spent a full day trying to install Discourse on multiple VPSs, hitting repeated LetsEncrypt certificate failures. The thread revealed a classic mistake: the domain debatehosting.co was never actually registered (it returned NXDOMAIN), as Supermathie pointed out in a key post. The community, including Merefield, Pfaffman, and David_Ghost, provided extensive debugging steps (checking connectivity, inspecting acme.sh.log, avoiding Cloudflare proxy) before the OP discovered the root cause and moved to a new domain. Read more

#Announcements

  • PostgreSQL 18 upgrade for self-hosters – The announcement thread became a hub for upgrade war stories. Richie shared a handy watch command to monitor disk space during the migration, while Ed_S suggested adding free -h to catch memory starvation. Jericson reported that a multisite install migrated only the default site, leaving the secondary as a fresh install – a risk of non‑standard setups. Chrisr clarified that PG18 clients are now included in the web image and explained the checksum considerations. Read more

  • Gemini Interactions API – Sam announced support for the new Interactions API in Discourse AI, replacing the legacy generateContent endpoint. The new provider includes tool‑call streaming, code execution, and Google Maps integration. A caveat was noted: Gemini 2.5 Flash models no longer allow “no thinking” mode. Read more

  • Redesigned admin dashboard discussion – Users pushed back on the new dashboard losing version info, backup/disk space visibility, and problem checks. Kjell lamented the old UI’s charm, Lilly suggested keeping both dashboards, and Mcwumbly pointed to a related thread about version info. Read more

#Community Building

  • “What’s the story behind your community?” – Danielle started a warm, open‑ended topic inviting members to share their founding stories. Jagster cited frustration with Facebook groups, HAWK framed Meta as a mission‑driven space, Canapin shared the bittersweet tale of a failed forum migration, and Newkid described his Real Estate community as the “front door” to property journeys. Read more

  • Drastic drop in support forum activity? – A lively debate on AI search cannibalizing forums. HAWK shared an AI‑generated insight about direct audience relationships, Nickdb criticized search AI unreliability, and Nathank argued that AI might filter out dumb questions, leaving higher‑quality traffic. Tris20 noted that publicly curated databases could become more valuable. Read more

Support

  • Discourse ID shows its own logo instead of the forum’s – Karthik_K1 reported that the Discourse ID login page displayed “Discourse” rather than his site name. Chapoi initially thought it wasn’t a bug, but after Moin's pushback, the team found a workaround: clearing the client credentials and toggling Discourse ID. Rishabh confirmed it’s on the roadmap to make the process clearer. Read more

  • Password reset with a forgotten email – Roke_Julian_Lockhart recounted being locked out of OpenAI’s Discourse because he didn’t recall the email alias used. The thread revealed that the hide_email_address_taken setting (enabled by default) disables username‑based resets. Southpaw showed instances where it works. This led to a follow‑up feature request. Read more

  • Meta error banner – “MERGE_BRANCH deployment failed” – Lilly spotted an alarming banner on Meta. Tgxworld acknowledged it and David explained it was an internal test‑deployment error accidentally exposed. It was fixed, and the team promised better internal error handling. Read more

ux

  • Mobile group admin interface is nearly unusable – Stephtara showed screenshots where usernames are half‑hidden when adding users to groups on iOS. Chapoi linked a PR that improves the component, and Moin connected it to an existing tag selector issue. A broader redesign is in the works. Read more

  • Improving the “Update Discourse” page – Mcwumbly asked for ideas. Asa proposed a status banner that distinguishes “behind but fine” from urgent updates, a version card, and an update history with changelog links. Ed_S stressed the need to highlight backup importance. Read more

  • “Regular mode” for admins (sudo‑like) – The long‑running feature request gained momentum. Sam suggested inverting the default: admins are normal users unless they toggle admin mode. Mcwumbly agreed and Lilly asked for an admin setting to keep permanent admin if desired. Moin drew parallels to suppress_secured_categories_from_admin. Read more

#Feature

  • Always allow username‑based password reset – Following the OpenAI incident, Roke_Julian_Lockhart filed a feature request to permit username entry even when hide_email_address_taken is on. Southpaw supported it, noting the current setting makes the username field disappear. Read more

  • Additional languages in the Language Selector – Karthik_K1 wanted Indian languages for AI‑translated content. Nat clarified that the selector changes the entire site locale, not just post content, and Hindi isn’t a supported Discourse locale yet – a plugin could register it. Falco asked for the specific list. Read more

  • Where did the version information go? – The removal of version numbers from the admin dashboard sparked this thread. Moin pointed out that /admin/update doesn’t work in safe mode because it’s part of docker_manager, so version info should be accessible elsewhere. This ties into the broader dashboard redesign discussion. Read more

Activity by the Team Group

The Discourse team has been very visible on Meta today. Here’s a snapshot of their contributions:

  • Sam – Announced the new Gemini Interactions API and discussed AI persona template parameters, warning about cache thrashing with usernames in system prompts (see this post). He also fixed a structured‑output JSON validation bug with a PR after Lilydjwg reported it.

  • Chapoi – Fixed the mobile group interface issue with PR #42304, addressed the Discourse ID logo problem with a workaround (see post 14), and responded to the “activity by category overflow” bug with PR #42305.

  • Lilly – Reported the deployment error banner, helped users with group mentions (testing expected behavior, see this post), and voiced preferences on the admin mode feature request (see post 40).

  • Moin – Provided thorough guidance on Discourse ID (see post 7), corrected assumptions about username‑based password resets (see post 14), and contributed to the dashboard discussion (where version info went).

  • Merefield – Was an early responder in the SSL installation thread, offering LetsEncrypt troubleshooting commands (see post 6) and later pinpointing the unregistered domain (see post 32). He also engaged in the password reset thread.

  • HAWK – Shared community wisdom on AI search volatility, quoting an AI agent (see post 76), and welcomed a new community story in the “What’s the story?” thread (post 3).

  • David – Fixed the deployment banner issue and explained the internal context (see post 4? and post 6).

  • Falco – Clarified how to check AI agent model usage and added a PR to improve that UI (see post 6). He also updated the Resenha plugin making slugs editable (see post).

  • Tgxworld – Acknowledged the deployment banner report and noted it was fixed (see post 2).

  • Rishabh – Confirmed the Discourse ID workaround and promised clearer UI for it (see post 20).

  • Mcwumbly – Actively participated in the “Improving the update Discourse page” and “Regular mode” discussions, sharing design perspectives (see post 41).

  • Jordan.Vidrine – Noted upcoming design modernizations for modals and select‑kits, promising a fix for the tag selector on mobile (see post 6).

  • Martin – Explained the unified new view behavior and internal discussion on preferences (see post 39).

Yesterday’s biggest mystery turned out to be a domain that didn’t exist — proof that even the most frustrating SSL errors can be just a registrar away from sanity!

946

Today on meta.discourse.org…

What a whirlwind 24 hours on Meta! The Discourse community has been buzzing with activity, from major designer test programs to deep philosophical debates about the future of the internet. Here’s your comprehensive digest:

Key Stats

The past 24 hours saw 192 new posts across 62 topics, generating 348 likes from the community. This represents a healthy mix of product feedback, support troubleshooting, and community discussions.

Top contributors by likes:

Other prolific contributors included Don (14 likes, 3 posts), Satonotdead (13 likes, 12 posts), Merefield (13 likes, 5 posts), NateDhaliwal (10 likes, 9 posts), and Mcwumbly (10 likes, 3 posts).

Interesting Topics

#Announcements

  • Chapoi announced the experimental composer redesign, which moves the toolbar to the bottom, integrates the title into the editor, and massively improves mobile composing with an expanding editor. The feedback has been passionate — Satonotdead compared adapting to the change to when “I was one of the folks who DIDN’T want a touchscreen on my cell phone” while Don noted it solves the long-standing problem where the context menu covers the editor button bar on mobile. Shauny raised concerns about muscle memory and accidental posts, but Canapin pushed back, saying the bottom toolbar “makes much more sense on mobile. Way easier to reach it” (read more).

  • The PostgreSQL 18 update continues to generate discussion. Pfaffman shared his manual multi-database migration approach, while Supermathie offered guidance on Google Cloud SQL upgrades. Lilly posted a detailed step-by-step walkthrough for dual-container setups behind Cloudflare, including disk cleanup commands, scheduled maintenance page strategies via Cloudflare workers, and the proper rebuild order. Tobias_1 shared a fix for the “cluster is owned by group id 993” error that plagues some upgrades (read more).

  • Sam revived the long-running discussion on admin “regular mode” (a sudo-like feature), suggesting that “maybe by default admins are just like any other user, except that they have a special page where they click a button to get temporary admin permissions.” Mcwumbly strongly agreed, proposing a toggle in the header with state clearly indicated. Lilly pushed back, saying she’d prefer an admin setting so she doesn’t have to “toggle into admin mode to get to /admin,” and Moin drew parallels to the existing suppress_secured_categories_from_admin setting (read more).

#Self-hosting

  • A truly epic saga unfolded in the Spanish-language topic “Ya estoy cansado, he instalado discourse en varios VPS ninguno me funcionan” (“I’m already tired, I’ve installed Discourse on several VPS and none of them work”). After extensive troubleshooting involving Jdc20181's Cloudflare insights, it turned out the domain debatehosting.co didn’t exist at all — Supermathie demonstrated this with a whois query showing “DOMAIN NOT FOUND.” Merefield noted the OP cancelled the domain during troubleshooting, which made it look like SSL issues. Satonotdead explained the real culprit: repeated attempts to get certificates hit Let’s Encrypt rate limits, which is “not the same as ‘SSL blocked my domain’” (read more).

  • In a thoughtful discussion about password reset security, Roke_Julian_Lockhart described being locked out when OpenAI disconnected their SSO integration, replacing it with an unfamiliar email alias. The thread sparked a genuinely moving exchange where Pfaffman publicly apologized: “I was a jerk and I humbly repent.” Pfaffman went on to acknowledge that “it’s not that uncommon for users in a long lasting community to no longer remember their email address” and questioned the logic of hide_email_address_taken requiring the email field, since “resetting the password with the username does not expose an email address” (read more). This led Roke_Julian_Lockhart to file a feature request for username-based password resets.

  • Picho_Pelis returned with a SMTP configuration question after the domain debacle, getting a prompt “try port 2525, port 587 is likely blocked” from Pfaffman, plus a security reminder from NateDhaliwal to censor credentials in public posts.

Support

#Feature

  • A feature request for multiple profiles per user (inspired by Discord’s PluralKit system) gained traction. A_Lilian made a compelling case: “Autonomy and expressiveness through online profiles matter. They give us the smallest window to the people past our screens and as such, are one of the primary pillars for building a humane web.” Satonotdead noted how the technical challenge lies in the fact that Discourse Chat “is built entirely into static user profiles” (read more).

#Site feedback

  • Lilly spotted an error banner on Meta reading “MERGE_BRANCH deployment failed.” Tgxworld confirmed it was fixed, then NateDhaliwal noted it persisted, and David explained the root cause: a hosting system for deploying git branches was throwing a merge conflict error that “wasn’t supposed to be displayed to everyone.” It’s now fixed for real (read more).

#Community Building

  • Mcwumbly kicked off a fascinating discussion about the next decade of the internet, reflecting on Discourse’s original 2013 promise. Awesomerobot delivered a brilliant response arguing that “I expect to be talking to people in 2036 the same way I was talking to people in 2013: typing words into boxes” and warned about AI chatbots seeking to “shortcut the web entirely,” while affirming Discourse can be “a safe harbor where you’re not subject to the massive unknowable algorithms.” Ed_S added concerns about increasing legal regulations (like the UK’s Online Safety Act) making it harder to run independent platforms, and Satonotdead outlined two possible futures — a hub format with deeper integrations, or a hardened, cypherpunk-esque decentralized platform (read more).

ux

development

  • Don unveiled a native Glimmer implementation of a Facebook-style topic modal, avoiding iframes entirely. He detailed how the modal reuses Discourse’s own Post components with a patched postStream, handles direct links and internal routing without escaping the modal, implements infinite scroll via IntersectionObserver, and even adds a skeleton loading state. Damian_Boon reacted enthusiastically: “I’d love to test your version :heart:”

#Theme component

  • Scavin released Clean Share URL, a theme component that adds a per-user preference to strip usernames from shared links (?u=username), addressing privacy concerns for users who don’t want their username attribution in shares. The component supports an optional custom user field for confirmation (read more).

bug

Activity by the Team Group

Our hardworking Team members have been extremely active across many fronts:

And in a day where Pfaffman publicly repented, Satonotdead mused on her pre-touchscreen cell phone days, and we learned that a missing domain name caused infinite Spanish-language pain… never forget: if your Discourse won’t install, make sure the domain you’re pointing at actually exists first — SSL can’t negotiate with a domain that isn’t there! :house::dashing_away:

Daily Summary Feedback
947

Today on meta.discourse.org…

Key Stats

Interesting Topics

#Announcements

  • :test_tube: Help Us Test the Composer Redesign – Chapoi unveiled an experimental composer redesign featuring a relocated toolbar, a more document-like title, and an expanding editor for mobile. The community quickly weighed in: Darkpixlz questioned the new title placement, Don loved the bottom toolbar, Canapin noted a missing rounded border on the selector, and Heliosurge couldn’t get the group-based rollout to work initially (later resolved). The topic drew 80+ likes and ongoing testing feedback from mobile users. Read more

  • :file_cabinet: PostgreSQL 18 update for self-hosters – Supermathie and Lilly shared detailed upgrade instructions for dual‑container setups, while Pfaffman clarified disk space requirements and Tobias_1 provided a fix for a group ownership error during the upgrade. The thread is a goldmine for anyone running self‑hosted installations. See the full guide

  • :key: Easier account signup using email codes – Thomas_Rother praised the new one‑time code feature, highlighting its low‑friction MFA benefits. This is part of a broader push to modernise authentication. Join the discussion

  • :robot: Introducing a docked composer for AI bot conversations – Keegan and Martin explained how to enable the new chat‑style composer for AI bots via user preferences, with Moin confirming the location under “Fonts & Appearance”. The feature is now available on ask.discourse.com. Learn more about the docked composer

  • :busts_in_silhouette: Granular group‑based permissions for anonymous and logged‑in users – Martin updated official components to use resolve_group_membership and shared a list of merged PRs. Lilly also contributed a PR to add the anonymous_users and logged_in_users CSS classes to a community component. This feature is steadily evolving. Track the changes

#Community Building

  • :globe_showing_europe_africa: For the next decade of the internet (2026 edition) – Mcwumbly kicked off a reflective thread asking what Discourse should look like by 2036. Awesomerobot delivered a memorable reply predicting “typing words into boxes” remains the norm, while Satonotdead and Ed_S discussed decentralisation and the importance of safe spaces. A thought‑provoking read. Join the conversation

development

  • :artist_palette: Facebook‑style Topic Modal – Is it better? – Don shared a theme component that opens topics in a modal, and demoed it on Theme Creator. The community loved the speed and feel, but Awesomerobot warned about rate‑limiting due to prefetching. Don responded by adding a max_prefetches_per_minute safety net. Try the modal

#Feature

  • :books: Redirect the landing page for each subcategory to index file by default for documentation categories – Mostapha requested that doc categories default to the index page rather than a topic list. He later acknowledged an existing request and wanted to close his own topic, but Merefield suggested keeping it open as a separate tracking item. See the feature request

  • :speech_balloon: More direct access to topics with new replies – Martin explained that a user preference to split “new” and “unread” isn’t planned, but he offered to add plugin APIs for theme developers. Shauny and Frederic_Bertrand pushed back, and Awesomerobot proposed alternative default settings. Lindsey moved the feedback to a separate feature topic for continued input. Share your thoughts

  • :key: Always allow username‑based password reset – Pfaffman argued that requiring an email address for password reset is a regression, especially for long‑time users who forget their sign‑up email. Awesomerobot linked the change to a GitHub PR and questioned whether the hardening rationale still holds. The discussion also covers abuse prevention and rate limiting. Vote on the feature

  • :video_game: Automating gamification points – Satonotdead is exploring using Workflows and AI to award gamification points automatically. Awesomerobot suggested adding an “award cheers” action to the Workflows plugin, and Falco pointed to a related PR. This could become a powerful engagement tool. Discuss gamification automation

Support

  • :bar_chart: Looking for storage details after Discourse update – M_Terenui praised the new admin dashboard but noted the missing backup and free space stats. Moin linked to related discussions about the old dashboard’s removals, and Awesomerobot provided a temporary workaround via the storage_stats.json endpoint. Find the solution

  • :globe_with_meridians: Setting translation to one language only – Marzena_Cudecka wanted to limit content translation to German, but the UI allowed all languages. Nat and Moin explained that interface languages are user‑controllable, and Nat noted an existing feature request for restricting languages. The team is also thinking about synergies with content localization. Explore the thread

ux

  • :bug: Discourse meta icon missing on Discourse ID login page – Canapin spotted a broken logo on the Discourse ID login page. Jordan.Vidrine investigated and found a caching issue where the logo isn’t re‑sent on changes; he implemented a fix that hides the broken image and shows the name only. Read the fix details

  • :artist_palette: The meta branded theme lacks margins on single group pages – Canapin noticed the composer‑testers group page has no margins, and Manuel confirmed it’s a likely missing body class. A quick but appreciated UX polish request. Report the margin issue

Activity by the Team Group

The Team group has been busy across many topics. Here’s a snapshot of their contributions in the last 24 hours:

And with 194 posts, 75 topics, and a slew of PRs being merged, it seems the puppies are not the only ones wagging their tails today – the composer redesign has everyone’s fingers wagging on their keyboards! :paw_prints:

948

Today on meta.discourse.org…

Key Stats

Over the past 24 hours, meta.discourse.org saw 135 new posts across 60 new topics, with 210 likes given. The community was buzzing with activity, from theme component updates to deep dives into new features like the Composer Redesign and AI bot integrations.

Top contributors this week:

Interesting Topics

development

  • Facebook-style Topic Modal — A lively thread where Don showcased his new theme component that opens topics in a slick modal instead of a full page. Multiple users praised its speed, while Awesomerobot noted network request rate limits on standard layouts. Don responded by adding settings for max_prefetches_per_minute and a “button” trigger style to tailor the component for custom themes, promising an open-source release after broader testing read more.

  • Automating gamification points — Awesomerobot suggested an “award cheers” action for the Workflows plugin, which Falco quickly implemented in this PR. Discussion also touched on using custom forms or the Custom Wizard plugin to automate rewards, though some users prefer staying within core Discourse tools read more.

#Praise

  • Contributor appreciation August (& Feb) 2026 — Moin compiled two heartfelt threads thanking all code contributors and translators over the past 6 months, including a special mention for the ES-release period. Community members voiced their gratitude, with HAWK simply replying “Thank you Moin, appreciated” read more.

#Announcements

  • Help Us Test the Composer Redesign — Testers shared feedback on mobile: Heliosurge reported settings not applying initially (later resolved), NateDhaliwal found tag buttons getting cut off with long category names, and Sk-Or-V1-Contents pushed for a preview button on mobile, linking to a related proposal. The team acknowledged the feedback and promised further refinement read more.

Support

  • Looking for storage details after Discourse update — M_Terenui praised the new admin dashboard but missed seeing backup space and free disk usage. Moin pointed to relevant topics about the redesign, and Awesomerobot provided a workaround using the /admin/reports/storage_stats.json endpoint until the data is re-added to the UI read more.

  • Setting translation to one language only — Marzena_Cudecka wanted to limit content translation to just German, but found users could pick any language. Nat explained that interface language and content language are separate, while Moin shared a feature request to restrict allowed interface languages. The team is reviewing the request read more.

  • Is there any built-in chatbot or conversational assistant? — Soumya_Ranjan_Mishra asked about chatbots beyond Discobot. RGJ mentioned the Discourse AI bot and Merefield's Chatbot plugin, while Awesomerobot highlighted that Discourse AI includes features like auto-categorize and auto-tagging, and can power a dedicated AI conversation page read more.

#Feature

  • More direct access to topics with new replies — The community debated the recent “New” vs “Unread” change. Lindsey stated there are no immediate plans to revert, but moved the discussion to a feature request category for iterative improvement. Awesomerobot explained the design rationale and asked if adding a “never” tracking option or a default for “replies” would help. Seanblue provided detailed feedback about wanting both options visible read more.

ux

  • “Vote returned” notification in case of unlimited votes — Moin reported that closing a topic sends a “vote returned” notification even when vote limits are disabled. Awesomerobot agreed it doesn’t make sense and submitted a fix in PR #42448, while noting additional nuances with the plugin’s vote limiting read more.

  • Should ‘Mee too’ be hidden on category descriptions topics? — Satonotdead asked if the “Me too” reaction should be hidden on category description topics that serve as indexes. Awesomerobot agreed and created a PR to exclude them, thanking the report read more.

#Theme component

  • Alternative User PMs Button For Admin — Heliosurge reported a JS error after updating Discourse, and Arkshine fixed it within hours. The rapid turnaround earned praise from the community read more.

  • Quote Callouts — A similar update issue surfaced for this component; @祁同伟 forked the repo to fix it, and Arkshine pushed an official fix shortly after read more.

  • Topic List Previews (TLP) — Eviepayne reported a critical bug where avatar uploads failed (no implicit conversion of Hash into String). Merefield traced it to the TLP sidecar plugin and released a fix via PR, confirming the resolution read more.

#Sysadmins

  • MKJ’s Opinionated Discourse Deployment Configuration — Raykholo asked about using Garage instead of Minio, sparking a detailed write-up of their experience with Garage under a Cloudflare tunnel. Mcdanlj confirmed the Garage works and corrected documentation on disabling transparent huge pages read more. The thread is a goldmine for self-hosters exploring S3-compatible storage read more.

#Site feedback

  • Uncategorized category? — NateDhaliwal noticed an unexpected “Uncategorized” category appeared on Meta. Moin linked it to a broader migration topic, suggesting it might be part of a test or a recent change. Discussion continues read more.

Activity by the Team Group

The Team group was highly active today, tackling bugs, responding to feedback, and shipping fixes:

  • Awesomerobot was prolific: they engaged with the Topic Modal thread on rate limits, explained the “New” functionality in More direct access, suggested an “award cheers” action for Workflows plugins, fixed the “Vote returned” notification with a PR, hid “Mee too” on category descriptions via another PR, and advised on storage stats endpoint workarounds read more.
  • Martin responded to testers in the Composer Redesign thread, confirming Meta uses a specific group setting and troubleshooting mobile issues read more.
  • Nat clarified translation settings in Setting translation to one language only and updated documentation links in the Content Localization topic read more.
  • Lindsey addressed user concerns in More direct access, explaining lack of immediate changes and moving the discussion to a feature category, and also noted they’d review the Zendesk token impact read more.
  • Falco implemented the workflow action for gamification points in a PR.
  • Davidb fixed a bug where /u/:username/activity lost scroll position after navigating back, shared in this commit read more.
  • Rishabh tested and discussed the Discourse-ID logo/name issue, noting that changes to site settings should automatically update the identity provider read more.
  • Chapoi engaged in UX feedback threads, such as asking Martin for thoughts on category permission logic read more.

From Facebook-style modals to clever bug fixes, it was a day of innovation—who knew a topic modal could spark so much excitement? Come for the feature previews, stay for the lightning-fast maintenance!

949

Today on meta.discourse.org…

Welcome to the daily wrap-up of activity on the Discourse Meta forum for the past 24 hours. It was a busy day full of plugin updates, core discussions, and helpful community contributions. Let’s jump into the stats, highlights, and team activity.

Key Stats

  • Total new posts: 64
  • Total new topics: 32
  • Total likes received: 89

Top contributors by likes and posts:

User Posts Likes
Moin 5 34
Merefield 6 11
RGJ 2 7
HAWK 2 4
Sk-Or-V1-Contents 4 3
NateDhaliwal 3 3
Eviepayne 2 3
Lilly 2 3
Weallwegot 1 3
DRRO 4 2

:clap: A special shout-out to Moin for not only posting the much‑appreciated Contributor Appreciation thread but also earning the most reactions today.

Interesting Topics

Here are some of the most engaging discussions from the past 24 hours, grouped by category.

#Praise

  • Contributor Appreciation August & February 2026 – Moin launched this heartfelt thank-you to all the contributors and translators who helped improve Discourse over the past six months. The thread (with a bonus February segment) celebrates community PRs, translations, and Meta participation. read more

#Feature

  • Add support for ‘personal notes’ on posts – DRRO continued the discussion on personal notes, exploring bookmarks, PMs, and drafts as workarounds. Awesomerobot suggested bookmarks as a natural fit, while Lilly shared a simple PM trick. Merefield then announced he is building a plugin and even got approval for a core PR. read more

  • More direct access to topics with new replies – Seanblue pushed back on the recent redesign of the “new” and “unread” filters, sharing that both communities he admins reverted the change. NateDhaliwal proposed a simple /unread sidebar link as an alternative. read more

#Announcements

  • Help Us Test the Composer Redesign – Sk-Or-V1-Contents provided feedback on mobile display, including a blue flash when expanding the editor and keyboard issues. Chapoi acknowledged several quirks and is actively iterating on the design. read more

  • PostgreSQL 18 update for self‑hosters – NateDhaliwal asked for help with a dev environment connection error, while others shared tips on upgrading. The thread is a good place to track issues and solutions for the new PostgreSQL version. read more

Support

  • Admin‑Hinweise nach letztem Update – Viddekla reported two admin notices after an update, related to the discourse-locations plugin and a legacy theme API. Moin explained how to identify and fix the plugin warnings. (This thread is in German.) read more

  • How to skip override-overrided localizations – Satonotdead asked how to stop core updates from overwriting custom Spanish translations. Several users shared workarounds and pointed to the content‑localization plugin. read more

bug

  • Bounce score does not reset when email address is changed – RGJ reported that bounce scores persist after a user updates their email to a correct address, which can wrongly flag good addresses. The expected behavior would be to reset the score on email change. read more

  • Monthly triggered recurring automation is not running as expected – Gassim followed up on a previously reported bug. Moin pointed to a merged fix (#40747) and Gassim is now testing the next month’s trigger. read more

  • FIX: Avoid traversing Redis keys when clearing 404 topic cache – Small-Lovely-Cat submitted a PR to fix a performance issue when clearing the page‑not‑found cache, which could cause 500 errors on large sites. read more

#Plugin

  • Locations Plugin – Jagster and Viddekla both noted the admin notice about deprecated code. Merefield announced that fixes have been merged, including contributions from Cvx and Angusmcleod, and the plugin now uses modern APIs. read more

  • Discourse Calendar and Events – Gassim asked detailed questions about Zoom webinar integration, permissions, and whether webhook triggers could be expanded to include event attendance actions. This is a great candidate for future core/plugin enhancements. read more

#Theme component

  • Topic List Previews (TLP) – Eviepayne reported an avatar‑upload error caused by the TLP sidecar. Merefield quickly identified a core compatibility issue and released a fix via a PR, which resolved the problem. read more

  • Clickable Social Icon Links on Profile – Weallwegot merged the long‑awaited Twitter → X change and offered to handle the next PR. Roi reported two conflicts in the PR that need resolution. read more

  • Social Share – Patrickemin suggested adding the new European network “W Social” to the official component. This could be a simple PR for anyone interested in expanding share options. read more

#Self-hosting

  • Fresh install/migrated! – ALinux shared a successful migration from phpBB and asked about performance. Darkpixlz provided feedback on loading times, and ALinux later added more CPU cores, which improved speed significantly. read more

  • Any cheaper alternatives to Hetzner? – Dopler and Satonotdead compared Hetzner pricing with OVH and other providers, discussing CPU, RAM, and network trade‑offs. read more

development

  • Facebook‑style Topic Modal – Damian_Boon asked if Don’s modal component could be open‑sourced. Don agreed to test it in production and added new settings for more flexible layouts. read more

  • Deprecating .hbs file extension in themes and plugins – Willy shared that they updated a plugin using Claude and agreed that consistency in the ecosystem is crucial. read more

#Extras

  • nodeBook: CNL knowledge graphs in posts – G_N introduced a new theme component that renders controlled natural language as interactive knowledge graphs, concept maps, and even Petri‑net simulations directly in posts. A fascinating addition for science and education. read more

Activity by the Team Group

The Discourse team was active on several fronts today, offering support, engaging with feedback, and driving forward core improvements.

That’s a wrap on a day full of gratitude, bug hunting, and creative plugin ideas — let’s hope the only bounce we see tomorrow is in the number of new topics, not email bounce scores! :tada: