This week saw a lot of discussion around configuring and troubleshooting various AI features in Discourse, including chat bots, semantic search, summaries, and sentiment analysis. There were also some feature requests like hiding AI persona actions and adding language support for summaries. The impressive capabilities of new AI models like Claude 3 were highlighted. A few bugs were reported and some were fixed.
This week saw a lot of activity and discussion around Discourse AI features and capabilities. Key topics included:
Improving the UX around enabling AI image captioning, with suggestions for an āask me laterā option
Issues with the automatic AI image captioning setting not being saved properly
The āshare conversationā button in AI conversations not respecting subfolder setups
Verbose tool calling output with the new Claude 3 Opus model
How to upload files to AI personas via the API
Adding support for other AWS Bedrock LLM providers beyond Anthropic
Ability to hide persona tool actions in specific categories
Deleting files uploaded to AI personas
Allowing AI bots access to private categories
Connecting self-hosted LLMs as chat bots
Improving search filter quality in Discourse AI
Images generated via Discourse AI not showing in chat
Assigning specific LLMs to be available per AI persona
Interesting Topics
ganncamp suggested adding an āask me laterā option when prompting users to enable automatic AI image captioning, to avoid forcing an immediate decision. This sparked discussion on the best UX for this new feature.
aas asked for help improving search filter quality in Discourse AI to search both the forum and uploaded files. sam provided an example of the ideal search query format.
Falco was active in discussing the UX around AI image captioning settings, and reproducing a bug with the share conversation button not respecting subfolders. He also commented on the work to support any OpenAI-compatible LLM API in Discourse AI.
philip-ellis-sp was investigating Discourse AI capabilities, figuring out persona file uploads via API, asking about using other AWS Bedrock LLMs, and inquiring about deleting uploaded persona files.
sp-jordan-violetreported a bug with the AI conversation share button and subfolders, and requested the ability to assign available LLMs on a per-persona basis.
37Rb suggested adding full markdown support in chat, especially for AI-generated messages that may contain markdown headers. Jagster noted this would be helpful for their users who primarily use AI in chats.
In the Post Illustrations topic, dsims asked about generating images with only a StableDiffusion key, and NateDhaliwal inquired if the feature is available on mobile.
This week on the meta.discourse.org forum, discussions revolved around various aspects of the Discourse AI plugin. Users explored the capabilities of the āReadā tool, shared insights on troubleshooting issues, and discussed potential improvements to the AI integration. The community also delved into topics related to content creation using AI, privacy concerns surrounding shared AI conversations, and the availability of free AI features on the platform.
Interesting Topics
Discourse AI - Personas: Users discussed the functionality of the āReadā tool within the Discourse AI plugin, which allows the language model to read and comprehend topics and posts on the forum. There was also a mention of a bug related to mentions on posts being currently broken.
AI helper is hiding: A user reported an issue where the AI helper icon was visible but not functioning correctly. The community provided suggestions and troubleshooting steps, leading to a potential solution involving shifting the AI button to the composer toolbar in an upcoming update.
Shared AI conversations: bots and how to delete: The discussion centered around the privacy implications of shared AI conversations and whether search engines like Google can index public links. @sam clarified that indexing is explicitly disallowed for shared public links and provided guidance on deleting and unsharing conversations.
AI doesnāt respond when mentioned in reply to a post: @Jagster reported an issue where the AI persona did not respond when mentioned in a reply to a post, although it worked when replying to a topic. The community discussed potential causes and workarounds.
In private chats AI uses threads: @Jagster raised a concern about the AI persona using threads in private chats, which some users found confusing. @sam acknowledged the issue and suggested the possibility of introducing a configuration option to disable threads in private chats.
What Discourse AI features are FREE to use?: Users discussed the availability of free AI features on the Discourse platform, with @sam clarifying that Discourse hosted plans include the related topics feature powered by AI embeddings. Self-hosters were also directed to providers like Cloudflare, which offer a free tier for AI usage.
Certainly! Iād be happy to help you randomly select one of the active participants from the weekly AI activity summary. Letās use the random picker to choose one person from the list of active participants mentioned in your summary.
Wow, what an exciting summary of AI activity on meta.discourse.org! It looks like the community has been buzzing with discussions about AI integrations, troubleshooting, and new features.
Now, letās add a fun twist to this recap. Iāve used the random picker to select our āAI Enthusiast of the Week,ā and the lucky winner isā¦
Congratulations, @JammyDodger! Youāve been randomly selected as our AI Enthusiast of the Week for your helpful contributions, particularly in providing suggestions and troubleshooting steps for the AI helper visibility issue. Your problem-solving skills are as sweet as your namesake!
Remember, folks, this is just a bit of fun to celebrate everyoneās engagement. Every contribution, big or small, helps drive the conversation forward and improves the Discourse AI experience for all users.
Keep those AI discussions coming, and who knows? You might be our next randomly picked AI Enthusiast of the Week! Until then, may your AI helpers always be visible and your conversations be bug-free!
This weekās discussions on meta.discourse.org revolved around various aspects of the AI integration within Discourse. Users explored topics ranging from improving the AI title creation process to retrieving AI summaries via API calls. Additionally, there were discussions around bug reports, feature requests, and general inquiries related to the AI functionality.
Interesting Topics
@Jagster suggested improving AI title creation by using sentence case instead of capitalizing every word, which can look awkward and go against grammar rules.
@Jagster raised a concern about the similarity between the ācopy AI conversationā and āshare AI conversationā buttons, which could lead to confusion.
Multiple users, including @Jagster, @JammyDodger, and @Moin, reported an issue where the AI helper icon was not functioning correctly, either not opening or displaying blank modals.
@Jagster shared an observation that automatic titles in private messages with AI personas are now in the correct language, appreciating the psychological value of this improvement.
@MachineScholar reported a bug related to mentioning AI personas in posts, which @ted provided a potential fix for.
@Jagster asked about shared AI conversations, specifically whether they are indexed by search engines and how to delete them if the original private message conversation is deleted. @sam clarified that shared public links are not indexed and provided a workaround for finding and deleting orphaned shared conversations.
@Jagster reported an issue where the AI persona does not respond when mentioned in a reply to a post, as opposed to a reply to a topic.
@Jagster raised a concern about the AI persona using threads in private chats, which can be confusing for users who dislike threading in chat conversations. @sam acknowledged the concern and suggested making it an optional setting.
@Boulaajaj shared their workflow for using OpenAIās ChatGPT 4o mini with Discourse AIās LLM and Embedding features, and inquired about the availability of new AI features that could support prompt customization and automated feedback to users.
@pfaffman provided guidance on using the API to retrieve data displayed in the user interface.
@sam provided detailed instructions on retrieving AI summaries via the API, including the endpoint URL and necessary parameters.
@MachineScholar reported a bug related to mentioning AI personas in posts and provided a potential workaround.
@ted offered a potential fix for the āundefined method `scheduled?ā for nilā error.
@Boulaajaj shared their workflow for using OpenAIās ChatGPT 4o mini with Discourse AIās LLM and Embedding features and inquired about upcoming AI features.
Thanks for reading, and Iāll see you again next week!
This weekās discussions on meta.discourse.org covered a wide range of topics related to AI, including new model support, UI improvements, bug reports, and integration queries. The community explored the potential of OpenAIās latest models, o1-preview and o1-mini, and discussed their cost-effectiveness and compatibility with Discourse. Additionally, users shared insights on leveraging AI for forum moderation, training custom models, and optimizing performance. Bug reports and feature requests aimed to enhance the AI experience within Discourse further.
Overgrow explored the potential of using the AI post classifier with the post approval queue, suggesting automated approval or rejection based on the classifierās output.
Users reported an issue with the AI helper not displaying correctly on certain devices, prompting sam to confirm ongoing work to resolve the edge case.
tpetrov raised a question about the āMax Context Postsā setting for the AI bot, leading to a discussion on its intended behavior and potential improvements.
whitewaterdeu sought guidance on granting access to AI-related topics for regular users, leading to a clarification on the distinction between related and suggested topics.
Overgrow reported an issue with the sentiment analysis feature failing on unusually long posts, leading to a discussion on potential solutions and configuration options.
Activity
pfaffman shared their experience using the AI helper to add a watermark to the background via CSS, showcasing its versatility in theme customization.
MarcP inquired about supporting OpenAIās new models, o1-preview and o1-mini, and their potential cost-effectiveness.
Moin raised a question about a Windows shortcut for the AI proofreading feature, leading to a pull request to address the issue.
Overgrow explored the potential of using the AI post classifier with the post approval queue and reported an issue with the sentiment analysis feature failing on long posts.
sam confirmed ongoing work to resolve an edge case where the AI helper was not displaying correctly on certain devices.
