Daily Summary (1pm UTC)

Today on meta.discourse.org

Key Stats

Interesting Topics

Bug

Support

  • A clarification in Support merefield and sam confirmed that Groq is a hardware inference provider, not a typo for “Grok” in the Discourse AI docs; sam emphasized that the naming is deliberate read more.

  • Many admins are exploring the new “More robust site search” features, but Lilly pointed out you must include filters like bot:true or whisper:true in your query syntax; docs will be updated soon read more.

  • toon251 ran into a “Page not found” when using /bookmarks?order=created; Lilly guided them to the correct /my/activity/bookmarks endpoint and advanced filter pattern read more.

  • New users asked why the “Reply” button doesn’t appear in some restricted categories; sam identified and resolved a misconfigured category permission to re-enable replies read more.

  • In an AI-focused support thread, awesomerobot explained that you can technically run Topic List Excerpts and AI gists simultaneously but recommended choosing one for clarity read more.

  • jordan-violet explored automating banner creation with AI summaries; the community discussed draft category workflows and LLM integration scenarios read more.

  • Joe_F sketched out a “roadmap style” category like Matillion’s roadmap and merefield pointed to the Kanban Board plugin and workflow extensions as a solid foundation read more.

  • fzngagan invited everyone to test the new rich text composer in Support, sharing an early draft build for feedback read more.

Installation

  • A newcomer, Vixi, struggled with the official Docker behind Nginx proxy; Lilly walked through the cloud install guide, launcher commands, SMTP settings, and admin account setup read more.

Feature

  • In Feature, icaria36 proposed real ActivityPub–style hashtags instead of Discourse’s internal tag syntax, sparking a deep discussion on federated tag semantics read more.

Dev

  • noahl asked whether API-driven group membership flows belong in a plugin or theme component; merefield pointed to the Verifiable Credentials plugin and private user fields as starting points read more.

Activity by the @team Group

That’s a wrap—after all those grok vs. groq debates and AI gist purges, even our servers deserve a coffee break!