人工智能主题的每周总结

网站反馈 论坛摘要
48

概述

本周 meta.discourse.org 上的讨论围绕着探索新的人工智能模型、配置人工智能驱动的垃圾邮件检测、管理人工智能角色和提示以及利用语义搜索功能展开。用户分享了他们使用各种语言模型的经验，讨论了潜在的改进，并寻求有关优化 Discourse 平台内人工智能功能的指导。

有趣的话题

活动

感谢阅读，下周再见！:slight_smile:

49

概述

本周在 Discourse 元论坛上，讨论主要围绕人工智能垃圾邮件检测功能、提议的“已解决问题查找器”工具、人工智能摘要问题以及与人工智能功能相关的各种错误报告和反馈。用户分享了见解、报告了错误并提出了改进建议，营造了一个协作环境，以增强人工智能在 Discourse 平台内的集成。

有趣的话题

活动

感谢您的阅读，下周再见！:slight_smile:

50

概述

上周在 meta.discourse.org 上，围绕 Discourse 的 AI 功能展开了各种讨论，用户分享了他们的经验、提供了反馈并寻求支持。社区探讨了 Discord 和 Discourse 的集成、AI 驱动的问答机器人潜力以及 AI 驱动的垃圾邮件检测功能。此外，还围绕 Helper 中的新智能日期功能、AI Persona Editor 以及 Standard 和 Business 套餐的 AI 功能可用性展开了讨论。

热门话题

活动

感谢您的阅读，下周再见！:slight_smile:

51

meta.discourse.org 每周 AI 摘要

概述

本周在 meta.discourse.org 论坛上，讨论围绕 Discourse AI 插件的各个方面展开，包括新功能、改进和用户查询。AI 驱动的垃圾邮件检测工具引起了关注，用户正在寻求关于其配置和使用的澄清。此外，还推出了“Ask Discourse”功能，允许用户与 AI 角色互动以获取文档帮助。其他主题包括可排序的情感表、使用 AI 处理详细内容、重新生成主题摘要以及管理 AI 使用配额。

有趣的话题

活动

感谢您的阅读，下周再见！:slight_smile:

2 个赞
52

Weekly AI Summary on meta.discourse.org

Overview

This week on the meta.discourse.org forum, discussions revolved around various AI-related topics, including a proposed moderation tool for formatting code using AI, the ongoing development of Discourse AI features, issues with AI summarization backfills, and the potential for uploading and discussing PDFs within the composer. Additionally, there were conversations about setting usage limits for AI, evaluating costs between different AI providers, handling AI-generated spam, and exploring the capabilities of AI bots and custom tools.

Interesting Topics

  • @merefield raised an idea for a moderation tool that would allow trusted users to format code blocks using AI, potentially improving readability and assisting new users who struggle with proper code formatting.

  • Discussions continued on the Discourse AI plugin, with @sam expressing interest in allowing users to upload large files and ask questions about the content using a persona-based approach.

  • @markschmucker encountered an issue where the AI summarization backfill process kept regenerating summaries for the same topic, even after a valid summary was already present. This led to a fix by @Roman to make the job more resilient.

  • @BrianC proposed a feature request to allow users to upload PDFs or text files directly in the composer and have the AI process and respond to questions about the content.

  • There was a discussion around setting per-group token and usage limits for AI features, with @sam clarifying that quotas are defined per group and applied per user, rather than being shared among users.

  • @oppman sought advice on evaluating the costs of using HuggingFace TGI versus OpenAI API endpoints for AI services, with @Falco providing insights on when running one’s own language model makes sense.

  • There was a bug report regarding posts and accounts not being restored when flags from Discourse AI spam detection were rejected, which @sam addressed with a fix.

  • Discussions took place around self-hosting embeddings for DiscourseAI, with @sam mentioning ongoing work to restructure the embedding configuration and plans to support multi-model embeddings.

  • @David_Ghost inquired about the ability of AI Triage to perform searches and avoid topics with similar titles based on creation dates.

  • @smithmarkl asked about the possibility of injecting custom prompts or manipulating embeddings in the AI Search feature to boost or separate staff responses from community responses.

Activity

Thanks for reading, and I’ll see you again next week! :slight_smile:

53

Weekly AI Activity Summary on meta.discourse.org

Overview

This week on meta.discourse.org, the Discourse team continued to enhance and refine the AI capabilities within the platform. Key discussions revolved around improving the AI summarization feature, managing costs through usage quotas, and integrating new language models. The community also explored potential use cases, such as formatting code with AI assistance and enabling document uploads for AI analysis.

Interesting Topics

  • Translate Discourse automatically (without a button) (ref)

    • The team provided updates on their progress towards enabling automatic translation of Discourse topics using AI models. While the initial target is to have the topic page translatable via a language toggle, challenges around search functionality and handling multilingual content remain.

  • LLM Quotas for Discourse AI (ref)

    • A new feature was released that allows administrators to define usage quotas for AI models, enabling better cost control and fair access to AI features across the community.

  • OpenAI’s text-embedding-ada-002 error “Embedding dimensions” (ref)

    • kuaza encountered an issue with OpenAI’s text-embedding-ada-002 model, which was resolved by Roman_Rizzi through a pull request.

  • Moderation tool for formatting code with AI (ref)

    • sam proposed the idea of allowing certain user groups access to an “AI Helper” feature for formatting source code in posts, acknowledging the potential performance trade-offs.

  • AI Plugin Causes All Posts to Be Unreadable in Latest Discourse Version (ref)

    • shannon1024 reported a critical bug where the AI plugin rendered all posts unreadable after updating to the latest Discourse version. The issue was related to the AI embeddings configuration and was resolved by disabling the relevant setting.

  • What LLM to use for Discourse AI? (ref)

    • Saif provided guidance on factors to consider when choosing a Large Language Model (LLM) for Discourse AI, including performance, context length, compatibility, language support, multimodal capabilities, and speed.

  • DeepSeek provider support? What to do when model provider isn’t in “Provider” list? (ref)

    • MachineScholar inquired about integrating the DeepSeek R1 model, which Falco provided a solution for by configuring it as an OpenAI model.

  • Discourse AI - AI usage (ref)

    • Saif introduced the AI usage page, designed to help administrators understand how the community is utilizing Discourse AI features over time, aiding in cost estimation and management.

  • AI helper is hiding. Again (ref)

    • Jagster reported an issue where the AI helper was not visible in certain contexts, which was subsequently fixed by pmusaraj.

