Resumo Diário (21h UTC)

Notícias e Eventos Resumos do fórum
946

Today on meta.discourse.org…

What a whirlwind 24 hours on Meta! The Discourse community has been buzzing with activity, from major designer test programs to deep philosophical debates about the future of the internet. Here’s your comprehensive digest:

Key Stats

The past 24 hours saw 192 new posts across 62 topics, generating 348 likes from the community. This represents a healthy mix of product feedback, support troubleshooting, and community discussions.

Top contributors by likes:

Other prolific contributors included Don (14 likes, 3 posts), Satonotdead (13 likes, 12 posts), Merefield (13 likes, 5 posts), NateDhaliwal (10 likes, 9 posts), and Mcwumbly (10 likes, 3 posts).

Interesting Topics

#Announcements

  • Chapoi announced the experimental composer redesign, which moves the toolbar to the bottom, integrates the title into the editor, and massively improves mobile composing with an expanding editor. The feedback has been passionate — Satonotdead compared adapting to the change to when “I was one of the folks who DIDN’T want a touchscreen on my cell phone” while Don noted it solves the long-standing problem where the context menu covers the editor button bar on mobile. Shauny raised concerns about muscle memory and accidental posts, but Canapin pushed back, saying the bottom toolbar “makes much more sense on mobile. Way easier to reach it” (read more).

  • The PostgreSQL 18 update continues to generate discussion. Pfaffman shared his manual multi-database migration approach, while Supermathie offered guidance on Google Cloud SQL upgrades. Lilly posted a detailed step-by-step walkthrough for dual-container setups behind Cloudflare, including disk cleanup commands, scheduled maintenance page strategies via Cloudflare workers, and the proper rebuild order. Tobias_1 shared a fix for the “cluster is owned by group id 993” error that plagues some upgrades (read more).

  • Sam revived the long-running discussion on admin “regular mode” (a sudo-like feature), suggesting that “maybe by default admins are just like any other user, except that they have a special page where they click a button to get temporary admin permissions.” Mcwumbly strongly agreed, proposing a toggle in the header with state clearly indicated. Lilly pushed back, saying she’d prefer an admin setting so she doesn’t have to “toggle into admin mode to get to /admin,” and Moin drew parallels to the existing suppress_secured_categories_from_admin setting (read more).

#Self-hosting

  • A truly epic saga unfolded in the Spanish-language topic “Ya estoy cansado, he instalado discourse en varios VPS ninguno me funcionan” (“I’m already tired, I’ve installed Discourse on several VPS and none of them work”). After extensive troubleshooting involving Jdc20181's Cloudflare insights, it turned out the domain debatehosting.co didn’t exist at all — Supermathie demonstrated this with a whois query showing “DOMAIN NOT FOUND.” Merefield noted the OP cancelled the domain during troubleshooting, which made it look like SSL issues. Satonotdead explained the real culprit: repeated attempts to get certificates hit Let’s Encrypt rate limits, which is “not the same as ‘SSL blocked my domain’” (read more).

  • In a thoughtful discussion about password reset security, Roke_Julian_Lockhart described being locked out when OpenAI disconnected their SSO integration, replacing it with an unfamiliar email alias. The thread sparked a genuinely moving exchange where Pfaffman publicly apologized: “I was a jerk and I humbly repent.” Pfaffman went on to acknowledge that “it’s not that uncommon for users in a long lasting community to no longer remember their email address” and questioned the logic of hide_email_address_taken requiring the email field, since “resetting the password with the username does not expose an email address” (read more). This led Roke_Julian_Lockhart to file a feature request for username-based password resets.

  • Picho_Pelis returned with a SMTP configuration question after the domain debacle, getting a prompt “try port 2525, port 587 is likely blocked” from Pfaffman, plus a security reminder from NateDhaliwal to censor credentials in public posts.

Support

#Feature

  • A feature request for multiple profiles per user (inspired by Discord’s PluralKit system) gained traction. A_Lilian made a compelling case: “Autonomy and expressiveness through online profiles matter. They give us the smallest window to the people past our screens and as such, are one of the primary pillars for building a humane web.” Satonotdead noted how the technical challenge lies in the fact that Discourse Chat “is built entirely into static user profiles” (read more).

#Site feedback

  • Lilly spotted an error banner on Meta reading “MERGE_BRANCH deployment failed.” Tgxworld confirmed it was fixed, then NateDhaliwal noted it persisted, and David explained the root cause: a hosting system for deploying git branches was throwing a merge conflict error that “wasn’t supposed to be displayed to everyone.” It’s now fixed for real (read more).

#Community Building

  • Mcwumbly kicked off a fascinating discussion about the next decade of the internet, reflecting on Discourse’s original 2013 promise. Awesomerobot delivered a brilliant response arguing that “I expect to be talking to people in 2036 the same way I was talking to people in 2013: typing words into boxes” and warned about AI chatbots seeking to “shortcut the web entirely,” while affirming Discourse can be “a safe harbor where you’re not subject to the massive unknowable algorithms.” Ed_S added concerns about increasing legal regulations (like the UK’s Online Safety Act) making it harder to run independent platforms, and Satonotdead outlined two possible futures — a hub format with deeper integrations, or a hardened, cypherpunk-esque decentralized platform (read more).

ux

development

  • Don unveiled a native Glimmer implementation of a Facebook-style topic modal, avoiding iframes entirely. He detailed how the modal reuses Discourse’s own Post components with a patched postStream, handles direct links and internal routing without escaping the modal, implements infinite scroll via IntersectionObserver, and even adds a skeleton loading state. Damian_Boon reacted enthusiastically: “I’d love to test your version :heart:”

#Theme component

  • Scavin released Clean Share URL, a theme component that adds a per-user preference to strip usernames from shared links (?u=username), addressing privacy concerns for users who don’t want their username attribution in shares. The component supports an optional custom user field for confirmation (read more).

bug

Activity by the Team Group

Our hardworking Team members have been extremely active across many fronts:

And in a day where Pfaffman publicly repented, Satonotdead mused on her pre-touchscreen cell phone days, and we learned that a missing domain name caused infinite Spanish-language pain… never forget: if your Discourse won’t install, make sure the domain you’re pointing at actually exists first — SSL can’t negotiate with a domain that isn’t there! :house::dashing_away:

Daily Summary Feedback