Tägliche Zusammenfassung (21 Uhr UTC)

[system]

Today on meta.discourse.org…

Key Stats

• New posts (last 24h): 36
• New topics (last 24h): 4
• Top users (posts / likes):
  • Crown1 — 8 posts / 5 likes
  • darkpixlz — 5 posts / 1 like
  • mcwumbly — 4 posts / 2 likes
  • Ethsim2 — 4 posts / 3 likes
  • Lilly — 2 posts / 7 likes
  • NateDhaliwal — 3 posts / 5 likes
  • Eviepayne — 3 posts / 1 like
  • Falco — 1 post / 2 likes
  • sniper756 — 1 post / 1 like
  • Moin — 1 post / 1 like

---

Interesting Topics

Support

• Crown1 reported that upgrading from Free to Starter didn’t appear possible (only Pro showed up), raising concerns about forced trials and plan visibility (hosted-support free-plan). The thread includes comparison screenshots and hints of potential A/B testing, with staff investigating and attempting a quick fix. read more
  Relevant posts: plan option discrepancy, staff diagnosis questions, attempted fix + follow-up

• Eviepayne asked for a declarative way to persist set_real_ip_from / real_ip_header X-Forwarded-For inside Discourse’s container Nginx when running behind HAProxy, after seeing client IPs collapse to the load balancer and triggering 429s (unsupported-install nginx). The discussion distinguishes host-vs-container nginx concerns and lands on using replace in app.yml to survive rebuilds. read more
  Key context: why the load balancer IP caused trouble, suggested replace injection snippet

• In a permissions/regression-style support question, a user reported they can’t delete topics anymore and is awaiting a fix; Prempavee closed with appreciation while waiting. read more

bug

• TroLLoBlogger documented a crash after attempting to update via the admin UI, then recovered by rebuilding from the terminal (./launcher rebuild app). The error log points to a plugin asset compilation timeout, and the thread pivots into practical guidance on update workflow and resource constraints. read more
  Notable replies: Lilly on avoiding admin-UI updates for self-hosting read more, and Falco requesting server specs to understand the 120s build timeout read more

• In an older-but-still-active bug report, Moin pointed to a fix PR for the “Thanks for Contributing” popup still appearing after the intended limit had been passed. read more

ux

• sniper756 reported that, on mobile browsers, the admin tag-group management page renders incorrectly (noted alongside “Modernize Foundation theme”), with a screenshot showing layout issues. read more

#Community Building

• A discussion on using Discourse for small town government sites focused less on software capability and more on institutional realities: moderation ownership, what counts as “official,” authentication, security, and user expectations. Ethsim2 emphasized that the human/process side is the hard part read more, while NateDhaliwal highlighted privacy implications—whoever hosts has “absolute access.” read more

Support (site setting behavior & governance)

• Ethsim2 proposed clearer behavior for /about group listings when “hidden groups” and “extra groups” overlap, including the idea of a boolean site setting like about_page_exclude_hidden_group_members to prevent unintended exposure through alternate group sections (groups about-page). read more
  The back-and-forth covers what each setting actually controls and where group visibility rules apply: Nate’s interpretation of the two settings, Ethsim’s reproduction/edge case, and the nuance that group interaction settings may still affect /about rendering read more

---

Activity by the @team Group

• mcwumbly jumped into a heated hosted-pricing/support thread to clarify that Starter has been deprioritized on the pricing page but should still be available from Free upgrades, then began troubleshooting where the upgrade flow was being triggered. See: initial clarification and question read more, confirmation it “should” appear and plan to investigate read more, an attempted quick fix read more, and the final “hang tight” update pending deeper review read more.

• Falco investigated a self-host update crash tied to plugin asset compilation timeouts, narrowing suspicion to the plugin build exceeding the two-minute limit and requesting server specs to confirm whether resources were the bottleneck. read more

---

May all your upgrade buttons reveal the plan you actually want—and may every ./launcher rebuild app finish before the timeout gremlins notice.