Activity

Thanks for reading, and I’ll see you again next week! :slight_smile:

54

概述

本周，meta.discourse.org 上的讨论集中在与人工智能相关的问题、功能和集成上。主要议题包括调试 AI 聊天、配置 AI 垃圾邮件检测、使用 DeepSeek-R1 等推理模型以及探索 AI Helper 插件的功能。用户分享了关于成本比较、性能评估以及各种语言模型的潜在用例的见解。

有趣的话题

  • @dsims 在 AI Helper 的帖子插图功能上遇到了一个问题，这引发了关于更新所需设置的讨论。[ref](AI-Helper post illustration error. ai_openai_api_key missing)

  • @oppman 寻求关于将 AI 与外部网站和 GitHub 存储库集成的指导，以用于软件开发社区。[ref](AI Integration with Specific External Sites and GitHub)

  • 用户讨论了 DeepSeek-R1 推理模型与 GPT-4 和 Claude 等其他语言模型相比的成本和性能。[ref](DeepSeek provider support? What to do when model provider isn’t in “Provider” list?)

  • @MachineScholar 报告在使用 AI Bot 与 DeepSeek-R1 模型交互时出现随机错误。[ref](DeepSeek-R1 randomly producing “Job exception: undefined method `finish’ for nil” error)

  • @Don 询问关于在 AI 回复中增加最大连续工具使用次数，这引发了关于潜在解决方案的讨论。[ref](Max consecutive tool usage in the answer)

  • @Eric_Platzek 寻求关于调试 AI 聊天的帮助，并澄清了不同语言模型的使用和相关成本。[ref](Debugging AI chat)

  • @markschmucker 分享了他们使用 AI Web Artifacts 功能的经验，并询问了关于编辑生成的代码和使用现有工件开始新上下文的问题。[ref](Announcing: AI Web Artifacts)

  • @NKERIFAC_CLAUD_NBAPNON 在更新后遇到了 Discourse AI 嵌入配置的一个问题，这引发了关于故障排除和配置步骤的讨论。[ref](Problems with Discouse AI embeddings configuration)

活动

  • @sam 提供了关于使用 Data Explorer 导出论坛帖子以手动上传到外部语言模型的见解。[ref](Exporting all Forum Posts for Manual Upload into External LLMs?)

  • @Roman_Rizzi 分享了关于解决 AI 插件导致最新 Discourse 版本中帖子无法阅读的问题的更新。[ref](AI Plugin Causes All Posts to Be Unreadable in Latest Discourse Version)

  • @BrianC 询问了关于在 AI 角色中管理上传的文本文件以及编辑索引内容的可能性。[ref](Discourse AI Persona, upload support)

  • @Saif 澄清了AI 垃圾邮件检测和 AI 分类之间的区别，并就标记单个帖子与整个主题提供了指导。[ref](Setting up spam detection in your community)

  • @per1234 报告了一个问题，即当 Discourse AI 垃圾邮件检测的标记被拒绝时，帖子和账户并非总是被恢复，这引发了关于潜在解决方案的讨论。[ref](Posts and account not always restored when flag from Discourse AI spam detection rejected)

  • @dsims 建议为 Dall-E 3 图像生成功能添加一个质量参数，以降低成本。[ref](Image sizes of Dall-E 3?)

  • @bugtracker 询问了关于在 Discourse AI 插件中使用 DeepSeek的问题。[ref](Discourse AI)

  • @StefanoCecere 分享了一个关于使用 AI Helper 生成日期时包含星期几的建议。[ref](Write out smarter dates with AI)

  • @BrianC 对在 composer 功能中上传和讨论 PDF表示了兴趣。[ref](Upload and discuss pdfs in composer)

感谢阅读，下周再见！:slight_smile:

55

Overview

Over the past week (2025-02-03 to 2025-02-10), AI discussions on meta.discourse.org have been both vibrant and diverse. Active debates ranged from fine-tuning the AI helper’s ability to distinguish between Discourse and Discord to exploring innovative ways to pass data to artifacts and chain multiple AI triage scripts. Users focused on enhancing features (as seen in discussions like AI helper does not know the difference between Discourse and Discord and post by sam in Support and ai) while also addressing bugs and configuration issues in sentiment analysis and semantic search. In-depth posts covering topics such as flexible artifact embedding (How do I pass data to an artifact? through post 7) and automated AI workflows (AI + Automation Governance: Orchestrating Independent AI Triage Scripts to post 8) demonstrated the community’s commitment to practical innovation. Meanwhile, bug reports such as issues with sentiment displays and semantic search anomalies were met with proactive troubleshooting by experienced users. These discussions, backed by numerous posts and detailed responses, highlight a week of forward-thinking ideas balanced by diligent debugging.

Interesting Topics

Activity

User Contributions Across Topics

Thanks for reading, and I’ll see you again next week! :slight_smile:

56

Overview

This week on meta.discourse.org the AI community engaged in in‐depth technical discussions and experiments with several new and evolving features. Contributors debated the feasibility of extending RAG to support diverse PDF formats—highlighting nuances in text extraction and OCR reliability (ref, ref)—and launched an intriguing one‐click experiment for AI summarization with mixed impressions (ref, ref). There were spirited conversations around ChatGPT’s role in forum assistance (ref, ref), together with detailed troubleshooting sessions for semantic search issues that consistently returned irrelevant results (ref, ref). Additional topics—including problems with rake tasks in the AI plugin (ref, ref), automation governance experiments (ref, ref), and fixes for persona tool JSON errors (ref, ref)—kept the forum buzzing with ideas and actionable fixes. Throughout these discussions, top contributors like sam, Yenwod, Jagster, Saif and many others drove the conversation forward by sharing clear troubleshooting steps, potential feature improvements, and critical reflections on AI integration in forum functionalities.

Interesting Topics

  • Will RAG Support PDF Files in the Future?
    Users debated the challenges of supporting all types of PDFs in RAG workflows. MachineScholar sparked the discussion with a comment praising the commit (ref), while Saif explained the intricacies of handling text versus image PDFs (ref). Subsequent troubleshooting steps were detailed by Yenwod when he encountered indexing delays (ref) and further debugging was shared (ref, ref, ref).

  • New Experiment: Enable AI Summarize on your Discourse with one-click!
    In this experiment, users evaluated a one-click activation for summarizations. shooj raised an initial query about limiting the feature to admins or mods (ref), and Jagster argued over its universal benefits (ref). Contributions by Arkshine provided CSS-based workarounds (ref), while additional observations by Jagster and Carverofchocie sparked extra debate (ref, ref, ref, ref).

  • How are we all feeling about ChatGPT and other LLMs and how they’ll impact forums?
    The conversation here balanced optimism with caution. Tris20 offered insights on repetitive answers by LLMs in forum settings (ref), while Saif looked at future directions for LLM assistance in topic formulation (ref).

  • Getting a lot of no results for semantic search
    A technical debate emerged when users reported that AI search always returned roughly 40 results regardless of query relevance. sam began the discussion (ref), and tyler.lamparter shared his observations (ref, ref). Further elaboration on model behaviors and result uniformity was provided by sam and Falco (ref, ref, ref, ref).

  • Rake tasks in the AI plugin not working
    A practical issue was raised by Yenwod regarding failures in AI rake tasks, especially with ruby-progressbar related errors (ref). His follow-up post provided more context (ref), while sam and Yenwod further discussed potential remedies (ref, ref).

  • AI + Automation Governance: Orchestrating Independent AI Triage Scripts
    This thread explored automating workflows for AI triage. Cloud_spanner shared a detailed workflow proposal (ref), with sam suggesting a custom tool for triage automation (ref), and Cloud_spanner reinforcing the benefits of a flexible IFTTT-style approach (ref).

  • AI Persona using Categories tool – “An empty string is not a valid JSON string”
    An error in using the Categories tool left users troubleshooting persona failures. markschmucker consistently encountered the JSON error (ref), while sam confirmed the bug and soon provided a fix (ref, ref).

  • All AI functions are working ok, but AI search gives 500 error
    A disruptive 500 error in AI search caught attention on this thread. Bathinda reported the initial error (ref) and subsequent status updates (ref, ref). Jagster guided users through troubleshooting with actionable solutions (ref, ref, ref).

  • Discourse AI – Spam detection
    Focusing on content quality, this topic examined AI’s capacity for spam detection. jordan-violet shared initial testing scenarios (ref, ref), while Jagster critiqued the logical phrasing in the detection rules and offered clearer alternatives (ref, ref, ref, ref).

  • How to properly debug AI Personas?
    A brief yet vital discussion focused on debugging AI personas where Falco inquired about the LLM/provider specifics (ref), and Overgrow responded with the details of his OpenAI setup (ref).

Activity

Thanks for reading, and I’ll see you again next week! :slight_smile:

57

Overview

This week on meta.discourse.org (Feb 17–Feb 24, 2025) the AI category has been buzzing with troubleshooting, experimentation, and feature enhancements. Users such as sam, Falco, hendersj, and others have been busy addressing critical bugs, testing integrations with local AI models like Ollama, and exploring new capabilities around PDF processing, search, and API interactions. For example, a serious page display bug raised by shannon1024 quickly attracted responses from Arkshine and sam, while robust troubleshooting in Getting discourse ai to work with ollama locally has yielded progress despite SSRF and streaming configuration challenges. Constant activity in threads discussing the performance of our AI forum helper, hosted model cost clarifications, and even Google Search API integration tests underscores a community deeply invested in making Discourse AI even better. Read on for a more detailed breakdown of the interesting topics and user activities from the past week.

Interesting Topics

Activity

Thanks for reading, and I’ll see you again next week! :slight_smile:

58

Overview
This week on meta.discourse.org the community’s AI activity has been energetic and multifaceted. Discussions have spanned innovative feature requests and detailed technical troubleshooting. A central theme has been the need to intelligently automate responses – as introduced in the Auto responder using AI discussion by Saif – with follow‐up examples from EricGT (post 2) and creative suggestions by hel_Sinki (post 3). Simultaneously, practical challenges such as enabling PDF support for AI analysis were examined in PDF support in Discourse AI with details by hameedacpa (post 7) and clarifications from sam (post 8). Meanwhile, integration issues with Claude 3.7 were dissected in the Error using Claude 3.7 Sonnet with Discourse AI plugin thread—fueling technical troubleshooting by emansilla (post 1) and iterative fixes by Falco (post 2). Other threads on LLM settings, experimental search results, and connection resets further enriched the dialogue. Collectively, these discussions underline the community’s commitment to exploring dynamic AI integrations that not only automate tasks but also enhance user experience across Discourse’s features.

Interesting Topics

  • Auto responder using AI (Feature, automation, ai)
    • Initiated by Saif (post 1), the idea of deploying an AI-driven auto-responder sparked follow-up queries by EricGT (post 2) and practical examples by Jagster (post 4) as well as use-case suggestions from MachineScholar (post 5).
  • PDF support in Discourse AI (#SiteManagement, how-to, ai)
    • Discussions centered on testing PDF upload and analysis were led by hameedacpa (post 7) with clarifications and follow-ups by sam (post 8 and post 10), while Falco provided configuration insights (post 12).
  • Error using Claude 3.7 Sonnet with Discourse AI plugin (Bug, ai, ai-bot)
    • Technical hurdles emerged when emansilla reported integration errors (post 1), provoking responses and troubleshooting steps from Falco (posts 2, post 4, and post 6).
  • Discourse AI - AI bot (#SiteManagement, ai-bot)
    • A demonstration by MarkDoerr (post 150) highlighted use cases that drive the AI bot’s interactions.
  • Discourse AI causing new SSL and Connection Reset by Peer errors (Bug, ai)
    • Issues with SSL and connectivity were investigated by oznyet (post 7 and post 9) with remedial updates from sam (posts 8 and 10).
  • Question about release note for experimental search results (General, ai)
    • sam explained fine-tuning efforts (post 3), while Jagster shared community concerns (post 4).
  • Discourse AI - Large Language Model (LLM) settings page (#SiteManagement, how-to, ai)
    • sam reminded users of supported configurations via the LLM settings (post 5).
  • How do you use Discourse AI? Tell us and make it even better! (Feature, feedback, ai)
    • A feedback thread encouraged sharing of use cases, with contributions from Bhack (post 22 and post 24) and an insightful comment by Saif (post 23).
  • What LLM to use for Discourse AI? (#SiteManagement, how-to, ai)
    • In response to user queries, Saif confirmed support for new models (post 5).
  • Error in any AI Tool with no parameters, e.g. “tags” (Bug, ai)
    • sam detailed an error scenario associated with tool parameters (post 6).

Activity

Thanks for reading, and I’ll see you again next week! :slight_smile:

59

Overview

Over the past week (March 10–17, 2025), the meta.discourse.org community has engaged in vibrant discussions around enhancing AI features across the forum. Developers and users alike explored enhancements to search functionality—for example, suggestions to improve user interaction in the Conversational AI Search coming to Discourse AI thread—while also debating the ethics and best practices of automated content creation in Rules Surrounding Writing Topics using AI. Other conversations centered on UI improvements such as displaying a live processing indicator in Provide visual cue when a topic is receiving an AI response, and practical customization queries like safely rebranding the AI spam detection account in Rebranding the ai spam detection account. Technical deep-dives emerged in areas such as configuring large language models in the Discourse AI - Large Language Model (LLM) settings page thread, and automating content classification in Using AI To Tag And Categorize Forum Posts. Troubleshooting challenges—ranging from imprecise semantic search results as discussed in Getting a lot of no results for semantic search to intermittent response failures highlighted in Why does the AI model stop responding—further underscored the community’s commitment to refining its AI systems. In addition, creative applications such as the Gemini ai bot to draw picture in chat and broad plugin transition implications in Discourse AI spam detection replaces Akismet plugin round out a week full of insightful, multi-dimensional AI activity.

Interesting Topics

Activity

Thanks for reading, and I’ll see you again next week! :slight_smile:

60

Overview

This week on Meta Discourse, the community dove deep into innovations at the intersection of AI and forum management. Members explored experimental implementations such as sam's work on Experiments with AI based moderation on Discourse Meta – where discussions ranged from leveraging Gemini Flash 2.0 (post #7) to addressing false positives (post #3). At the same time, the conversation around new interaction modalities was vibrant, with topics like Is there a way to chat with Discobot? generating feedback from trusktr, tobiaseigen, and Canapin – even prompting interface tweaks such as the redirection fix by Lilly (post #10).

Cost and performance debates were front and center in What’s the cheapest/best AI to use for AI Spam? where users like trusktr, ondrej, and thoka compared models – with NateDhaliwal sharing insights from OpenRouter’s Gemini approach (post #4). On the UI and feature front, members discussed vital accessibility enhancements in What’s the best way to add image descriptions? and smoother interaction via the Setting to manually close AI Helper’s popup modal. Innovative ideas such as enriching API calls in enterprise settings (Enrich API Calls of AI Plugin?) and improvements in AI search functionality (Conversational AI Search coming to Discourse AI) further fueled the debate. This week’s activity also reflected a growing interest in troubleshooting and refining AI personas – as seen in How to properly debug AI Personas? – and led the community to explore new notification possibilities, like sending automation summaries to groups (Ability to send Automation AI summaries to groups). Overall, from experimental moderation strategies (post #1) to enterprise API enrichment (post #1), the dialogue has been rich, diverse, and full of actionable insights.

Interesting Topics

  • Experiments with AI based moderation on Discourse Meta
    Discussions highlighted the promising evolution of AI for moderation, detailing experiments with Gemini Flash 2.0 (post #7) and updates ensuring that only public posts are scanned (post #6).

  • Is there a way to chat with Discobot?
    Users explored the idea of interacting with Discobot in a chat format, with suggestions to use ask.discourse.com (post #3) and commentary on domain redirects (post #9).

  • What’s the cheapest/best AI to use for AI Spam?
    The community weighed cost against performance by comparing models like GPT-4o-mini, Claude 3.5 Haiku, and Gemini 2.0 Flash – with hands-on recommendations from users such as trusktr (post #1) and NateDhaliwal (post #4).

  • FYI: Cloudflare AI Labyrinth
    An insightful share on Cloudflare’s strategy to trap misbehaving bots using AI-generated mazes sparked curious reactions and humorous takes (post #1, post #3).

  • Hide persona from composer dropdown
    A user-friendly debate was held on how to prevent personas from cluttering the composer dropdown, with suggestions for a dedicated “Hide from composer” option (post #1, post #3).

  • What’s the best way to add image descriptions?
    Accessibility improvements were discussed with reference to current markdown capabilities and potential UI enhancements for image ALT text (post #17, post #19).

  • Setting to manually close AI Helper’s popup modal
    With feedback about the finicky nature of the AI Helper modal, a feature request emerged to add a manual close option for enhanced usability (post #1).

  • Conversational AI Search coming to Discourse AI
    Users provided feedback on the new search summary interface, discussing minor UI glitches like missable “More…” text and unexpected closures (post #10).

  • How to properly debug AI Personas?
    Troubleshooting steps and questions about debugging inconsistent AI persona responses spurred a helpful discussion among experienced users (post #4).

  • Enrich API Calls of AI Plugin?
    An enterprise user raised ideas on enriching outgoing API requests with proper authentication headers, opening a conversation on integrating internal auth endpoints with custom tooling (post #1).

Activity

Thanks for reading, and I’ll see you again next week! :slight_smile:

61

Overview

This week on meta.discourse.org the community passionately discussed several AI topics, driving the conversation forward on configuration issues, user experience, and new feature experiments. Members collaborated on troubleshooting critical bugs in AI tools—ranging from errors when creating new AI personas to refining popup modal behaviors—while also sharing insights about LLM settings, sentiment analysis, image captioning, embeddings, and even experiments in AI moderation. These discussions, spread across multiple topics such as Unable to create new Personas (post 1), Setting to manually close AI Helper’s popup modal (post 3), LLM settings page (post 10) and Discourse AI - Sentiment (post 41), underscore the shared passion and technical know‐how applied by our members. The blend of bug reports, configuration tweaks, and creative ideas has paved the way for improvements to our AI functionality—ensuring that both self-hosted and managed services continue to run smoothly. For instance, fixes announced by joffreyjaffeux in Unable to create new Personas (post 6) and keegan in Setting to manually close AI Helper’s popup modal (post 3) highlight our concerted effort toward continuous improvement. Below is a detailed roundup of the most interesting topics and user activities from the past 7 days.

Interesting Topics

  • Unable to create new Personas (Bug, ai, ai-bot)
    MachineScholar kicked off this discussion by reporting an error on attempting to create new AI personas (post 1). sam joined with troubleshooting suggestions (post 2 and post 4), while further investigation by MachineScholar confirmed the issue (post 3). Later, joffreyjaffeux provided a fix by referencing the upcoming patch (post 6) and MachineScholar confirmed resolution (post 7).

  • Setting to manually close AI Helper’s popup modal (Bug, ai, ai-helper)
    When users expressed the need for more control over AI Helper’s popup modal, keegan swiftly responded by moving the request to Bug and subsequently pushed out a fix (post 3). MachineScholar later confirmed that the issue was resolved (post 5).

  • Discourse AI - Large Language Model (LLM) settings page (#SiteManagement, how-to, ai)
    In this thread, AquaL1te shared their experience with setting up the LLM settings page, noting a quirk with the default model name (post 10 and post 12). Saif contributed by asking for clarifications regarding model identifier discrepancies (post 11 and post 13).

  • Discourse AI - Sentiment (#SiteManagement, how-to, ai-sentiment, content)
    This topic saw RBoy raise concerns about the cessation of the sentiment process since January 2025, prompting discussions regarding configuration changes (post 41). Falco responded with an explanation about the changes in sentiment server deployments (post 42).

  • Experiments with AI based moderation on Discourse Meta (Community, moderation, ai)
    Creative ideas were floated by RGJ, who proposed that an AI moderation bot could intermittently signal that a post required no action—injecting an element of transparency into automated moderation (post 10).

  • A setting for AI-enabled image title default value (Support, ai)
    fbpbdmin started this discussion by suggesting that AI-enabled image titles should be off by default in order to save tokens (post 1 and post 4). keegan provided configuration guidance on the available settings (post 3).

  • Self-Hosting Sentiment and Emotion for DiscourseAI (#Self-Hosting, ai, ai-sentiment)
    In a discussion aimed at self-hosters, RBoy raised important questions about running local instances for sentiment analysis, seeking advice on resource requirements and integration techniques (post 4).

  • Discourse AI - Embeddings (#SiteManagement, ai, ai-search, related-topics)
    Lastly, Saif prompted an update in the embeddings discussion to ensure that the feature stays aligned with the platform’s evolving needs (post 37).

Activity

Additional references from the discussions include multiple insights and confirmations across posts such as post 2 of Unable to create new Personas, post 4 of Unable to create new Personas, post 12 of LLM settings page, post 13 of LLM settings page, post 41 of Sentiment, and post 37 of Embeddings among others. Each contribution has helped build a rich tapestry of discourse with over 40 discussion links embedded across topics, showcasing the depth and collaborative effort of our community.

Thanks for reading, and I’ll see you again next week! :slight_smile:

62

Overview

This week on meta.discourse.org the AI discussion threads have been buzzing with innovative ideas and practical troubleshooting. Community members explored everything from fresh feature proposals to intricate technical issues. For example, the AI Avatar Generator thread saw tpetrov kick off a discussion with ideas for generating personalized avatars (tpetrov post 1, sam post 2, tpetrov post 3), while the lively Ways to Add Knowledge to My Persona discussion featured a deep dive into enabling search and read tools for AI support personas – with contributions from Angela_MRS, Falco, and pfaffman (Angela_MRS post 1, Falco post 2, Angela_MRS post 3, Falco post 4, Angela_MRS post 5, Falco post 6, Angela_MRS post 7, Angela_MRS post 8, pfaffman post 9, plus an extra insight about private categories (Allow Bot on Private Categories)) – ensuring that even “backstage” AI teaching ideas were on the table. Other hot topics included improvements to AI‐based moderation (sam post 11) and extensive discussions on the customization and troubleshooting of the Discourse AI Bot (jorge-gbs post 152 through EricGT post 158). Meanwhile, threads on automation—such as the ability to send AI summaries to groups (sam post 2, jordan-violet post 3)—and resource management via daily AI token limits (sam post 13) highlighted both the potential and the challenges of integrating AI in community workflows. Finally, troubleshooting posts like those on the Invalid Request Error in Google Flash (BrianC post 1 through sam post 7) and API enhancements in the combined discussion on enriching API calls and Google Search integration (sam post 3 in 357898, jorge-gbs post 11 in 307107, sam post 12 in 307107) underscore the collaborative drive to refine Discourse’s AI capabilities.

Interesting Topics

Activity

Thanks for reading, and I’ll see you again next week! :slight_smile:

63

Weekly Summary of AI Activity on Meta.discourse.org

Below is a detailed overview of this week’s vibrant discussions and developments around Discourse’s AI features and integrations from 2025-04-07 to 2025-04-14.

Overview

This week saw a flurry of activity around leveraging and refining AI capabilities on Meta. Discussions ranged from concerns over personal data and privacy when using the AI plugin to technical deep-dives into embedding models, API call enrichments, and troubleshooting internal server errors. Privacy and configuration details took center stage as wotography initiated the discussion on Concerns over personal privacy with the AI plugin – a thread that quickly sparked detailed responses from Falco (post 3, post 6, post 8) and clarifications by sam (post 9, post 10). Further, technical queries such as How to implement Mistral with Embeddings drew contributions from RGJ (post 1, post 3) and insightful remarks by Falco (post 2, post 4). Meanwhile, innovative experiments were shared on enhancing the user experience with features like the Expanded with AI Summaries option and Conversational AI Search, as well as advanced inquiries into Enriching API Calls. Troubleshooting themes also emerged in topics such as Discourse AI Internal Server Error and Discourse AI - Semantic Search & Summarization Not Working for our configuration, ensuring that technical issues are rapidly addressed. These discussions underscore a community committed to both innovation and rigorous technical support in the ai, privacy, Support, and rest-api spaces.

“If you both don’t trust any third party LLMs and can’t run your own, I recommend simply not integrating them.” – Falco
ref

Interesting Topics

Activity

Each contribution – from detailed technical analysis to thoughtful user inquiries – has been crucial in shaping the future roadmap of Discourse AI integrations. Community members have built on each other’s ideas by referring to earlier posts like this privacy note or the troubleshooting tip, ensuring a robust and collaborative dialogue.

Thanks for reading, and I’ll see you again next week! :slight_smile:

64

Overview

This week on meta.discourse.org, the AI discussions have been vibrant and multifaceted. Contributors explored how to harness AI/LLMs in building custom themes, components, and plugins in the Dev space – sparking debates on the pros and cons of using tools like Cursor and Claude Code (jimkleiber’s insight, Falco’s experiment, Dimava’s challenges, awesomerobot’s tip). Equally engaging was the proposal for a dedicated page to filter or list AI conversations in the Feature category (kuaza’s initial post, responded to by Jagster and others through posts 3, 4, 5, and 6). Other threads discussed practical issues like AI-driven spam detection in #SiteManagement (Olle11’s query, KhoiUSA’s suggestions, follow-ups and further tips), while the Support category saw an in-depth exploration of building modular AI chatbots with specialized personas (Yenwod’s proposal, Falco’s confirmation, additional clarifications, more insights, sam’s constructive inquiry, and a further note by Yenwod). Discussions also spanned technical configurations for self-hosted embeddings (satonotdead’s update, Falco’s follow-up), troubleshooting visible reasoning and image recognition challenges with Grok (hel_Sinki’s suggestion), addressing PDF upload and indexing errors (Michael_Liu’s detailed post and follow-up), and resolving issues with the AI helper’s generation process in the Bug space (MachineScholar’s report, Falco’s query, additional MachineScholar updates and further details along with keegan’s follow-up). Finally, a fresh discussion on innovative prompt evaluation tools – funnel, orbit, and flux charts – was raised in the Feature arena by EricGT (post). These rich interactions underscore the community’s commitment to refining AI integration and addressing practical challenges.

Interesting Topics

  • How are you using AI/LLMs to create themes/components/plugins?
    In the Dev category with the ai tag, jimkleiber launched a discussion on leveraging AI for Discourse customizations (post 1). Falco soon shared his experience using Cursor in agent mode (post 2), while Dimava noted challenges with bug fixes (post 3). awesomerobot later added practical tips for dealing with modern Ember issues (post 4).

  • Listing conversations with artificial intelligence on a separate page or filtering them on the messages page
    In this Feature discussion tagged ai, kuaza proposed a dedicated page for AI conversations (post 1). The idea received active feedback from Jagster (post 2), with follow-up clarifications and questions further detailed in posts 3, 4, 5, and 6.

  • Discourse AI - Spam detection
    Within #SiteManagement and tagged with moderation, how-to, ai, and spam, users discussed replacing Akismet with an AI-based solution. Olle11 raised questions regarding cost-effective alternatives (post 10), while KhoiUSA recommended Gemini 2.0 Flash with follow-ups in posts 11, 12, and 13.

  • Building Modular AI Chatbots
    In the Support category with tags ai and ai-bot, a conversation unfolded about designing a modular AI chatbot system. Yenwod introduced the concept (post 1), followed by Falco affirming technical feasibility (post 3) and further elaborations from Yenwod (post 4, post 7). Additional insights were provided by Falco (post 5) and sam (post 6).

  • Self-Hosting Embeddings for DiscourseAI
    Under the #Self-Hosting category with tags ai, ai-search, and related-topics, discussions focused on endpoint configuration and backfill procedures. satonotdead reported having an endpoint to use for embeddings (post 21), and Falco clarified that Discourse now handles backfill automatically (post 22).

  • Need Support for Displaying Reasoning Process and Enabling Grok to Recognize Images
    In a Support thread tagged ai, hel_Sinki raised the need for Grok’s visible reasoning traces and improvements so that its image recognition capabilities can properly interact with posts (post 1).

  • PDF support in Discourse AI
    In the #SiteManagement category with tags how-to and ai, Michael_Liu reported issues with PDF uploading and indexing, highlighting error messages and questioning file size limits (post 14 and post 15).

  • AI Helper stuck generating
    A bug report in the Bug category tagged with ai and ai-helper detailed an instance where the AI helper remained stuck on “generating”. MachineScholar initiated the report (post 1), followed by responses from Falco (post 2), further updates from MachineScholar (posts 3 and 4), and a clarification by keegan (post 5).

  • Prompt tools: funnel, orbit, and flux charts
    In a fresh Feature discussion with the tags ai and sql-query, EricGT introduced innovative concepts for prompt evaluation. He outlined how tools like Funnel, Orbit, and Flux could provide deeper insights into prompt performance (post 1).

Activity

Thanks for reading, and I’ll see you again next week! :slight_smile:

65

每周人工智能活动摘要 (2025-04-21 至 2025-04-28)

概述

上周，社区深入探讨了增强 Discourse AI 的 功能、可用性 和 稳定性。在 Feature 板块，成员们探索了在 AI 工具栏中添加一键式“起草回复”操作 使用 AI 协助回复 Discourse 中的新帖子，并初步实现了在“消息”页面列出和过滤 AI 生成的对话 在单独的页面列出人工智能对话或在消息页面过滤它们。在 Support 讨论中，量化了 Persona 文件大小的成本与质量权衡 更多 Persona 文件会增加 LLM 请求费用吗？，同时优化了模块化机器人创作模式 构建模块化 AI 聊天机器人，并澄清了自定义 vs. 内置工具的可视性 我们可以查看 AI 中的所有工具及其设置吗？。在 UX 方面，一个简单的 CSS 调整修复了编辑器中的图标定位 类别助手 AI 图标位于 + 菜单上方，并且在增强验证 验证 AI 工具的名称字段 和解决了“生成卡住”问题 AI 助手生成卡住 后，众多 Bug 报告得到关闭。最终结果是一个更直观、性能更好、成本效益更高的生态系统。

热门话题

  • \u003ca class="mention" href="/u/wlandgraf"\u003ewlandgraf\u003c/a\u003e 倡导添加一个起草回复按钮，让版主可以按需调用 AI 生成的回复，并引发了通过 Persona 和 AI 工具栏连接该操作的建议 使用 AI 协助回复 Discourse 中的新帖子 (功能, ai)。

  • \u003ca class="mention" href="/u/isaac"\u003eisaac\u003c/a\u003e 宣布 discourse-ai 插件中已实现列出和过滤 AI 助手对话的功能，\u003ca class="mention" href="/u/kuaza"\u003ekuaza\u003c/a\u003e 在 在单独的页面列出人工智能对话或在消息页面过滤它们 中进行了预览并给予了赞扬 (功能, ai)。

  • \u003ca class="mention" href="/u/wlandgraf"\u003ewlandgraf\u003c/a\u003e 询问上传大量 Persona 文件是否会增加 LLM 成本，\u003ca class="mention" href="/u/Falco"\u003eFalco\u003c/a\u003e 解释了用于调整费用的“上传块令牌”ד搜索对话块”公式 更多 Persona 文件会增加 LLM 请求费用吗？ (支持, ai)。

  • \u003ca class="mention" href="/u/Yenwod"\u003eYenwod\u003c/a\u003e 和 \u003ca class="mention" href="/u/kuaza"\u003ekuaza\u003c/a\u003e 迭代了疫苗机器人系列的提示，而 \u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e 提出了一个自定义 JS 工具，用于仅加载上传中的相关子集 构建模块化 AI 聊天机器人 (支持, ai-bot)。

  • \u003ca class="mention" href="/u/Moin"\u003eMoin\u003c/a\u003e 发现 AI 图标遮挡了编辑器中的 + 菜单，\u003ca class="mention" href="/u/awesomerobot"\u003eawesomerobot\u003c/a\u003e 确认了与早期 UX 主题相同的修复方法 类别助手 AI 图标位于 + 菜单上方 (UX, ai-helper)。

  • \u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e 验证了工具名称字段现在强制执行验证，从而关闭了一个长期存在的错误 验证 AI 工具的名称字段 (Bug, ai)。

  • \u003ca class="mention" href="/u/wlandgraf"\u003ewlandgraf\u003c/a\u003e 请求了一个仪表板来检查所有 AI 工具的脚本和参数，\u003ca class="mention" href="/u/Falco"\u003eFalco\u003c/a\u003e 澄清了内置工具（Ruby）与自定义 JS 工具不同 我们可以查看 AI 中的所有工具及其设置吗？ (支持, ai)。

  • \u003ca class="mention" href="/u/keegan"\u003ekeegan\u003c/a\u003e 确定了编辑器 AI 助手的语言遵循 站点 区域设置，并在与 \u003ca class="mention" href="/u/MachineScholar"\u003eMachineScholar\u003c/a\u003e 进行 PM 调试后，核心+插件更新修复了菜单生成挂起问题 AI 助手生成卡住 (Bug, ai-helper)。

  • \u003ca class="mention" href="/u/Justin_Gonzalez"\u003eJustin_Gonzalez\u003c/a\u003e 询问通过 Glean 索引 Discourse 的问题，\u003ca class="mention" href="/u/Falco"\u003eFalco\u003c/a\u003e 建议使用爬虫用户代理或 Discourse AI 来显示隐藏内容 在 Glean AI 中索引 Discourse 社区内容 (支持, ai)。

  • \u003ca class="mention" href="/u/Jagster"\u003eJagster\u003c/a\u003e 报告了解释功能中普遍存在的幻觉问题，并就模型选择和提示调整提供了建议 AI 助手在解释某事时出现大量幻觉 (支持, ai-helper, ai-custom-prompt)。

活动

\u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e (14 个赞，15 篇帖子)
• 推动了“起草回复”功能讨论 363298/5?silent=true
• 确认了工具名称验证 330830/2?silent=true
• 为疫苗机器人流程提出了自定义工具 JS 361807/10?silent=true
• 分享了 GitHub 助手演示 363437/4?silent=true
• 分类并关闭了多个错误：
– 子文件夹链接 278007/3?silent=true
– 私信草稿移除 336927/7?silent=true
– 聊天机器人中断 318546/2?silent=true
– 创建用户错误 312281/6?silent=true
– 聊天 UI 标签页 285403/4?silent=true
– 选择时下拉菜单 305688/3?silent=true
– Gemini 支持 312280/6?silent=true
– 定期报告模型 293762/6?silent=true
– 作业异常修复 344935/3?silent=true

\u003ca class="mention" href="/u/Falco"\u003eFalco\u003c/a\u003e (9 个赞，4 篇帖子)
• 解释了 Persona 文件中的成本公式 363440/3?silent=true 和 363440/5?silent=true
• 澄清了工具可见性差异 363437/3?silent=true
• 就 Glean 索引方法提供了建议 363335/4?silent=true

\u003ca class="mention" href="/u/wlandgraf"\u003ewlandgraf\u003c/a\u003e (5 个赞，5 篇帖子)
• 请求了 AI“起草回复”按钮 363298/1?silent=true 和 363298/4?silent=true
• 质疑了 Persona 成本影响 363440/1?silent=true 和 363440/4?silent=true
• 请求了工具仪表板视图 363437/1?silent=true

\u003ca class="mention" href="/u/kuaza"\u003ekuaza\u003c/a\u003e (4 个赞，2 篇帖子)
• 庆祝了 AI 对话过滤功能的实现 362711/8?silent=true
• 分享了疫苗机器人提示想法 361807/9?silent=true

\u003ca class="mention" href="/u/isaac"\u003eisaac\u003c/a\u003e (4 个赞，1 篇帖子)
• 宣布了对话列表的 PR 合并 362711/7?silent=true

\u003ca class="mention" href="/u/keegan"\u003ekeegan\u003c/a\u003e (3 个赞，2 篇帖子)
• 调查了助手挂起问题，启用了 PM 调试 362643/7?silent=true 和 362643/8?silent=true

\u003ca class="mention" href="/u/awesomerobot"\u003eawesomerobot\u003c/a\u003e (3 个赞，2 篇帖子)
• 确认尚未内置“起草回复”功能 363298/3?silent=true
• 应用了先前模态补丁的 UX 修复 363692/4?silent=true

\u003ca class="mention" href="/u/maiki"\u003emaiki\u003c/a\u003e (3 个赞，1 篇帖子)
• 在管理员 UI 中验证了工具名称字段 330830/3?silent=true

\u003ca class="mention" href="/u/Moin"\u003eMoin\u003c/a\u003e (3 个赞，1 篇帖子)
• 报告了编辑器中 AI 图标裁剪问题 363692/1?silent=true

\u003ca class="mention" href="/u/Yenwod"\u003eYenwod\u003c/a\u003e (2 个赞，2 篇帖子)
• 试验了疫苗机器人工具 361807/8?silent=true 和 361807/11?silent=true

感谢阅读，下周再见！:slight_smile:

66

概述

“此主题组件为每个帖子添加了一个按钮，允许用户通过直接聊天消息将帖子发送给 AI 机器人进行分析。” — Don, AI Post Analyzer for Chat

在过去的一周（2025 年 4 月 28 日至 2025 年 5 月 5 日），#meta.discourse.org 充满了 ai 增强和深度讨论：

AI Post Analyzer for Chat 的推出在 chat 中提供了一个便捷的 AI 按钮；OpenAI image generation and editing now supported in Discourse AI 的发布将 GPT-image-1 工作流带到了 Announcements；Is an automation like this possible with Discourse AI today? 讨论串探讨了通过 LLM 自动化产品公告摘要和横幅创建；A Plug-In to convert Discourse Forum Discussions into Clear Proposal Revisions with Community-Sourced Justifications 提出了用于治理的 SimScore；而 AI changed quite many gists in English 支持主题则解决了由提示驱动的语言混淆问题。

热烈的后续讨论重新审视了 AI Post Analyzer for Chat 的重命名指导，推动了 OpenAI image generation and editing now supported in Discourse AI 的测试，优化了 Is an automation like this possible with Discourse AI today? 的逻辑，解决了 SimScore 插件主题 (A Plug-In to convert Discourse Forum Discussions into Clear Proposal Revisions with Community-Sourced Justifications) 的托管限制，并处理了 AI changed quite many gists in English 中的数据库清理。

在工具方面，The complete list of variables used in AI prompts 引发了对全面文档的需求；AI helper hallucinating a lot when explaining something 讨论串暴露了模型的怪癖；How to install and configure AI features step by step 阐明了插件设置；AI Assistants with Web Search capability 的讨论确认了自定义代理的灵活性；而 Provide visual cue when a topic is receiving an AI response 则提出了用户体验的增强。

随后的更新要求扩展 The complete list of variables used in AI prompts 以支持个性化定制；在 AI helper hallucinating a lot when explaining something 讨论串中提供了模型更换建议；改进了 How to install and configure AI features step by step 中的安装指南；测试了 AI Assistants with Web Search capability 的网络搜索集成；并在 Provide visual cue when a topic is receiving an AI response 中讨论了设计模式。

有趣的话题

活动

感谢阅读，下周再见！ :slight_smile:

67

Weekly AI Activity on meta.discourse.org (May 5 – May 12, 2025)

Overview

Over the past week, the ai and ai-bot community dove into a variety of Support, Bug, UX, and Feature discussions. From customizing the AI bot homepage to fixing a persistent topic‐summary hang, members collaborated on configuration tricks, merged hotfixes for PDF uploads and image captioning, and ironed out UX quirks like proofread quote handling and AI typing indicators. Under the hood, developers wrestled with LLM performance—troubleshooting a Perplexity Sonar Deep Research setup—and explored advanced automations and web‐search integrations, laying groundwork for richer AI experiences in Discourse.

Interesting Topics

  • Custom AI Bot Homepage (Support, ai)
    kuaza opened “How to set the home page to be an AI bot?” to replicate an ask.discourse.com‐style landing page, testing trust‐level redirects; Lilly later demonstrated success using AI bot enable dedicated UX and the Custom Homepage for Groups component in post #7.

  • Topic Summary Hanging (Bug, ai)
    KhoiUSA reported that “Summarize Topic” hung with a 400 Invalid JSON Payload error in post #1. Falco recommended switching the provider to OpenAI and updating the endpoint, resolving the issue in post #5, and sam suggested adding fallback logic for unexpected non‐JSON responses in post #7.

  • Proofread Breaks Quotes (UX, ai-helper)
    Jagster flagged that the Proofread helper mangles quotes in the preview in post #1. Falco clarified it’s a visualization quirk and proposed a diff‐only approach in post #2, and stance455 confirmed quoted text is skipped after the latest update in post #3.

  • PDF Upload in AI Bot UX (Support, ai-bot)
    MachineScholar asked if the new AI Bot UX supports text‐based PDFs in post #1, referencing the enhanced PDF processing roadmap. Falco merged a bugfix in post #4 enabling RAG on image‐only PDFs, though full text‐PDF support remains under development.

  • Perplexity Sonar Deep Research Configuration (Dev, ai)
    aas encountered 502 errors testing perplexity/sonar-deep-research via OpenRouter in post #1, while sam noted API slowness and high per‐reply costs in post #2.

  • AI Image Captioning Enhancement (Announcements, ai-helper)
    On the AI Image Captioning Feature plugin, fokx requested background processing after upload in post #31, and Falco confirmed plans to defer captioning until after submission in post #32.

  • Disable AI Title Generator in PMs (UX, ai-helper)
    awesomerobot merged a fix for the AI title generator not being editable in private messages in post #2.

  • Auto Responder Using AI (Feature, automation)
    Geraldine_Comiskey sketched out an AI‐powered auto‐responder for unwanted DMs in post #17, sparking ideas for conversational “chatbot” flows.

  • AI Typing Indicator & Visual Cue (Feature, ai)
    sam proposed displaying an “AI is typing” placeholder on topic pages to signal live AI responses, extending existing chat presence indicators in post #4.

  • AI Assistants with Web Search (Support, ai-bot)
    sam detailed how the OpenAI Responses API supports integrated search and demoed built‐in Google search tooling from the discourse-ai repo, along with a shared conversation demo.

Activity

Below is a summary of contributions by all active users over the past week:

Thanks for reading, and I’ll see you again next week! :slight_smile: