Biggest “news” posts: a Meta-only experiment with Boosts (read more) and an update to Solved notifications for watchers/trackers in support categories (read more).
Also seeing fresh replies in ongoing threads: numeric-tag URL errors (read more), localized emoji search aliases landing (read more), Bitnami installs being unsupported resurfacing (read more), and “how do I filter topic lists?” tips (read more).
Interesting Topics
#Announcements
lindsey introduced a live experiment: “Boosts”—a short, one-per-post micro-reaction that’s meant to sit between a standard reaction and a full reply (read more). Early feedback covered visibility glitches, naming confusion, translation gaps, and UX nits like accidental flag clicks near the boost UI (read more).
Discourse improved the solved experience: if you’re Tracking or Watching a topic in a support category, you’ll now get a notification when it’s marked solved (read more). The announcement also links back to guidance on setting up support categories (read more) and the main Solved plugin doc (read more).
The long-running “content gardening hub” experiment got a practical boost: Moin pointed out two near-duplicate feature requests about merging posts (read more), linking to “merge replies with OP” (read more) and “cannot merge first & second post” (read more). NateDhaliwal also shared a staff-focused topic-filter query to help find bug/#ux topics that probably need a fixed tag when a PR is already linked (read more).
Enforcing 2fa can strand logged-in users on the security screen, so the thread focused on how to embed better guidance into the enforcement experience. supermathie pointed to customizing site text strings (read more), while awesomerobot suggested a theme-component approach to insert richer HTML content above the wrapper outlet (read more).
A 500 error on an old numeric-tag URL (bad for crawlers) was diagnosed with logs and a likely backend name/ID resolution mismatch; nat confirmed the team has eyes on it and a fix is coming (read more).
On ask.discourse.com, a UI nit: the “Back to Forum” link appears even on the homepage where it’s redundant; NateDhaliwal proposed hiding it there (read more).
Tag banners looked “empty” because tags weren’t rendering; awesomerobot traced it to upstream data changes, shipped a fix in the tag-banners plugin, and confirmed they were back on Meta (read more).
A hosted AI translation mishap produced “AI commentary” / “thinking” text leaking into German output; nat said the agent formatting was tightened, linked the deployed fix, and cleaned up affected titles/posts (read more).
Cloudflare R2 backups: users reported multipart upload failures tied to aws-sdk-s3 1.182.0 (undefined method 'downcase' for nil). pfaffman shared a prior workaround thread (read more) referencing the earlier aws-sdk bump discussion (read more), and the OP confirmed pinning gems restored successful uploads (read more). (Related: ongoing CDN/CORS troubleshooting patterns also showed up in the recent self-hosting CORS thread (read more).)
iPad Safari briefly showed the composer jumping to the top and losing button functionality; after a few checks (including theme suspicion), the issue became non-reproducible—filed as “the joys of computing” for now (read more).
The Category Experts plugin crashed during user merges; zogstrip acknowledged the report and pointed to the PR that resolves it (read more).
#Feature
A localization edge case: in combined tag + category banners, tag icons render for English tags but not for translated tags; a feature request was opened to make translated tag banners consistent (read more)—building on recent momentum around translated tag/icon support (read more).
AI feature request: Mistral embeddings integration hits an OpenAI-compat mismatch (dimensions vs output_dimension), where leaving out dimensions makes tests pass but blocks saving because the UI requires it (read more). The report references earlier setup guidance for Mistral embeddings (read more).
“Where are the design resources?”: for UI designers, the recommended path was enabling the built-in styleguide; the topic was marked solved (read more).
lindsey kicked off two high-signal announcements: testing Boosts on Meta (read more) and Solved notifications for Tracking/Watching users in support categories (read more).
nat confirmed a fix is forthcoming for the numeric-tag URL 500 regression (read more), posted an update on the AI-translation “thinking text” leak (including cleanup) (read more), and continued the multilingual push by linking “Building for every language” as the next blog entry (read more).
zogstrip helped debug early Boosts rollout quirks (visibility/refresh) and clarified it’s not intended to reorder/bump posts (read more). They also pointed reporters toward a fix for a Category Experts merge crash (read more) and flagged Bitnami as a likely factor in a polls-related stack trace report (read more)—with relevant context that Bitnami installs are unsupported (read more) and the container image has been deprecated (read more).
awesomerobot shipped fast turnaround on a tag-banner regression: diagnosis + fix + confirmation on Meta (read more), and provided a concrete theme-component recipe to inject richer guidance into the enforced 2FA screen (read more).
supermathie shared the simplest admin-friendly option for 2FA enforcement messaging—customizing the relevant site text string in /admin/customize/site_texts (read more)—and earlier helped surface the severity of the numeric-tag URL 500s with logs (read more).
Falco closed the loop on a long-running emoji request: English + translated emoji aliases are now implemented, along with a payload size reduction (read more). They also chimed in on a self-hosting migration-collision oddity with a bit of gallows humor (read more).
davidb pointed to the upstream commit that should resolve group dropdowns not refreshing when new groups are created (read more).
“There are only two hard things in Computer Science: cache invalidation and naming things.” — resurfaced again while everyone tried out Boosts (read more).
Until tomorrow: may your tags resolve to names (not IDs), your backups finish multipart uploads, and your rockets boost morale more than they boost confusion.
A big chunk of today’s conversation clustered around how “Boosts” fit into Discourse’s interaction model—especially around naming, moderation, and UI complexity (read more, read more).
Interesting Topics
#Announcements
Lilly, putty, Shauny, Canapin and others dug into what Boosts are for (vs reactions/likes), whether they’re optional, and how moderation/flagging should work—plus a lively naming debate (“Boost” vs something less algorithmic-sounding) (read more, read more, read more, read more).
The new embedding approach prompted feedback about UX tradeoffs: infinite-scroll discoverability, iframe drawbacks, and “how do I add a top-level comment without scrolling to the end?” (read more, read more, read more).
A new official how-to covered auto-provisioning accounts when external auth (DiscourseConnect / OIDC / OAuth2 / SAML, etc.) is enabled—aimed at skipping the extra signup confirmation step via site settings (read more).
On Ask Discourse specifically, the “Back to Forum” link was called out as confusing on the homepage; awesomerobot noted ask.discourse.com is a special customization case and would be adjusted (read more).
Self-hosters revisited iOS “Add to Home Screen” push notifications: Falco confirmed it should work on iOS 16.4+, then the thread dug into why certain admin flows (e.g. impersonation) can break it and why Discourse currently wipes keys on logout (read more, read more, read more, read more).
A moderation workflow surprise: a hidden post can reappear after the author edits it, which prompted discussion about “intended behavior” vs “needs approval before reinstating,” and when “request revision” is the safer tool (read more, read more, read more).
A user asked how to stop the composer panel from appearing when editing; the conversation quickly narrowed to toggling between rich-text and Markdown modes (read more, read more).
#Plugin
A prototype “workspaces” plugin proposed turning top-level categories into Slack/Mattermost-like team spaces, pairing channels with chat channels, and adding join/leave + guest access flows; mcwumbly asked about real-world usage and rollout plans (read more, read more, read more).
The “Discourse Daily Challenges” plugin thread had a practical hiccup: GitHub access started returning 404 for some users, leading to a move to GitLab and updated links (and a side-note about GitHub account flags) (read more, read more, read more).
The long-running Pushover plugin got a fresh burst of life: featheredtoast posted that it’s been updated/modernized for current Discourse versions (read more).
A new report flagged that when using Mistral for translations, translated posts lose embedded images (text-only rendering), whereas OpenAI translations didn’t—complete with repro steps and an external example link (read more).
A Safari PWA issue report: /upcoming-events appears to trigger user-facing rate limiting in production, backed by a screen recording and version details (read more).
Cloudflare R2 backups: someone confirmed a workaround for multipart upload failures (aws-sdk-s3 1.182.0 / downcase nil) and noted the fix required placing the change in its own hooks: block (read more).
#Feature
A thread on “logged out” popups continued with a security/auditability angle: clarifying that admins can force-log-out users, and debating whether the UI should indicate who initiated the logout without exposing sensitive info like IPs (read more, read more).
awesomerobot spent time clarifying the intent and safety boundaries of Boosts—including that the feature will be optional, how it compares to Basecamp’s version, and current moderation coverage (watched words yes; AI scan not yet) (read more, read more, read more). They also pointed someone to discover.discourse.org when asked about transit/urbanism communities (read more), and noted Ask Discourse’s homepage needs a small customization tweak for the “Back to Forum” link (read more).
j.jaffeux outlined the longer-term interaction hierarchy thinking—where boosts sit today and how Discourse might eventually unify boosts/reactions/likes so communities can pick what fits their culture/scale (read more).
Falco confirmed that iOS home-screen installs on iOS 16.4+ should receive push notifications, and then pinpointed a specific code path that causes fragile behavior when admins impersonate users (read more, read more).
featheredtoast explained the security rationale behind wiping push keys on logout (preventing sensitive previews from going to logged-out devices), and floated a more nuanced approach (session-bound subscriptions) as a future improvement (read more). They also revived the Pushover plugin by modernizing it for current Discourse versions (read more).
mcwumbly jumped into the new “workspace groups” prototype to validate the direction and ask the most important question: “is this in the wild yet?”—helping frame it as an RFC before production migration (read more).
Yesterday’s vibe in one sentence: if your notifications didn’t push, at least your comments could still get a morale Boost—just maybe not three new buttons’ worth of it (read more, read more).
New activity (last 24h):69 new posts across 13 new topics (plus ongoing discussions), including threads like minimalist feature setups (read more), translation/language requests (read more), and category security regressions (read more).
Flagged confusing composer UX around “Discard” while editing posts (read more) and weighed in on preserving upload:// image links in AI translations (read more).
Shared a “minimal (but practical)” configuration and plugin/theme stack (read more), plus continued the “Boosts” UI discussion with prototype ideas (read more).
Confirmed Meta will add Ukrainian/Russian to the language switcher soon (read more) and discussed safe approaches to video codec/transcoding handling (read more).
Drove multiple localization/AI threads: Meta language support request (read more), Mistral translation image loss troubleshooting (read more), and AI triage scope questions for DMs (read more).
A Zenless Zone Zero “Inter-Knot” inspired UI theme — Monikas showed off a striking custom theme concept, with Lilly suggesting it be reposted to the proper theme category once a repo is ready (read more).
#Community_Building
How to grow a Discourse forum without a product/service behind it? — haydenjames described the classic “founder-as-primary-engine” problem (4 years in, still driving a large share of activity) and asked what actually moves the needle for pure-interest communities; responses stressed consistency, SEO, and accepting the 99-9-1 dynamic (read more).
Composer wording confusion: “Discard your post?” when you only meant cancel editing — RGJ highlighted a long-running papercut where the UI asks “Do you want to discard your post?” even when you’re merely exiting edit mode (and sometimes even with zero changes), proposing clearer “Cancel edit” / “Discard edits” language (read more).
#Feature
Auto-detect or reject VP9-in-MP4 uploads (iOS Safari playback failure) — shortmort37 reported “silent” iOS failures when users upload MP4 files that are actually VP9, and suggested rejecting, warning, or transcoding. Falco pointed to Discourse Video Stream and discussed the tricky security/performance trade-offs of safe local transcoding, possibly as an opt-in plugin (read more).
Images missing in translated posts when using Mistral (aicontent-localization) — a translation regression was narrowed down to model behavior: upload:// image links were not consistently preserved by Mistral Small, while switching to Mistral Large resolved the issue, reinforcing that prompt-following fidelity can vary significantly by model tier (read more).
Category security permissions reset when re-parenting categories (with simplified category creation enabled) — Moin provided a detailed repro where changing parent/subcategory relationships wipes carefully set security rules and re-enables everyone posting. The report explicitly ties to the setting/topic “Enable simplified category creation” (read more) and references Enable simplified category creation as a key toggle.
#Site_feedback
Please add Ukrainian or Russian languages to Meta’s language switcher (content-localization) — Denis_Kovalenko asked for Ukrainian/Russian on meta.discourse.org itself; Falco confirmed it’s planned for early next week and expects the current translation model to handle it (read more).
Meta category posting restrictions may have been unintentionally loosened — in the collaborative “content gardening hub” experiment thread, Moin noticed category descriptions and/or configs no longer match expected “only group members can post” rules for plugins/themes/announcements. mcwumbly connected it to the same class of “re-parenting resets permissions” issues and linked it directly to the new repro report (read more).
#Announcements
Testing Boosts on Meta: reactions/likes/boosts convergence and UI clutter — the “Boosts” experiment continued with users arguing that boosts and reactions feel redundant today, while pointing to longer-term plans to unify these feedback affordances; several UI decluttering concepts were shared (read more).
#Plugin
ProxyTracer: VPN & Proxy Blocker plugin release — ProxyTracer announced a new plugin integrating the ProxyTracer API to detect/block VPN/proxy traffic with caching and fail-open options, plus configuration details and CIDR whitelisting (read more). The thread also touched Safe Mode concerns, with pointers to settings and recovery flows like log back in as admin after lockout, and general plugin installation docs (read more).
How to tune TL3 thresholds (and find what’s blocking promotions) — Ed_S asked how to choose which trust-level requirements to adjust to reach a desired TL3 population; Moin marked a solution: inspect per-user TL3 requirements and use Data Explorer queries like “find users likely to become TL3” (read more) via this query thread.
Cloudflare + reverse proxy setup causing all traffic to appear as Cloudflare IPs (unsupported-installcloudflare) — a Chinese-language support thread dug into a multi-proxy setup (User → Cloudflare → 1Panel Nginx → Discourse) and why adding the Cloudflare template may not be sufficient when an intermediate proxy rewrites headers. The canonical reference remains the Cloudflare best practices guide (read more) and its template instructions (read more).
Structured data: “Missing field ‘text’ (mainEntity.suggestedAnswer)” after updates — Richie reported Google Search Console still failing schema validation even after updating to a build that was expected to resolve “AcceptedAnswer” issues, referencing the earlier bug topic (read more) and prior context (read more).
Does “AI triage automation” scan DMs between regular users? — Denis_Kovalenko questioned whether “Include personal messages” truly covers user-to-user DMs, citing real moderation-risk scenarios and asking if this is a limitation or intentional behavior (read more).
Falco confirmed Meta will add Ukrainian/Russian to the language switcher soon, responding positively to the localization request in #Site_feedback (read more).
Falco weighed in on safe handling of incompatible VP9 uploads in #Feature, pointing admins at Discourse Video Stream while noting that local transcoding has security/CPU abuse risks and may be best offered as an opt-in plugin (read more).
mcwumbly acknowledged and triaged a regression where category security settings reset during re-parenting, thanking Moin for the detailed steps and confirming it will be investigated (read more).
mcwumbly connected broader Meta configuration drift (lost posting restrictions in certain categories) to the same class of category re-parenting issues, linking back to the new bug report and committing to fix the underlying problem (read more).
May your edits be clearly “canceled” (not “discarded”), your boosts stay uncluttered, and your translations keep every last upload:// image link intact.
elmuerte published a new Ko-fi integration plugin that can reward donations with badges and group memberships via webhooks, plus notes about currency handling and anonymization hooks (read more; install guide reference: read more).
ars18 introduced Discourse MiniMod, a plugin for “organizer-like” powers (managing categories/tags/topics) without granting full moderator access, building on category group moderation (read more).
The ProxyTracer VPN/Proxy blocker thread continued with operational guidance: safe mode isn’t helpful for diagnosing it, so the author added steps for disabling via Rails console and clarified how safe mode access changes when “Enabled for All Visitors” is on (read more).
In Discourse Suggested Edits (experimental), sam confirmed a requested piece isn’t implemented yet and will be added, while others asked for category-selection ergonomics (top-level vs subcategories) (read more).
Two Data Explorer (data-explorer) papercuts landed back-to-back: one report shows the UI refusing queries that contain semicolons even when they’re inside quoted strings (read more), and a second report shows double HTML escaping in output (“Fish & Chips” instead of “Fish & Chips”) indicating a display-layer issue rather than SQL (read more).
A structured data issue was flagged as Missing field text in mainEntity.suggestedAnswer, and davidb replied that the team is investigating and will update soon (read more).
Mobile/editor UX remains under scrutiny: one topic was moved into bugs because users reported being unable to exit editing a post (at least on the mobile web) (read more).
Tablet workflow trouble: an iPad user reported they can’t scroll the topic while the reply composer is open in DiscourseHub, making quoting mid-reply awkward (read more).
A user reported a puzzling bottom-left overlay with “dots and lines”; after some misdirection about sidebar gadgets, bryce explained it’s likely a sidebar footer fade gradient artifact and provided a CSS variable override to disable the fade (read more; related: Sidebar Theme Toggle discussion read more).
To remove the fade: --d-sidebar-footer-fade: transparent; (read more)
The Testing Boosts on Meta conversation kept digging into what boosts are for: Canapin argued likes/reactions help the community discover valuable posts, while boosts may be more author-centric, proposing different default visibility for authors vs everyone else (read more).
“Clearing advice doesn’t actually clear it” gained traction when a contributor opened a PR to let admins ignore select problem checks properly, plus a dashboard tab to review/undo ignores (read more).
An admin asked whether AI triage automation (automationai) can scan regular-user DMs when “Include personal messages” is enabled; RGJ stated that it does (and asked how the reporter determined it wasn’t scanning) (read more).
In a solved thread on tuning TL3 thresholds (trust-levels), mcwumbly shared that meta reduced TL3 caps (topics viewed cap and posts read cap), based on learnings from a “who is likely to become TL3” query, and noted work is underway to roll out site-setting defaults more methodically (read more; referenced query topic: read more).
A French-language support question asked for a better way to notify all “Going” participants when an event is cancelled (calendar-and-event), pointing out manual PM tagging doesn’t scale; discussion centered on possible UI improvements and what “Close event” actually changes in notification behavior (read more; docs context: read more and read more).
In Alternative icons (referencetheme-guides), manuel pointed to Discourse’s lucide-based icon set repo and discussed brand icon mappings, prompting Canapin to suggest the official set should be highlighted more clearly in the original guide (read more).
The Horizon Theme (officialhorizon-theme) thread got an update from chapoi: no new compatibility work is currently planned, and they highlighted a likely conflict around the welcome banner outlet—suggesting configuration changes that might make it work (read more).
In “Claude & Discourse-related development,” new reflections landed on whether AI-generated work changes the migration/build landscape, with some skepticism about overly AI-polished writeups and a preference for more human-looking experience reports (read more).
The “Using dv (Discourse Vibe) to configure Discourse AI in development” topic saw follow-up questions about running multiple dev instances and mirroring a live site in dev behind a reverse proxy (read more).
manuel helped clarify the “official” direction for icon packs by pointing to Discourse’s lucide icon set and asking what improvements might still be needed (read more).
bryce diagnosed the reported bottom-left “artifact overlay” as a sidebar fade/gradient effect and provided a practical CSS override via --d-sidebar-footer-fade (read more).
sam responded in the Suggested Edits plugin thread, confirming a missing piece “isn’t implemented yet” and will be added (read more).
mcwumbly shared internal context about TL3 “cap” reductions on meta and described ongoing work to roll out future default site-setting changes in a more transparent, controllable way for admins (read more).
davidb acknowledged the structured data report about mainEntity.suggestedAnswer missing text, stating the team is investigating and will follow up (read more).
chapoi provided a status update on Horizon Theme compatibility priorities, noting roadmap decisions depend on demand and outlining a likely welcome-banner outlet conflict (read more).
That’s a wrap—may your sidebar gradients stay smooth, your boosts stay meaningful, and your Data Explorer finally serve “Fish & Chips” without the extra &.
sam shipped a small-but-mighty UX improvement: topic-level bookmark controls now surface all post bookmarks from the bottom-of-topic action, making it far easier to find what you saved in long threads—see Easier access to bookmarks.
A new theme component proposal introduces hover tooltips for internal topic links (topic preview “cards” on hover), with early feedback requesting screenshots and preview clarity in Topic Hover Cards.
#Feature
Feedback rolled in on the new Boosts concept: concerns about “visual flooding” on mobile at higher boost counts, plus suggestions like collapsible display and quoting UX, in Some ideas about discourse-boost plugin.
A CSS/layout troubleshooting thread: a navigation bar wraps awkwardly, and chapoi suggested white-space: nowrap; (and possibly overflow handling) in How can I fix this spacing issue?.
Users disabling translations report that the setting “comes back” after a while; today’s key detail is that it currently persists in local storage for 30 days, and a change is in flight to persist per-user across devices—see User disables translations, but they keep coming back.
RSS consumers found that exclude_tag works on /latest.rss but not on category feeds, with a confirmed workaround and a core fix queued—full repro steps in Exclude_tag does not work in category RSS feeds.
A localisation regression report: anonymous users visiting with ?tl=[lang] see inconsistent language across topic lists and inside topics, despite the UI showing the selected locale—recorded with a screencast in Localisation bug for anonymous users with ?tl=[lang].
A long-running plugin thread hit a breaking change: Topic Ratings UI vanished due to widget leftovers after a modernization effort; the thread includes analysis and a proposed fix path in Topic Ratings Plugin.
#Self-hosting
A (very) large VPS sizing question sparked discussion about whether huge NVMe allocations are necessary, and whether the question is Discourse-related; the context includes running Discourse plus other services—see 请问有使用netcup root server的么？.
#Nested Replies Testing
Nested replies UX exploration continued: a user discovered “Pin” behavior differs between nested vs flat mode, and the answer is that pinning is currently nested-mode-only—see 发现了在Topic中 Pin 的功能，这是只有在嵌套模式下才可以使用么.
Plugin/theme author fatigue surfaced in the ongoing template deprecation conversation: a plugin maintainer asked how to responsibly sunset plugins without breaking downstream users, and david outlined safer paths (marking broken/unmaintained, archiving, enabling forks)—see Deprecating .hbs file extension in themes and plugins.
sam shipped a bookmarks UX improvement and then immediately dug into mobile edge cases around indicating “post bookmarked vs topic bookmarked” in Easier access to bookmarks.
Yesterday, Meta got easier to navigate (hello, bookmark shortcuts), learned to smile in more languages (localized emoji aliases), and kept sharpening the theme toolkit—one Lucide stroke at a time.
supermathie asked clarifying questions about what “private topics” meant in practice, and later requested better postmortem details for future readers in the same thread.
Moin flagged inconsistent plugin availability notes and also called out outdated plan naming in official plugin banners in a site feedback report.
tknospdr hit a scary “ticket visibility” surprise using the #private-topics workflow; the root cause ended up being a misunderstanding of “Private topics permitted groups”, and RGJ explained exactly why TL0 users could see everything in the accepted solution (also see the related plugin thread: read more).
API users asked about hiding a post via the API without resolving flags; awesomerobot confirmed the limitation and suggested tuning hide_post_sensitivity as a practical workaround in Hide posts via API.
A Cloudflare proxy setup caused all traffic to appear as Cloudflare IPs in admin views; the thread moved toward “restore real visitor IP” guidance (Apache example shared) in this support topic.
Email operations discussion: separating mail subdomains and moving from POP3 to the newer mail-receiver model came up in Auto-restarting once a day via cron?.
Subscriber automation: hipp0 asked for automatic add/remove of users to groups when subscriptions start/end; Moin pointed out the subscriptions plugin already does this group lifecycle management in Subscriber group automation (plugin reference: read more).
Mobile bookmarks UI got a serious iteration: chapoi proposed reusing the sidebar’s nested dropdown patterns to make bookmarked-post navigation clearer, and sam prototyped it (including multi-level menu concerns) in Unable to tell “post” bookmarks exist in footer on mobile.
Topic split “small action posts”: a request suggested the display text should survive topic renames more predictably (or rebuild like oneboxes do), explored in Link in “Split this topic” mini post.
Backups UI anxiety: admins sometimes see “no logs yet” even when the backup succeeds, raising concerns about failure-state observability in Backup process page keeps saying “no logs yet”.
Calendar integration fix (calendar-and-event): Google Calendar was using the webcal URL as the “Calendar Name”; Falco shipped a core fix using X-WR-CALNAME in this bug report.
Theme component update behavior: .discourse-compatibility is honored on install, but not reliably re-checked on subsequent updates; RGJ described a painful uninstall/reinstall workaround and requested rollback-aware updates in Theme (component)s do not look at .discourse-compatibility on update.
#Plugin
Geo-blocking enhancement: a contributor proposed an IP allowlist feature, and RGJ welcomed it with a performance constraint (avoid extra DB calls per request; use lazy-loaded cache) in Geo Blocking plugin.
#Site feedback
Official plugin topic banners appear to have outdated/inaccurate “available on all hosting tiers” notes after pricing/tier changes; examples were collected (including plan name drift like “Standard” vs “Pro”) in Inaccurate plugin availability notes on meta with related plugin topics cited: Math, Cakeday, Solved, Yearly Review, plus an older banner example in Advertising.
Helped untangle conceptual confusion around “private topics” vs PM/group inbox workflows, and later pushed for a more useful postmortem for future readers in Sudden realization about issue with Ticket System.
Noted that the calendar fix should also satisfy Outlook’s expectations for X-WR-CALNAME in the calendar bug thread.
Yesterday’s vibe: half the forum was polishing UX edges while the other half was doing “PRs on our brains” to fix configuration mix-ups—may your bookmarks be discoverable and your private topics stay private.