Today on meta.discourse.org…
Key Stats
- New posts (last 24h): 33
- New topics (last 24h): 3 — including discussions like the composer toolbar visibility on touch devices (read more), a privacy question about proxy access (read more), and embedding Bunny Stream videos (read more).
Top users (posts + likes in the last 24h)
| User | Posts | Likes | Recent reference |
|---|---|---|---|
| awesomerobot | 2 | 4 | Composer toolbar arrow behavior on touch devices (read more) |
| Canapin | 3 | 3 | Requesting a better workflow for post edits / staff attention (read more) |
| merefield | 2 | 3 | Advice on locking down a forum being mirrored via proxy (read more) |
| Tealk | 1 | 2 | ActivityPub logs confirming repeated handle validation behavior (read more) |
| chapoi | 1 | 2 | Root-cause analysis for missing counts in a Ghost theme outlet (read more) |
| darkpixlz | 1 | 2 | Converting a post to wiki so the author can update it themselves (read more) |
| amotl | 2 | 1 | Hosted CDN attachments missing after a hiccup (read more) |
| Falco | 2 | 1 | Sentiment setup: checking the self-hosting guide + clarifying backfill (read more) |
| renato | 3 | 1 | UX suggestion: show toolbar overflow affordance based on pointer type (read more) |
| ばこん | 3 | 1 | “Someone else’s URL can access my forum” follow-up + resolution (read more) |
Interesting Topics
ux
-
The composer toolbar overflow affordance came under scrutiny: awesomerobot noted Discourse hides the scroll arrow on touch devices and wondered if that assumption should change (read more), while renato suggested switching the logic to “show if a fine pointer is available” to avoid issues on touch-enabled laptops (read more).
-
The same thread also turned into a debugging checklist: safe mode showed the missing arrow for the OP, hinting at a theme/style interaction rather than core behavior (read more) and confirming that reproduction depends on environment/device quirks (read more).
Support
-
A privacy/security concern: a user reported their forum could be accessed via “someone else’s URL” (proxy-style exposure) and asked how to prevent mirroring (read more). The accepted guidance was pragmatic: go fully private if needed and ban accounts showing obvious “visit everything” scraping behavior (read more).
-
A Ghost-theme-specific display issue: reply/view/activity counts disappeared inside a category topic list when the category had no subcategories, due to the chosen rendering outlet not appearing in that context (read more). The report included screenshots and narrowed the problem to an outlet selection tradeoff (read more).
-
Hosted customers asked how to recover individual missing CDN uploads (one image + two JSON attachments) after a hiccup, particularly when they’re comfortable self-hosting but unsure what options exist on hosted (read more; read more).
-
Embedding video from Bunny CDN Stream: attempts to paste a Bunny “player.mediadelivery.net” URL resulted in a plain link rather than an inline embed, prompting questions about allowed/whitelisted oneboxes and embedding rules (read more).
-
Discourse AI tool calls timing out: a user shared screenshots showing tool execution timing out during script testing and asked whether Discourse’s timeout can be adjusted (read more; read more).
-
Automation composer formatting: users trying to paste special markup like
[wrap]into automation text fields found that rich-text pasting escapes content; renato pointed out a fix that landed, while acknowledging the broader “rich editor vs plain markdown” expectation mismatch (read more). -
Sentiment setup and historical backfill: Falco pointed users back to the self-hosting guide for Sentiment/Emotion (read more)—and the follow-up clarified that the dashboard works, but the community wants more than 60 days of backfill and needs to know how far back is feasible (read more). For reference, the guide being cited is here: read more.
#Site feedback
-
Meta experimentation around “content gardening” doubled as a process question: Canapin explained they often flag their own old posts to request edits, but after a previous staff edit the flag UI only offered “It’s illegal,” so they asked for a better path (read more). darkpixlz solved the immediate need by turning the post into a wiki so the author can update it directly (read more).
-
That same exchange tied together several “knowledge curation” threads: Canapin wanted to update their earlier post about monitoring uploads (read more) to point at a relevant plugin and topic gallery tooling (read more), and darkpixlz noted staff-attention DMs can be replied to later since they tend not to close (read more).
#Plugin
-
ActivityPub troubleshooting continued with confirmatory logs showing repeated
/webfinger/handle/validaterequests and a follow-upfind-by-handlelookup, suggesting a consistent reproduction pattern across installs (read more). -
Topic Voting feature request: someone asked whether advanced search can be limited to “votable” areas and/or sorted by votes, referencing an older closed related question (read more; read more).
#Self-Hosting
- Cloudflare best practices got fresh field notes from a long-term proxy-mode setup: key takeaways included ensuring the Cloudflare template is in
app.yml, bypassing cache for/session/*, and skipping WAF on post creation/edits—plus a nuanced WordPress-comment caching strategy to handle bursty traffic (read more).
#Theme component
- Topic List Previews (TLP) theme component: a user reported that visiting
/u/user/messages/tags/abcwas being auto-switched into a “tiles topic lists” display mode and asked how to keep messages on the default display instead (read more).
bug
- Anchor links inside Discourse topics: renato reported they can no longer reproduce the issue after a fix merged, and moved toward closing the report unless someone still experiences it (read more).
General
- A “coding agents + SSH” anecdote: a community member described being emboldened as a Discourse admin by using coding agents to resurrect a long-dead vBulletin install—an interesting signal of how admin workflows are changing (read more).
users
- Discourse MCP setup in OpenAI Codex CLI saw a brief update: a follow-up post was deleted by the author, leaving the thread without that additional context (read more).
Activity by the @team Group
-
awesomerobot investigated why the composer toolbar overflow arrow wasn’t visible and asked whether safe mode showed it—strongly suggesting a theme/CSS interaction (read more). They also clarified current intent: the arrow is intentionally hidden on touch devices because horizontal scrolling is “easier,” while openly questioning whether the UI should change to show it anyway (read more).
-
chapoi diagnosed the Ghost theme issue where views/replies/activity disappear inside certain category lists, pointing to the
topic-list-after-categoryoutlet not being available when there’s no category context, and noted they’d check whether an easy outlet switch exists (read more). -
Falco supported a Sentiment/Emotion deployment by confirming whether the self-hosting setup guide was followed (read more) and then pushed for clarification on what data range was actually backfilled so troubleshooting could proceed with clear expectations (read more).
-
renato weighed in on the composer toolbar affordance logic, proposing a refinement: show/hide the arrow based on screen width or fine pointer availability, rather than the broad “touch device” rule (read more). They also noted an anchor-link bug appears fixed and queued the topic for closure unless further reports come in (read more), and confirmed an automation formatting/paste issue should be addressed by recent changes while acknowledging remaining UX tension (read more).
Sign-off: Yesterday’s meta moral: if your toolbar controls vanish, don’t panic—sometimes the missing arrow is just playing hide-and-seek until you flip into safe mode.