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.
In a discussion on when to @ mention users, Architect suggested using @ mentions so names update if usernames change. HAWK noted it depends on the community, and should only be used to call someone into a discussion they aren’t part of yet.
supermathie shared a cautionary tale of an AWS S3 invoice over $1000 just two days after setup, noting that Discourse’s upload bucket name is not obscured and can be abused if discovered.
kuazaasked about the rationale for serving separate JS and CSS files in Discourse rather than combining them. They wondered if reducing the number of files could improve initial boot speed.
velichorasked about which features and plugins are available in the open source version of Discourse on GitHub compared to the hosted plans. supermathie clarified that everything is available in the self-hosted version without restrictions.
ncaming215 couldn’t find the ‘Automation’ tab in their Discourse instance and asked for help locating it. They realized it was because the Discourse Automation plugin needed to be enabled first.
Moinpointed out an issue with the “no results” text in the user directory. When filters are applied and no results are found, the current text about the community being “brand new” doesn’t make sense. Reverting to “No results were found.” was suggested.
Diego_Santos encountered some UX issues on iPhone with the Discourse Hub app and Chrome browser. The problems included the keyboard covering input fields and not being able to scroll or save posts. merefield advised checking the theme CSS.
HAWK noted that Richard_Millington’s [request for paid theme/plugin work://meta.discourse.org/t/paid-work-custom-theme-plugin-work-developer-needed/306208/5) with a $300 budget may be challenging to fulfill.
Thanks for reading, and I’ll see you again tomorrow!
James_Dean is seeking a developer for paid custom theme/plugin work. There was discussion around reasonable pricing, with HAWK noting Discourse charges $250/hour for engineering time, but a non-CDCK dev may be able to implement pagination for around $300. read more
piffyquestioned the wording of the bookmark actions, finding “Edit” and “Delete” momentarily confusing in terms of whether they applied to the post or bookmark. They also felt “Delete” in red was a bit intense for the common action of removing a bookmark.
In a discussion on combining JS and CSS files for performance, sam noted evidence is required that bundling would yield benefits on HTTP 2.0 sites like Discourse, and that JavaScript eval is the current bottleneck rather than number of files.
In the Split profile hiding and presence topic, lindsey started a poll to gather feedback on how often users want to change their online presence settings, as part of investigating separating profile hiding and presence settings.
sp-jordan-violet discovered an unexpected behavior when bulk adding users to a group by email - it emails invites to every address not found. More verbosity in the UI copy was suggested to make this clearer to admins.
jidanni suggested that clicking “Mark Unread” on a post should not navigate the user away from the current topic. However, others noted this may be unavoidable to prevent the post from being re-marked as read.
Ryan_Hyer had issues after moving Discourse to a new server, with the admin panel inaccessible. Disabling Cloudflare’s “orange cloud” resolved it. Avoiding Cloudflare’s JS “optimization” features was recommended.
david investigated an iOS Safari loading issue after a Discourse upgrade and reverted a change while continuing to look into Cloudflare and Safari 15 problems. He also fixed missing images in a popular topic.
sp-jordan-violetnoted the new topic map blends in too much with posts on meta and shared how it looks more visually distinct on their own site.
MarcPasked if safe mode access should be off by default for non-staff, as it allows bypassing custom CSS and plugins. Moin and Lilly shared thoughts on when safe mode is helpful vs restricting it.
Truest was seeing #numbers next to site text and wondered how to remove “powered by Discourse”. simon explained the numbers are from enabling verbose localization. Moin guided on where to find settings to customize the text.
Lillyshared that as an admin she disables safe mode for anon users and thinks it should be staff-only by default.
awesomerobotasked if non-staff safe mode access actually causes problems in practice, as users can do many of the same things via browser dev tools.
joffreyjaffeuxexplained that the header flash when returning to a topic from the menu on iOS is a current limitation of how the header is implemented when locking the body.
Thanks for reading, and I’ll see you again tomorrow!
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.
