Today on meta.discourse.org…
Key Stats
- New posts (last 24h): 75
- New topics (last 24h): 9 (including Emoji picker search now works in your language, Random thought, and Videos and Monetizing my Discourse community)
Top users (posts / likes in the last 24h)
| User | Posts | Likes |
|---|---|---|
| Falco | 6 | 22 |
| Canapin | 4 | 20 |
| Lilly | 5 | 12 |
| lindsey | 1 | 10 |
| piffy | 1 | 10 |
| merefield | 4 | 10 |
| eisammy | 7 | 9 |
| fuse | 3 | 7 |
| kirupa | 3 | 5 |
| mcwumbly | 7 | 5 |
Interesting Topics
#Announcements
-
Discourse shipped localized emoji search: the composer’s emoji picker now matches keywords in 48 languages, addressing a long-standing multilingual need in Emoji picker search now works in your language (localization). Related history: Add English and translated aliases for emojis and the older support question now effectively answered by today’s announcement: How to support other language in emoji search? (read more)
-
Default email subject lines are getting simpler/less technical, removing redundancy like
[%{email_prefix}]for “sent from the community” messages, in Simpler email subject lines (email). The discussion also surfaced cases where people still rely on subject “context,” like category indicators and subcategory display needs (see Subcategory display options in email templates).
#Site-Feedback
-
A “where do I post this?” thread turned into a mini showcase of community experiments, with a proposed norm: share work in General tagged show-and-tell—starting from Show and tell: where to share things interesting things you’re doing with Discourse (show-and-tell). It also included examples like embedding-driven topic clustering (see read more), plus follow-up encouragement to spin off dedicated topics when deeper feedback is wanted (read more).
-
Tagging/naming hygiene popped up too: whether an announcement should carry a localization tag was raised in the ongoing gardening experiment, Experiment: Collaborative content gardening hub for meta (a neat “meta about meta” moment that ties directly back to Emoji picker search now works in your language).
General
-
A thoughtful request: should contributors be notified when a topic disappears (deleted, made private, or otherwise removed), so they don’t lose track of time invested? That idea—and the context of a category accidentally being public—came up in Random thought (read more).
-
A community member shared a big “here’s what I customized and why” roundup—covering practical, real-world UX and funding mechanics—via Modifications/features I made on my forums (and why) (show-and-tell). It was explicitly inspired by the earlier “where should I post this?” discussion in Show and tell: where to share things interesting things you’re doing with Discourse.
-
A provocative “show-and-tell” raised eyebrows: using AI bots to repopulate a mostly-dead forum, plus discussion about disclosure and what “community” means when content isn’t organic, in I populated my (mostly-dead) Discourse forum with bots! (show-and-tell). The replies dug into transparency expectations and the “Dead Internet” concern (read more).
-
Positive feedback landed for official ecosystem docs UX: the release-notes hub got kudos for readability improvements in Releases.discourse.org feedback & suggestions (read more).
-
A community-driven “newsletter about Meta” concept continued to be debated—especially around incentives and avoiding popularity contests—in MNN Meta Monthly News (read more).
Support
-
A gamification/leaderboard edge case: can someone appear on a “top contributors” leaderboard without visible topics/posts in their activity? The thread explored private-category activity and alternate scoring vectors in Can a leaderboard top contributor have no topic or posts in their activity?, with a pointer to external point-awarding integrations in How to integrate Discourse Gamification with an external system (redeem and award points) (read more).
-
Discourse AI translations behavior under model churn: if you change the LLM provider/model, do translations restart? The answer: old translations are kept, and the new model only fills gaps, in What happens to translations when LLM changes? (ai) (read more).
-
A practical monetization question: selling access to instructional videos inside a Discourse community. The thread quickly turned to architecture tradeoffs (hosting vs. embedding, storage headaches, and “members-only” options) in Videos and Monetizing my Discourse community (read more).
-
SEO + localization nuance: translated pages using
?tl=won’t rank independently because of canonical behavior, confirmed in Translated pages cannot rank in Google. Killed by CANONICAL. Content Localization + ?tl= (seo, content-localization) (read more).
ux
- Admin workflow papercut: changing a member’s email can produce an “Access Denied” when clicking the verification link while still logged in as admin—leading to talk about impersonation and “admin should be able to change anything” expectations in Admin changing email address of a member is still quirky!. A related “fast path” workaround was referenced via console tooling: Change staff email address from console (read more).
#Feature
-
Long-topic navigation UX resurfaced: a request for bookmark-like “reply later” markers (and jumping between “my reactions”) was added to the classic thread Natural breakpoints or “chapters” for long topics? (read more).
-
A compassionate moderation/UX proposal about “undo send” / delayed posting—framed around episodic unwellness—continued in For users with episodic unwellness: Post Approval by “future self” or “trusted friends”?, and it cross-linked to another “oops” moment: The awkward mishap of premature posting (read more).
#Plugin / #Theme / #Developer-Guides (grab-bag updates)
-
A plugin regression report: a Discourse update seemingly disabled category settings for a plugin’s buttons, in Trading Buttons (read more).
-
A theme perception issue: someone questioned whether a default pattern element resembles a swastika, and the thread touched on “what users notice first” vs. intent in Graceful Theme (read more).
-
A developer-doc nudge: someone suggested folding new guidance into the canonical first post of the long-running guide Install Discourse on macOS for development (dev-install, how-to) (read more).
Activity by the @team Group
-
lindsey published a product-facing walkthrough of the new defaults (and rationale) for tidier notifications in Simpler email subject lines, aiming to make Discourse emails feel less “technical” in members’ inboxes.
-
Falco shipped and announced multilingual emoji search in Emoji picker search now works in your language, and also confirmed translation behavior when LLM settings change in What happens to translations when LLM changes?. Additionally, Falco jumped into the embed comments case to point to fixes/work being tracked for GTM/script injection and analytics segmentation in Tecnoblog’s Experience With Discourse Comments and read more.
-
mcwumbly steered the emerging show-and-tell norm—encouraging dedicated follow-up topics for deeper feedback—inside Show and tell: where to share things interesting things you’re doing with Discourse (read more). mcwumbly also acknowledged the “vanishing topic” confusion and indicated the underlying access mix-up would be untangled in Random thought, and offered a practical long-topic reading/replying technique (quote-to-composer as a stash) in Natural breakpoints or “chapters” for long topics?.
-
nat confirmed the SEO implication of canonical URLs for localized content in Translated pages cannot rank in Google. Killed by CANONICAL. Content Localization + ?tl=.
That’s a wrap—may your email subjects be simpler, your emoji searches multilingual, and your “show-and-tell” ideas just organic enough to avoid summoning the Dead Internet discourse again.