Welcome to our AI-generated Daily Summary topic! (9:00 PM Edition)
This is the topic where a daily summary of meta’s activity is collated by our good friend Bert, and posted here so everyone can get a rundown of some of the top discussions over the past 24 hours.
To account for our global audience, we have three editions (this one, Daily Summary (5am UTC), and Daily Summary (1pm UTC)), which fire at different times of the day so you can get one at a time most convenient to you. All of them cover the last 24 hours (respectively), so the main difference is when they land.
If you’d like to get a ping whenever a new one is posted just set this topic to Watching (and if you change your mind, change it back ).
Feedback is certainly welcome. We’ll be tweaking and refining the idea as we go, so all input is encouraged. We do have a separate topic for that so as to keep this one just for summaries. You can find that here - Daily Summary Feedback
Enjoy!
Small caveat… AI (even GPT-4) does hallucinate, it is unavoidable. Don’t treat everything it says as truth, as there will likely be some lies mixed in. We’ll try to manually correct any if we spot them, but still… keep an eye out.
Users reported issues with oneboxes not working for certain websites. martin explained that private GitHub oneboxes were recently added, but this shouldn’t affect other sites. The team is investigating the problem read more.
A request was made for per-topic or tag-based settings to navigate to the first post after topics are read, which would provide more granular control over topic navigation.
Users reported an issue with iOS not loading CSS when navigating between subdomains. pmusaraj implemented a potential workaround using a <base> tag, but this caused problems with the DMs button. The team is continuing to investigate and has reported the issue upstream to WebKit.
davidprovided guidance on the deprecation of parentView access in PluginOutlet and suggested alternative approaches for accessing information higher up in the component tree.
JammyDodgerconfirmed that video embedding is supported on the Standard plan and offered assistance for users experiencing issues.
joffreyjaffeuxaddressed an issue with the Custom Header Links component and is investigating a potential fix for invalid URL validation.
jordan-vidrineannounced that the usercard redesign experiment has been turned off as they plan to merge the new design into core Discourse.
natreported that database tables for the Topic Voting plugin have been migrated to match the naming convention of post voting tables.
Roman_Rizziassisted a user with installing the Discourse AI plugin and provided guidance on pinning the plugin to a specific commit for Ruby 3.3 compatibility.
hellekin raised concerns about the recent changes to the Terms of Service, suggesting that a link to the specific changes and a way to provide feedback would be helpful. Several users agreed, noting the importance of understanding what has changed before accepting.
yotarid encountered difficulties accessing the system admin space to update their Discourse instance. It was discovered that they were using a CERN-specific setup, which may require different update procedures.
Eugene49 inquired about using a custom domain for their Discourse-hosted forum to bypass access restrictions in their workplace.
MustardMan reported a broken logo in the site header during the development stage of their community. The issue was resolved by enabling the “force https” setting in the admin panel.
Moin discovered an issue with iOS not loading CSS when navigating between subdomains. It was clarified that this affects all browsers on iOS/iPadOS due to Apple’s restrictions on browser engines.
kryptosurfer64 reported ongoing sitemap issues in their Google Search Console, seeking solutions to fix the empty sitemap_recent file.
A discussion about supporting GPT-4o mini in Discourse AI was initiated, with users expressing interest in trying the new model while acknowledging potential hallucination issues.
debonair_marmot sought advice on organizing a multi-lingual site for people with under-recognized diseases, considering whether to use subcategories or tags for diseases within language categories.
Aaron_Walsh sought information about updating terms of service on the Discourse platform. They later confirmed successfully adding the required fields.
david responded to a report about an increase in CPU load possibly due to CSS, suggesting that the change might be related to differences in monitoring systems or how Discourse responds to them.
thoka proposed an idea for improving multilingual translations in the Multilingual Plugin, suggesting a unified file structure for easier updates and context-aware translations.
HAWK provided support for a user having trouble with custom domains, advising them to email the Discourse team for direct assistance with hosted plans.
david offered insights on a reported increase in CPU load, suggesting it might be due to changes in monitoring systems rather than actual performance issues.
A user reported a critical issue where a bad MF translation string in the Hebrew client locale caused a fatal site error. The problem was traced to a malformed string in the config/locales/client.he.yml file, highlighting the importance of proper localization formatting.
An inconsistency in plural definition was discovered, potentially affecting multiple languages beyond just Hungarian and Hebrew. This issue stems from discrepancies between Discourse’s plural rules and those defined in the make-plural library.
A user encountered a problem where reply-by-email includes other users’ unsubscribe links, allowing recipients to potentially unsubscribe other users from forum notifications. This security concern needs to be addressed to prevent unauthorized unsubscriptions.
Some users reported that chat messages are not showing up unless they refresh or switch channels, indicating a potential issue with real-time message delivery or client-side updates in the chat feature.
A user inquired about disabling unlimited loading of the topic list, preferring a “See more” button after a certain number of topics instead of infinite scrolling. This request highlights a desire for more control over content presentation.
An interesting discussion arose about why Discourse hasn’t been rewritten in Rust, touching on the complexities of large-scale rewrites and the recent frontend rebuild with standardized components and styles.
A user shared positive feedback about working with Arkshine on fixing a plugin error related to topic-bulk-actions, praising the developer’s professionalism and communication.
Responded to a bug report about reactions being removed when changing to a like, acknowledging the potential connection to recent changes in reaction functionality.
Provided a detailed explanation of themes and color schemes in Discourse, helping a user understand the difference between these customization options and how they affect the site’s appearance.
Thanks for reading, and I’ll see you again tomorrow!
david provided an update on the issue with pluralized translations, explaining that a change has been made to limit the impact of failed compilations to only affect _MF strings rather than taking down the whole site. The team is continuing to investigate the root cause read more.
A discussion about improving Gravatar avatar management was started, suggesting the implementation of Gravatar’s new Quick Editor feature to simplify how Discourse users update their avatars.
Jaskaran inquired about the distribution of votes in the topic voting plugin, wondering if TL1 users’ 10 active votes can be spread across different topics within a specific category or across multiple categories.
A user reported an issue with the “Body seems unclear” error when typing in Chinese. zogstrip shared a pull request addressing this problem, which includes performance improvements and better handling for non-Latin locales.
iluvjoshallen encountered a bootstrap error when attempting to start Discourse, receiving a “failed to create the container ID file” message. pfaffman suggested checking if Docker is working correctly.
A request was made to add CSS to a Discourse instance. Bas explained that custom CSS is not included in the Basic plan and requires a higher-tier plan.
Full30 initiated a discussion about the Terms of Service and sought clarity on what constitutes off-topic, unprofessional, or disruptive content in the context of civilized discourse.
Gotchur expressed appreciation for the Right Sidebar Blocks theme component and asked for help in making it compatible with the Redditish theme’s custom right sidebar.
davidprovided an update on the issue with pluralized translations and shared a pull request to address the problem.
JammyDodgerresponded to a user regarding moderator access to Watched Words, confirming that the functionality is working as expected despite a minor UX bug.
A discussion on why old topics are closed and the auto-bump feature. JammyDodger explained that auto-bumping helps keep content up-to-date, but acknowledged it can be annoying for some users. The community discussed potential alternatives like flagging old topics for review instead of bumping them.
A user noticed that buttons now have sharper corners in the interface. Others pointed out that the changes vary between the Meta branded theme and the default theme.
There was a discussion about having fewer trust levels in Discourse. JammyDodger suggested ways to effectively use the existing trust level system for closed communities.
angus introduced the new Journal Plugin, which allows turning a Discourse topic into a one-to-many journal where one user can post entries that other users comment on.
Full30 expressed interest in the Landing Pages Plugin and asked about its potential to replace WordPress. cabidop provided insights on the plugin’s intended use and ongoing maintenance.
Users reported an infinite-loading loop issue with the new topic map. david confirmed it was due to a bug introduced on Monday, which has since been fixed in core but not yet deployed to Meta.
Jarjar encountered an issue where a category group couldn’t be opened, which turned out to be caused by an ad blocker. The community suggested whitelisting Discourse or using a different group name to avoid conflicts.
huynhthai824 reported issues with the Topic Cards theme component, noting that an additional component to hide activity and username was not working on their site.
A user reported issues with the “Reset Bump Date” feature not working as expected. JammyDodger initially provided incorrect information but later corrected himself, demonstrating the complexity of this functionality.
Mohan43u encountered a problem with unverified users creating topics. After investigation, it was discovered that the issue stemmed from users deleting their own accounts.
A user reported being unable to upgrade due to a Docker Manager error. JammyDodger suggested the issue might be related to MaxMind and recommended rebuilding from the command line.
Small caveat… AI (even GPT-4) does hallucinate, it is unavoidable. Don’t treat everything it says as truth, as there will likely be some lies mixed in. We’ll try to manually correct any if we spot them, but still… keep an eye out.
