sam discussed potential uses for o1-preview & o1-mini models in custom AI tools, suggesting they could be used for specific reasoning tasks in conjunction with other models.
Discourse shared their first edition of Current Projects, a new monthly newsletter highlighting ongoing work. Key projects include a composer redesign, new theme chooser in the setup wizard, and improvements to the converter framework. Read more
A discussion on tips for new Discourse users to level up effectively, emphasizing natural engagement with the community rather than focusing solely on trust levels.
A community member shared positive feedback on Discourse’s effectiveness in reducing trolling and improving participation after migrating to the platform.
A user sought help increasing the size of their reply textarea in Discourse. After troubleshooting, it was discovered that the issue was caused by the “Choose Next Topic” plugin.
A question was raised about changing the link under the logo to point to the Categories page instead of Discovery. Solutions involving custom settings and theme components were suggested.
There was a discussion about configuring permissions to allow users to create posts in a category without seeing others’ posts. The built-in flagging system was recommended as an alternative.
A user asked for recommendations on plugins to enhance user engagement on Discourse forums. Suggestions included the Gamification plugin, Follow plugin, and the built-in Poll feature.
A thread discussed looking for the perfect theme for a Discourse forum, with users sharing various theme and component suggestions.
An issue was reported where bookmarks couldn’t be deleted in certain situations. The problem seemed to be related to how old bookmarks were recognized by the system.
The Discourse team shared an update on current projects for September 2024, including work on the composer, converter framework, and other improvements.
guidoleenders shared experiences with AI-based spam and the challenges of detecting well-crafted, relevant-seeming messages from temporary domains read more.
pfaffman discovered an issue with the path for importing the Form component in the Discourse toolkit. He suggested changing it to import Form from "discourse/components/form";read more.
A user reported problems compiling JavaScript in their component. merefield advised against using the widget API, recommending Glimmer Components instead read more.
NateDhaliwal encountered issues with settings not appearing in a theme component. Lilly provided a solution by creating a pull request demonstrating how to properly split up the files read more.
A user reported problems with Cloudflare’s Speed Brain feature causing Content Security Policy errors. simon suggested disabling the feature as a potential solution read more.
mbiistscther encountered a blank page issue on the activate account page after updating to Discourse 3.4.0. The problem may be related to Cloudflare’s Speed Brain feature read more.
nathank raised a concern about the 100 character limit for replacing words with links in Watched Words, suggesting it might be too restrictive read more.
jrgong reported an issue with category icons not displaying in mobile autocomplete search results on Discourse 3.3.1. Arkshine provided a quick CSS fix while suggesting a potential solution read more.
mcwumbly acknowledged feedback about developing for Discourse and the overall developer experience, promising to address it after the Meetup week read more.
Falco confirmed that making every system prompt of AIs editable is on their roadmap for the next few months read more.
david requested more information about a site experiencing missing icons read more.
Lilly investigated and provided a solution for missing category icons in mobile search results read more.
sam mentioned plans to add special guidance to the system prompt to ensure “ask” never recommends usage of widgets read more.
Thanks for reading, and I’ll see you again tomorrow!
patrickemin continued discussing issues with the approve unless allowed groups setting, providing screenshots of their current configuration and clarifying their desired approval flow for different trust levels.
wings inquired about retrieving user_api_keys values via API for authorization purposes. RGJ and simon explained that these keys are not retrievable and suggested alternative approaches for handling user authentication.
Moin reported a bug in the review queue where a “Translation missing: en” button appears for category moderators when reviewing posts with watched words.
HAWK clarified that storage limits in hosting plans are for uploads only and do not include the database. They also confirmed that there’s no limit to topics or posts, but page views are limited.
ppcole encountered an issue with blocked words in URLs when adding an event. It was resolved by identifying a watched word with an asterisk that was unintentionally matching legitimate content.
th21 reported incorrect activate URLs for traditional Chinese sites, causing “page not existed” errors. This may be related to a recent fix for URL generation.
A user inquired about removing topics from the latest list that they created themselves. Several solutions were suggested, including using plugins or muting specific tags.
There was a discussion about Google Docs image hotlinking and image compression in Discourse. Users debated the pros and cons of compression and explored various settings to control image quality.
A user reported trouble with new Font Awesome 6 icons in theme components. The community helped troubleshoot and provided solutions for using the updated icon names.
An issue was reported regarding Let’s Encrypt with multiple domains not working for ECC certificates. The community worked together to identify the problem and suggest fixes.
A discussion was started about SEO strategies for forums. Users shared tips and resources for improving search engine visibility for Discourse communities.
A user suggested adding SCIM support as a service provider to Discourse. The community discussed the potential implementation and challenges of this feature.
A user encountered an SSO issue with missing parameters when integrating Discourse with another platform. The community provided troubleshooting steps and configuration advice.
Stevej reported issues with category endpoints in WordPress integration. The problem was resolved by reverting the lazy load categories groups setting, as suggested by Lilly and RGJ.
Vede reported issues with the Discourse Hub app not connecting accounts after the latest update. The problem seems to persist for some users despite reinstallation attempts.
<h1><a name="today-on-metadiscourseorg-1" class="anchor" href="#today-on-metadiscourseorg-1"></a>Today on <a href="http://meta.discourse.org">meta.discourse.org</a>…</h1>
<h2><a name="key-stats-2" class="anchor" href="#key-stats-2"></a>Key Stats</h2>
<ul>
<li>New posts: 45</li>
<li>New topics: 6</li>
</ul>
<p>Top users:</p>
<ol>
<li><a class="mention" href="/u/moin">Moin</a> (18 likes, 5 posts)</li>
<li><a class="mention" href="/u/merefield">merefield</a> (5 likes, 3 posts)</li>
<li><a class="mention" href="/u/andrew15-5">Andrew15-5</a> (4 likes, 1 post)</li>
<li><a class="mention" href="/u/lilly">Lilly</a> (4 likes, 1 post)</li>
<li><a class="mention" href="/u/nathank">nathank</a> (4 likes, 2 posts)</li>
</ol>
<h2><a name="interesting-topics-3" class="anchor" href="#interesting-topics-3"></a>Interesting Topics</h2>
<h3><a name="feature-4" class="anchor" href="#feature-4"></a><a class="hashtag-cooked" href="/c/feature/2?silent=true" data-type="category" data-slug="feature" data-id="2"><span class="hashtag-icon-placeholder"><svg class="fa d-icon d-icon-square-full svg-icon svg-node"><use href="#square-full"></use></svg></span><span>Feature</span></a></h3>
<ul>
<li>
<p><a class="mention" href="/u/moin">Moin</a> discovered that <a href="https://meta.discourse.org/t/-/67983/7?silent=true">TL4 users can now be prevented from editing other users’ posts</a> by removing the trust level 4 group from the new “edit all post groups” setting.</p>
</li>
<li>
<p>There’s an ongoing discussion about <a href="https://meta.discourse.org/t/-/20666/18?silent=true">enabling the tab key in the markdown editor</a> to improve indentation functionality, similar to other Markdown editors.</p>
</li>
<li>
<p>A suggestion was made to <a href="https://meta.discourse.org/t/-/328507?silent=true">change the wording</a> when undoing a group membership acceptance from “request undone” to “user removed” for better clarity.</p>
</li>
<li>
<p>Users are discussing the possibility of <a href="https://meta.discourse.org/t/-/190706/2?silent=true">adding automatic group request accept/deny messages</a>, with automatic acceptance messages now implemented.</p>
</li>
</ul>
<h3><a name="ux-5" class="anchor" href="#ux-5"></a><a class="hashtag-cooked" href="/c/ux/9?silent=true" data-type="category" data-slug="ux" data-id="9"><span class="hashtag-icon-placeholder"><svg class="fa d-icon d-icon-square-full svg-icon svg-node"><use href="#square-full"></use></svg></span><span>UX</span></a></h3>
<ul>
<li>
<p><a class="mention" href="/u/andrew15-5">Andrew15-5</a> reported an issue where the <a href="https://meta.discourse.org/t/-/328472?silent=true">advanced tutorial was completed before reaching TL2</a>, causing redundant bot automation.</p>
</li>
<li>
<p>A bug was reported where <a href="https://meta.discourse.org/t/-/328510?silent=true">duplicate related topics tabs appear sometimes</a> in the interface.</p>
</li>
</ul>
<h3><a name="installation-6" class="anchor" href="#installation-6"></a><a class="hashtag-cooked" href="/c/installation/31?silent=true" data-type="category" data-slug="installation" data-id="31"><span class="hashtag-icon-placeholder"><svg class="fa d-icon d-icon-square-full svg-icon svg-node"><use href="#square-full"></use></svg></span><span>Installation</span></a></h3>
<ul>
<li><a class="mention" href="/u/joshhabka">joshhabka</a> sought help <a href="https://meta.discourse.org/t/-/328520?silent=true">setting up Discourse with Cloudflare Tunnels</a>, encountering issues with hostname recognition during setup.</li>
</ul>
<h3><a name="plugin-7" class="anchor" href="#plugin-7"></a><a class="hashtag-cooked" href="/c/plugin/22?silent=true" data-type="category" data-slug="plugin" data-id="22"><span class="hashtag-icon-placeholder"><svg class="fa d-icon d-icon-square-full svg-icon svg-node"><use href="#square-full"></use></svg></span><span>Plugin</span></a></h3>
<ul>
<li>
<p>The <a href="https://meta.discourse.org/t/-/180967/108?silent=true">Landing Pages Plugin</a> discussion continued, with clarification that it’s not available for standard <a href="http://Discourse.com" rel="noopener nofollow ugc">Discourse.com</a> hosting plans.</p>
</li>
<li>
<p>Exciting developments in the <a href="https://meta.discourse.org/t/-/256652/960?silent=true">Discourse Chatbot plugin</a> were shared, with <a class="mention" href="/u/merefield">merefield</a> reporting impressive results using the new llama3.2 model locally.</p>
</li>
</ul>
<h3><a name="theme-8" class="anchor" href="#theme-8"></a><a class="hashtag-cooked" href="/c/theme/61?silent=true" data-type="category" data-slug="theme" data-id="61"><span class="hashtag-icon-placeholder"><svg class="fa d-icon d-icon-square-full svg-icon svg-node"><use href="#square-full"></use></svg></span><span>Theme</span></a></h3>
<ul>
<li>Users discussed the <a href="https://meta.discourse.org/t/-/144264/133?silent=true">Homepage Feature theme component</a>, sharing alternative options for customizing the homepage.</li>
</ul>
<h3><a name="sso-9" class="anchor" href="#sso-9"></a><a class="hashtag-cooked" href="/c/sso/24?silent=true" data-type="category" data-slug="sso" data-id="24"><span class="hashtag-icon-placeholder"><svg class="fa d-icon d-icon-square-full svg-icon svg-node"><use href="#square-full"></use></svg></span><span>SSO</span></a></h3>
<ul>
<li>A user inquired about <a href="https://meta.discourse.org/t/-/328157/8?silent=true">Ghost integration with paid Discourse plans</a>, leading to a discussion on the complexity of setup and potential improvements.</li>
</ul>
<h3><a name="support-10" class="anchor" href="#support-10"></a><a class="hashtag-cooked" href="/c/support/6?silent=true" data-type="category" data-slug="support" data-id="6"><span class="hashtag-icon-placeholder"><svg class="fa d-icon d-icon-square-full svg-icon svg-node"><use href="#square-full"></use></svg></span><span>Support</span></a></h3>
<ul>
<li>
<p><a class="mention" href="/u/jagster">Jagster</a> asked about <a href="https://meta.discourse.org/t/-/328552?silent=true">updating all topics to show full WordPress posts</a> after changing a setting in the WordPress integration.</p>
</li>
<li>
<p>A user reported an <a href="https://meta.discourse.org/t/-/328549?silent=true">error with embed URLs in the Gutenberg editor</a> when integrating WordPress with Discourse.</p>
</li>
</ul>
<h2><a name="activity-by-the-team-group-11" class="anchor" href="#activity-by-the-team-group-11"></a>Activity by the <a class="mention-group" href="/groups/team?silent=true">@team</a> Group</h2>
<p><a class="mention" href="/u/lilly">Lilly</a> provided assistance in a thread about <a href="https://meta.discourse.org/t/-/328520/5?silent=true">installing Discourse with Cloudflare Tunnels</a>, pointing the user to a helpful guide on the topic.</p>
<p>Thanks for reading, and I’ll see you again tomorrow! <img src="https://emoji.discourse-cdn.com/twitter/slight_smile.png?v=12" title=":slight_smile:" class="emoji" alt=":slight_smile:" loading="lazy" width="20" height="20"></p>
lindsey provided an update on the Discourse composer update, mentioning that they are considering Lexical as a potential option for integration.
sam responded to inquiries about Discourse AI features, noting that while PDF support is not yet available, TXT files are supported in their Persona and Tool RAG implementation.
hugh acknowledged feedback on review queue improvements and mentioned that the team is currently working on making reasons for flags clearer and standardizing moderator actions.
A discussion continued on making Discourse installation easier, with nat suggesting a potential option to skip email setup during installation, though noting potential drawbacks.
