Resumo Diário (13h UTC)

Notícias e Eventos Resumos do fórum
908

Today on meta.discourse.org…

Key Stats

In the past 24 hours, there have been 30 new topics and 106 new posts across meta.discourse.org, drawing 103 likes. The top contributors by likes this period were:

Interesting Topics

#Announcements

  • PostgreSQL 18 upgrade for self-hosters — Chrisr announced the rollout of PostgreSQL 18 in the Discourse Docker image, with detailed instructions for single-container and data-container setups, plus warnings about disk space (the check now requires 2x the DB size in free space). Commenters hit issues ranging from pg_dump failing on single-CPU hosts (@nachocaballero, @Ivan_Rapekas) to upgrade-loop recovery paths (@chrisc); Chrisr fixed the core-count detection to use nproc --ignore=1. read more

ux

  • Where did the version information go? — Kjell and others questioned why the redesigned admin dashboard dropped version/technical info, with Ed_S feeling it’s “marketing-led” over engineering-led. Lilly observed the dashboard is now geared to “community managers,” and Mcwumbly explained the team’s intent to consolidate version details into the “Manage updates” page. read more

  • I don’t see the red line for last visit — Ed_S briefly feared the “red line” indicating unread posts had been removed, but Lilly and Canapin confirmed it still displays normally; NateDhaliwal noted a transient miss after a page refresh but it returned. read more

development

  • Clarifying the ‘posts read’ TL3 promotion logic — NateDhaliwal struggled to understand why the TL3 requirement multiplied posts by a percentage and took a minimum; Mcwumbly explained that tl3_requires_posts_read is a percentage bounded by a cap, making the math clear. read more

  • Now in Beta: Plugin to see TL3 Progress for TL2 users — EricGT raised a nuanced edge case: muted categories can inflate the “posts read” requirement. He proposed a category-by-category breakdown in the plugin to show eligible vs. read posts, which NateDhaliwal noted core itself lacks. read more

#Self-hosting

  • Any cheaper alternatives to Hetzner? — Lilly, Merefield, and Jagster dug into running Discourse on minimal hardware. Jagster shared real-world numbers from a 4-vCPU / 8GB server running a dual-container setup with 1000–1500 daily visitors and needing 4GB swap during rebuilds; Merefield suggested 3+ cores for dual-container comfort. read more

  • Configure a supported tracking branch to get Discourse software updates — Ghorbani questioned whether git pull remains necessary in the daily upgrade workflow. David confirmed it’s effectively redundant—launcher auto-detects and pulls the latest commit—though Ed_S prefers to play it safe and run it anyway. read more

#Praise

  • Dependent Plugin Settings are … AWESOME! — Merefield showcased the new dependent settings feature (settings visible only when relevant), calling it “:sparkles: fantastic” for reducing plugin config clutter and cognitive load. He shared pointers to the schema docs and examples from the Chatbot plugin’s settings.yml. read more

Support

  • Hola, me gustó el theme actual que tiene Discourse — Picho_Pelis asked about Meta’s branded theme; Canapin explained it’s not public, linking to prior discussion about the custom nature of Meta’s look. read more

  • Cannot view post preview in mobile composer? — FishHead reported that the rich text editor toggle fails on markdown like [color=red]. Chapoi said the plan is to improve the toggle and only re-instate the preview button if that proves insufficient, recommending the community Mobile Composer Preview component for now. read more

  • Unable to switch accounts—Sign In automatically logs into the previous account — FlowCaffe described getting locked out of an admin account in Chrome; Pfaffman explained the Discourse ID single-sign-in flow, suggesting a logout at id.discourse.com or impersonation via the Admin user page. read more

  • What happened to claiming reviewables? — Darkpixlz couldn’t find the “claim” button in the review queue. Lilly and Moin traced it to an admin site setting (now optional), and Darkpixlz confirmed that solved it. read more

#Feature

  • Add interface preferences to individually hide Suggested and Related topics — Akanora proposed two separate user-level toggles (hide Suggested / hide Related) to reduce clutter, explaining his choice might vary per-community; Mcwumbly asked probing follow-ups about real-world usage patterns. read more

#Plugin

  • Discourse Chatbot :robot: — Merefield published a comprehensive PR round-up for the Chatbot plugin (v2.4.1), covering new local reasoning strategies, a semantic blocked-question gate using embedding similarity, replacement of the unsafe SafeRuby evaluator with Dentaku, and adoption of Zeitwerk loading. read more

  • Discourse Workflows — Sam announced a new PR adding interaction API support to Discourse Workflows and invited testing in a trial environment; Eviepayne also left feature-gap notes (e.g., missing pagination in the HTTP request block). read more

Activity by the Team Group

  • Chrisr posted the flagship PostgreSQL 18 upgrade guide, then worked through the comments: correcting the disk-space check to 2x DB size, fixing the single-CPU pg_dump job count bug, and explaining how to postpone or recover from failed upgrades. read more

  • Mcwumbly provided the canonical explanation of the TL3 “posts read” percentage calculation and cap, and offered a thoughtful breakdown of why the admin dashboard now targets “community manager” vs. “sysadmin” hats, directing users to the “Manage updates” page for version info. read more | read more

  • Chapoi responded to UI feedback in two threads: confirming the rich-text-editor preview toggle is being improved (with a third-party component as a temporary patch) and clarifying that the Welcome Banner is intentionally hidden on small screens, including a CSS snippet to override it. read more | read more

  • David clarified that ./launcher automatically pulls the latest discourse_docker commit, making a manual git pull unnecessary in standard workflows. read more

  • Sam acknowledged Daily Summary feedback and committed to a validation rework (“may take a week or 2”), and also shepherded a new Workflows PR adding interaction API support. read more | read more

  • Tgxworld stepped in on the Spanish-language install thread to tell Picho_Pelis that a recently pushed bug had been fixed and a launcher rebuild app should resolve the postgresql.conf failure. read more

  • Pfaffman diagnosed an account-switching lockout caused by Discourse ID single sign-on, suggesting logout at id.discourse.com or admin impersonation as workarounds. read more

Between the PostgreSQL 18 migration drama, a flood of Chatbot PRs, and a detour into music theory, it seems even the most technical days on meta can still end with a tune! :musical_notes: