Resumo semanal de tópicos de IA

Feedback do site Resumos do fórum
68

Visão Geral

As conversas sobre IA nesta semana na Meta se concentraram em gerenciamento de conteúdo com IA, refinamentos de UI e correções internas. Os principais temas incluíram:

  1. Divisão de tópicos por IA: O lançamento de Usando o pesquisador de fóruns para ajudar a organizar e dividir tópicos grandes (#Comunidade, #ia) gerou comparações lado a lado de fluxos de trabalho manuais vs. assistidos por IA, com \u003ca class="mention" href="/u/JammyDodger"\u003eJammyDodger\u003c/a\u003e compartilhando conselhos detalhados sobre divisão manual.
  2. Visibilidade aprimorada da persona de IA: Discussões em Criar um link mais perceptível para a persona de IA (#Suporte, #ia) exploraram a colocação de um ícone de chatbot maior na UI e até mesmo a substituição de imagens personalizadas para maior destaque.
  3. Transformação da página inicial: A ideia de transformar a página de destino em uma interface de bot de IA foi prototipada em Como definir a página inicial para ser um bot de IA? ex: ask.discourse.com (#Suporte, #ia), com \u003ca class="mention" href="/u/Lilly"\u003eLilly\u003c/a\u003e sugerindo automações de convite de grupo.
  4. Passagem de dados de artefatos: Em Como passo dados para um artefato? (#Recurso, #artefatos-ia), \u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e introduziu uma correção de API baseada em postMessage, posteriormente mesclada como um pull request.
  5. Correções de esquema e payload: Um bug crítico na análise de JSON foi resolvido em Resumir Tópico com IA carrega indefinidamente, Payload JSON Inválido Recebido? (Bug, #ia) por meio de ajustes no manipulador de esquema Gemini.
  6. Ajustes de posicionamento de UX: Ajustes para evitar que o botão flutuante de Documentos de IA se sobreponha aos controles nativos foram delineados em Botão de sobreposição de Documentos de IA mal posicionado (UX, #acessibilidade, #ia).
  7. Considerações de custo: Avisos sobre chamadas de modelo caras surgiram em Problemas na configuração manual da pesquisa profunda do sonar de perplexidade (Dev, #ia), observando que uma única resposta poderia custar mais de US$ 0,70.
  8. Fluxos de trabalho estendidos de divisão de tópicos: Posts de acompanhamento em Usando o pesquisador de fóruns para ajudar a organizar e dividir tópicos grandes testaram a ferramenta em outros tópicos “coletivos”.
  9. Aprimoramentos adicionais de persona: Membros da comunidade iteraram sobre a abordagem de \u003ca class="mention" href="/u/Lilly"\u003eLilly\u003c/a\u003e em Criar um link mais perceptível para a persona de IA, construindo componentes personalizados através do plugin Discourse Custom Components.
  10. Rastreamento de patches de backend: Mais correções foram rastreadas através de atualizações de PR em Como passo dados para um artefato? e ajustes de margem em Botão de sobreposição de Documentos de IA mal posicionado.

Tópicos Interessantes

  • Usando o pesquisador de fóruns para ajudar a organizar e dividir tópicos grandes (tópico 366188, #Comunidade, #ia)
    \u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e demonstrou uma persona de IA desativada por padrão para pesquisa profunda, mostrando esboços automatizados para o tópico Quadro Kanban.

  • Criar um link mais perceptível para a persona de IA (tópico 365884, #Suporte, #ia)
    \u003ca class="mention" href="/u/Angela_MRS"\u003eAngela_MRS\u003c/a\u003e perguntou como aumentar o ícone do chatbot, e \u003ca class="mention" href="/u/Lilly"\u003eLilly\u003c/a\u003e compartilhou hacks de barra lateral e menu suspenso.

  • Botão de sobreposição de Documentos de IA mal posicionado (tópico 366138, UX, #acessibilidade, #ia)
    \u003ca class="mention" href="/u/SvenPuschmann"\u003eSvenPuschmann\u003c/a\u003e relatou o botão flutuante de Documentos de IA obstruindo os controles do iOS, com \u003ca class="mention" href="/u/pmusaraj"\u003epmusaraj\u003c/a\u003e sugerindo correções simples de margem CSS.

  • Como passo dados para um artefato? (tópico 350791, #Recurso, #artefatos-ia)
    Uma solução postMessage que requer sandboxing foi implementada por \u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e, rastreada em PR #1346.

  • Resumir Tópico com IA carrega indefinidamente, Payload JSON Inválido Recebido? (tópico 365587, Bug, #ia)
    \u003ca class="mention" href="/u/Roman_Rizzi"\u003eRoman_Rizzi\u003c/a\u003e confirmou que o ajuste do formato do esquema JSON em PR #1340 resolveu os erros de carregamento infinito.

  • Problemas na configuração manual da pesquisa profunda do sonar de perplexidade (tópico 365572, Dev, #ia)
    Obstáculos de configuração e custos por token foram sinalizados por \u003ca class="mention" href="/u/aas"\u003eaas\u003c/a\u003e após citar a cautela de \u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e sobre despesas.

  • Como definir a página inicial para ser um bot de IA? ex: ask.discourse.com (tópico 365126, #Suporte, #ia)
    As propostas incluíram scripts de automação para inscrição automática por meio de campos de usuário personalizados, demonstrados por \u003ca class="mention" href="/u/Lilly"\u003eLilly\u003c/a\u003e.

Atividade

Obrigado pela leitura, e nos vemos na próxima semana! :slight_smile:

69

Overview

This week the community dove into improving AI workflows and tooling across Meta Discourse. Key initiatives included exploring persistent JSON data storage in AI artifacts to empower user‐bound data management, crafting a roadmap for an official Model Context Protocol (MCP) to standardize AI tool integrations, and resolving an audio playback issue in the AI Helper that was interrupting uploaded mp3 streams. We also saw experiments with Discord search integration, tackled subcategory slug bugs in the AI bot’s outputs via Category listing for AI does not return full slugs, and refined content organization using the forum researcher tool. Best practices for Discourse AI examples, discussions on AI‐driven moderation, and proposals to empower the SQL helper rounded out an active week of collaboration.

Interesting Topics

Activity

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

70

Overview

Over the past week on #meta.discourse.org, the community’s focus centered on the rollout and configuration of Discourse AI’s new Forum Researcher persona, alongside vital bug fixes, self-hosting guidance, and customization requests. Administrators and power users dove into the Forum Researcher AI Persona guide to fine-tune their LLM settings, while several support threads detailed troubleshooting—ranging from mobile UI scroll issues to JSON parsing errors in the researcher tool. Conversations also spanned best practices for self-hosters (spam, #AI-detection), implementing local LLMs, automating AI replies, and renaming or removing default AI personas. This variety of discussions highlights both the excitement around AI-powered features and the community’s dedication to smooth deployment and customization.

Interesting Topics

  • Announcing the Forum Researcher Announcements ai
    sam unveiled the new Forum Researcher persona, a powerful ai-bot tool for in-depth analysis of forum content. The initial announcement ref showcased sample executive reports, and MachineScholar lauded its potential for research workflows ref.

  • Forum Researcher AI Persona guide #Site Management how-to ai ai-bot
    In this comprehensive guide, sam walked administrators through enabling the persona, selecting appropriate Large Language Models, and debugging research tasks ref.

  • Discourse AI spam detection replaces Akismet plugin Announcements spam ai
    Self-hosting concerns emerged when patrickemin discovered Akismet was no longer bundled and asked about alternatives ref. Moin highlighted documentation gaps ref, and sam recommended free Discourse AI models or Gemini Flash 2.0 for self-hosters ref.

  • Mobile AI helper popup cannot be scrolled Bug mobile ai-helper
    NateDhaliwal reported that AI response popups on Android Chrome cut off long answers ref. keegan deployed a fix ref, which NateDhaliwal confirmed resolved the issue ref.

  • Unexpected error in Forum Researcher Bug ai ai-bot
    When noahl tested the new tool, they encountered a JSON parsing error ref. sam traced the issue to the hosted LLM’s capacity ref, and Falco explained the dropdown model access was for early testers ref.

  • Discourse AI – Summarize model upgrade question #Site Management ai-summarize
    Heliosurge asked if Discourse AI had moved from Gemini v1.5 to v2.0 ref. Falco confirmed support for Gemini 2 and 2.5 ref.

  • Configuring Discourse with a locally installed LLM Support ai
    Falco recommended DeepSeek V3, Qwen 3, and Llama 3.3 among top-tier models, and suggested a lightweight Hugging Face option for small communities ref.

  • How to generate AI replies for existing forum topics Support ai automation
    MihirR inquired about backfilling old topics with AI replies ref. satonotdead outlined using Discourse AI + Automation plugins ref, while sam advised this remains a manual API workflow for now ref.

  • Removing default AI personas/bots Support ai-bot
    satonotdead asked if default prompts could be removed via console ref, and Falco explained they’re part of plugin code but noted future support for custom texts ref.

  • Renaming “AI Persona” → “AI Agent” Feature ai
    iamcapote proposed renaming for clarity and requested an editable setting ref.

Activity

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

71

Overview

Over the past week, the ai community on meta.discourse.org has been bustling with new capabilities, feature explorations, and troubleshooting discussions:

Interesting Topics

Activity

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

72

Overview

This week’s AI discussions spanned enhancements to ai-artifacts, ai-captions, and ai-bot features, alongside self-hosting strategies, token transparency, and integration workflows. Notably, the AI Artifact User storage announcement catalyzed requests for wider artifact creation controls and led directly to An admin API for AI web artifact creation and editing. On the accessibility front, users in Is there any way to permanently disable AI captions as a user? uncovered a persistent prompting bug that sam acknowledged and keegan began investigating. The Support category also tackled user-level AI behaviors like reenabling search discoveries and clarifying what consumes API tokens. Meanwhile, #Self-Hosting advocates in Self-Hosting Sentiment and Emotion for DiscourseAI successfully deployed local models, and Feature contributors debated a “Model Context Protocol” in Is there an official Discourse Model Context Protocol (MCP). Lastly, routing and performance surfaced in Redirect logged-in users to conversations page and Job exception: Net::ReadTimeout during custom tool usage.

Interesting Topics

Activity

Below is a rundown of contributors and the threads they engaged with this week:

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

73

Overview

Over the week of June 23–30, 2025, the ai section on Meta Discourse buzzed with new Feature proposals, deep technical dives, and swift resolutions of Bug and Support threads. Key highlights included community efforts to define a dedicated administration endpoint for AI Web Artifacts via An admin API for AI web artifact creation and editing, renewed exploration of embedding-based search in Support for Vanilla Embedding Search, and fresh calls for a native Model Context Protocol server in Is there an official Discourse Model Context Protocol (MCP). Data aficionados dissected sentiment analytics in Joining classification_results table to other tables support request, while plugin maintainers and self-hosters tackled issues from Gemini AI image analysis errors to Bootstrap migrations with the AI plugin and group-based summarization controls via personas in Managing user groups for summarization features. The long-standing announcement Announcing: AI Web Artifacts also saw spinoff questions from iamcapote and sam about admin-only artifact creation flows. Even UI tweaks like Redirect logged-in users to conversations page and image embedding quirks in Discourse AI image didn’t load correctly kept the conversation lively.

Interesting Topics

Activity

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

74

Resumo Semanal da Atividade de IA
Data de Início: 2025-06-30
Data de Fim: 2025-07-07

Visão Geral
As conversas sobre ai desta semana em meta.discourse.org abrangeram preocupações ambientais, flexibilidade de plugins, personalização de recursos e correções de bugs. pHneutre liderou um debate sobre computação verde em AI-free Discourse (veja post #2 para a resposta de merefield).
A estabilidade do modelo de visão foi verificada em Quick welfare check on the AI caption bot com etapas de resolução em post #2 e post #3.
Os administradores refinaram os controles de persona em Is it possible to enable only one AI persona?, conforme Falco detalhou os alternadores em post #2.
A flexibilidade de sumarização evoluiu através de Can you customize the Ai Summarize prompt? e Customizing AI summarizer to use non-English languages, com acompanhamentos em 372448/2 e 372644/2.
A extensão de contexto através de RAG foi explorada em Another added context for AI Bot (detalhes em post #2).
As principais correções de bugs incluíram o erro “no implicit conversion of Array into String” em Error "no implicit conversion of Array into String" (resolvido em post #5), campos opcionais sendo redefinidos em Small bug in AI Persona Editor e omissões de rótulos de modelo em Model name not showing in AI bot.
Tópicos de automação e integração de pesquisa ganharam força em Discourse AI - AI triage e Discourse AI - AI search.

Tópicos Interessantes

Atividade

Obrigado pela leitura e nos vemos na próxima semana! :slight_smile:

78

OverviewOver the past week, our ai category on #meta.discourse.org featured a major rollout of Content Localization and Automatic Translations with the announcement and a comprehensive manual guide, sparking discussions on language selector UX (https://meta.discourse.org/t/-/370000/6?silent=true, https://meta.discourse.org/t/-/370000/7?silent=true) and translation flags (https://meta.discourse.org/t/-/370000/9?silent=true, https://meta.discourse.org/t/-/370000/11?silent=true). Meanwhile, the Forum Researcher AI Persona was dissected in a thread on custom prompt filters and hallucination handling (https://meta.discourse.org/t/-/368942/9?silent=true, https://meta.discourse.org/t/-/368942/12?silent=true). Contributors also tackled Discourse AI plugin issues across the asset pipeline troubleshooting and AWS Bedrock integration. Administrators grappled with sporadic500/504 errors in semantic search (https://meta.discourse.org/t/-/373769/1?silent=true, https://meta.discourse.org/t/-/373769/4?silent=true), inspected truncated spam detection logs (https://meta.discourse.org/t/-/373460/1?silent=true), restored missing LLM settings after update (https://meta.discourse.org/t/-/373367/1?silent=true, https://meta.discourse.org/t/-/373367/2?silent=true), and polished persona fields in the AI bot editor (https://meta.discourse.org/t/-/373176/2?silent=true, https://meta.discourse.org/t/-/373151/2?silent=true). A handful of translatability gaps surfaced in inferred concept settings (https://meta.discourse.org/t/-/373346/1?silent=true), underscoring ongoing efforts to ensure a fully multilingual AI experience.## Interesting Topics- nat announced the release of content-localization with Content Localization and Automatic Translations for Your Community on2025-07-10, detailing sitewide multilingual support and kicking off deep-dive conversations on UX and moderator flows (https://meta.discourse.org/t/-/370000/6?silent=true, https://meta.discourse.org/t/-/370000/7?silent=true, https://meta.discourse.org/t/-/370000/8?silent=true, https://meta.discourse.org/t/-/370000/9?silent=true, https://meta.discourse.org/t/-/370000/10?silent=true, https://meta.discourse.org/t/-/370000/11?silent=true, https://meta.discourse.org/t/-/370000/12?silent=true).- nat provided an in-depth Content Localization - Manual and Automatic with Discourse AI guide, walking admins through setup, category localization, and bulk API considerations (https://meta.discourse.org/t/-/370969/2?silent=true, https://meta.discourse.org/t/-/370969/3?silent=true).- sam and jrgong examined the Feature Forum Researcher AI Persona guide, debating the need for external docs on custom search parameters (https://meta.discourse.org/t/-/368942/7?silent=true, https://meta.discourse.org/t/-/368942/8?silent=true, https://meta.discourse.org/t/-/368942/9?silent=true, https://meta.discourse.org/t/-/368942/10?silent=true, https://meta.discourse.org/t/-/368942/11?silent=true, https://meta.discourse.org/t/-/368942/12?silent=true).- productdeploy flagged an SCSS compile error post-plugin install in the Plugin Discourse AI thread, prompting discussions on stable vs tests-passed branches and AWS integration (https://meta.discourse.org/t/-/259214/213?silent=true, https://meta.discourse.org/t/-/259214/214?silent=true, https://meta.discourse.org/t/-/259214/215?silent=true, https://meta.discourse.org/t/-/259214/216?silent=true, https://meta.discourse.org/t/-/259214/217?silent=true, https://meta.discourse.org/t/-/259214/218?silent=true).- Moin opened a Site feedback Frequent Error500 after searching thread on random500/504 modals during semantic search, confirmed by patrickemin and gormus (https://meta.discourse.org/t/-/373769/1?silent=true, https://meta.discourse.org/t/-/373769/2?silent=true, https://meta.discourse.org/t/-/373769/3?silent=true, https://meta.discourse.org/t/-/373769/4?silent=true).- sam caught a minor bug in the Bug AI Persona Editor, where optional fields persisted after save, and joffreyjaffeux quickly merged a fix (https://meta.discourse.org/t/-/373176/2?silent=true, https://meta.discourse.org/t/-/373176/4?silent=true).- Cédric_Brunet reported missing LLM settings post-update in Support Discourse AI, leading to a discussion on restoring vs streamlining settings (https://meta.discourse.org/t/-/373367/1?silent=true, https://meta.discourse.org/t/-/373367/2?silent=true, https://meta.discourse.org/t/-/373367/3?silent=true).- per1234 noted that Bug spam detection scan logs are truncated, clarifying expectations for the admin test dialog (https://meta.discourse.org/t/-/373460/1?silent=true).- Moin highlighted the need for translatable labels in the #translations settings inferred concepts feature to aid non-English admins (https://meta.discourse.org/t/-/373346/1?silent=true).- sam suggested renaming LLM users to control display names in the Bug AI bot, an idea validated by MachineScholar (https://meta.discourse.org/t/-/373151/2?silent=true, https://meta.discourse.org/t/-/373151/3?silent=true).## Activity- nat (64 likes,11 posts) led the Content Localization announcement, refined UX in https://meta.discourse.org/t/-/370000/6?silent=true & https://meta.discourse.org/t/-/370000/9?silent=true, authored the manual guide and bulk API response (https://meta.discourse.org/t/-/370969/2?silent=true), and clarified translation flags in https://meta.discourse.org/t/-/370000/10?silent=true & https://meta.discourse.org/t/-/370000/11?silent=true.- Moin (15 likes,5 posts) probed moderator flags in https://meta.discourse.org/t/-/370000/9?silent=true, stress-tested translation flags (https://meta.discourse.org/t/-/370000/11?silent=true), reported semantic search errors, flagged infer settings gaps (https://meta.discourse.org/t/-/373346/1?silent=true), and explained plugin pinning (https://meta.discourse.org/t/-/259214/216?silent=true).- sam (5 likes,8 posts) debugged the Researcher AI Persona (https://meta.discourse.org/t/-/368942/9?silent=true, https://meta.discourse.org/t/-/368942/10?silent=true, https://meta.discourse.org/t/-/368942/12?silent=true), fixed the SCSS pipeline in https://meta.discourse.org/t/-/259214/214?silent=true, and restored missing settings in https://meta.discourse.org/t/-/373367/2?silent=true.- Simon_Manning (4 likes,2 posts) raised UX considerations in https://meta.discourse.org/t/-/370000/6?silent=true and supported dual-language selectors (https://meta.discourse.org/t/-/370000/8?silent=true).- Falco (3 likes,1 post) recommended the default release channel in https://meta.discourse.org/t/-/259214/218?silent=true.- joffreyjaffeux (2 likes,1 post) merged the optional fields fix in https://meta.discourse.org/t/-/373176/4?silent=true.- putty (2 likes,1 post) inquired about bulk localization via API in https://meta.discourse.org/t/-/370969/2?silent=true.- gerryfw (2 likes,3 posts) discussed SEO impacts (https://meta.discourse.org/t/-/370000/16?silent=true), confirmed translator plugin status (https://meta.discourse.org/t/-/370000/13?silent=true), and noted hreflang flags (https://meta.discourse.org/t/-/370000/21?silent=true).- jrgong (2 likes,2 posts) sought docs for prompt filters (https://meta.discourse.org/t/-/368942/8?silent=true) and API reproduction of filters (https://meta.discourse.org/t/-/368942/11?silent=true).- gormus (1 like,2 posts) documented repeated search failures in https://meta.discourse.org/t/-/373769/3?silent=true & https://meta.discourse.org/t/-/373769/4?silent=true.Thanks for reading, and I’ll see you again next week! :slight_smile:

79

Weekly AI Activity Summary (2025-07-14 – 2025-07-21)

Overview

This past week on Meta saw deep dives into content localization, AI tooling, and site reliability. The community explored fully automated workflows in Content Localization and Automatic Translations for Your Community (Announcements, ai, content-localization) and introduced per-language moderator roles via Content Localization - Manual and Automatic with Discourse AI (#Site Management, ai, content-localization). Administrators triaged hidden configuration calls in AI helper model site setting is hidden now but still in use (Bug, ai) and patched summarizer errors after You need to select a model before the AI Summarizer Persona works (Bug, ai-summarize). There was hands-on troubleshooting around bot customization in Discourse AI - AI bot (#Site Management, ai-bot), while backfill translation roadblocks surfaced in AI translation backfill not working after all settings configured (Support, content-localization) and The usage problem after using AI translation (Support, ai). Reliability issues in Frequent Error 500 after searching (#Site feedback, ai-search) led to error-tracking improvements, and new sentiment analytics were unveiled in AI sentiment and emotion analysis reports (#Data & reporting, ai-sentiment). Lastly, UI tweaks for category/tag suggestions were covered in AI helper icon not appearing for category and tags field (Support, ai-helper).

Interesting Topics

Activity

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

80 
# Resumo Semanal da Atividade de IA em meta.discourse.org  
**Período:** 21/07/2025 a 28/07/2025  
**Novas postagens:** 43 · **Novos tópicos:** 16  

---

## Visão Geral  
Esta semana viu uma mistura de solução de problemas técnicos, solicitações de recursos e discussões de roadmap em torno das ofertas de IA do Discourse. Os temas principais incluíram:

- **Problemas de atualização e compilação** causados por um espelho npm chinês desatualizado #Bug #ai.  
- **Ajuste da proteção contra spam**, com comunidades privadas desativando filtros de spam de IA #Bug #ai.  
- **Agrupamento do plugin Discourse AI** no core e questões relacionadas de integração #Plugin #official #included-in-core #ai.  
- **Fluxos de trabalho de tradução**, cobrindo a retradução de postagens geradas por IA e peculiaridades de cache #ai #ai-helper.  
- **Controle de comportamento de bots**, de limites de resposta a opções de gatilho #Support #ai-bot.  
- **Integrações de LLM de terceiros** (Azure OpenAI, IBM WatsonX) e uploads RAG #Integrations #ai #ai-bot.  
- **Engenharia de persona**, incluindo conversão de logs do Slack e exploração de sub-agentes #SiteManagement #ai-bot.  
- Discussões sobre a adoção do **Model Context Protocol (MCP)** #Feature #ai.  

---

## Tópicos Interessantes  

- Falhas de compilação durante atualizações do Discourse devido a uma incompatibilidade de espelho npm chinês  
  ([Build failures during Discourse updates due to a Chinese npm mirror mismatch](https://meta.discourse.org/t/-/376095/1?silent=true)) #Bug #ai  

- Filtro de spam de IA superativo em comunidades privadas e como desativá-lo  
  ([Overactive AI spam filter in private communities and how to disable it](https://meta.discourse.org/t/-/375475/1?silent=true)) #Bug #ai  

- Agrupamento oficial do plugin Discourse AI no core e notas de atualização  
  ([Official bundling of the Discourse AI plugin into core and upgrade notes](https://meta.discourse.org/t/-/259214/219?silent=true)) #Plugin #official #included-in-core #ai  

- Retraduzindo conteúdo gerado por IA e lidando com traduções desatualizadas  
  ([Retranslating AI-generated content and dealing with stale translations](https://meta.discourse.org/t/-/259214/221?silent=true)) &  
  ([AI helper does not always use user's locale](https://meta.discourse.org/t/-/298867/6?silent=true)) #ai #ai-helper  

- Controle de gatilhos de resposta do assistente de IA, limites por tópico ou por usuário  
  ([Controlling AI helper response triggers, limits per topic or per user](https://meta.discourse.org/t/-/376066/1?silent=true)) #Support #ai-bot  

- Configuração de chaves de API do Azure OpenAI e solução de problemas de erros 500  
  ([Configuring Azure OpenAI API keys and troubleshooting 500 errors](https://meta.discourse.org/t/-/282442/7?silent=true)) #Integrations #ai  

- Projetando e gerenciando personas de IA usando fontes de conhecimento externas  
  ([Designing and managing AI personas using external knowledge sources](https://meta.discourse.org/t/-/306099/16?silent=true)) #SiteManagement #ai-bot  

- Roadmap e status de adoção do Model Context Protocol (MCP)  
  ([Roadmap and adoption status of the Model Context Protocol (MCP)](https://meta.discourse.org/t/-/364859/16?silent=true)) #Feature #ai  

- Personalizando o ícone do robô de IA no cabeçalho e na barra lateral  
  ([Customizing the AI robot icon in the header and sidebar](https://meta.discourse.org/t/-/375472/1?silent=true)) #Support #ai  

- Uploads programáticos para fluxos de trabalho de Geração Aumentada por Recuperação (RAG)  
  ([Programmatic uploads for Retrieval-Augmented Generation (RAG) workflows](https://meta.discourse.org/t/-/374408/3?silent=true)) #Support #ai-bot  

---

## Atividade  
Aqui estão quem postou esta semana e onde:

- <a class="mention" href="/u/cshll">cshll</a> abriu um problema sobre o erro do espelho npm em [Build failures during Discourse updates due to a Chinese npm mirror mismatch (post #1)](https://meta.discourse.org/t/-/376095/1?silent=true) e adicionou detalhes de acompanhamento em [post #3](https://meta.discourse.org/t/-/376095/3?silent=true).  

- <a class="mention" href="/u/sam">sam</a> sugeriu uma recompilação do console em [Build failures during Discourse updates due to a Chinese npm mirror mismatch (post #2)](https://meta.discourse.org/t/-/376095/2?silent=true), comentou sobre a configuração do filtro de spam em [Overactive spam filter? (post #5)](https://meta.discourse.org/t/-/375475/5?silent=true) e confirmou o cache de local em [AI helper does not always use user's locale (post #6)](https://meta.discourse.org/t/-/298867/6?silent=true).  

- <a class="mention" href="/u/david">david</a> esclareceu erros de pacotes ausentes em [Build failures during Discourse updates due to a Chinese npm mirror mismatch (post #5)](https://meta.discourse.org/t/-/376095/5?silent=true) e celebrou o agrupamento de plugins em [Discourse AI (post #219)](https://meta.discourse.org/t/-/259214/219?silent=true).  

- <a class="mention" href="/u/Moin">Moin</a> apontou problemas de cache de tradução em [Build failures during Discourse updates due to a Chinese npm mirror mismatch (post #6)](https://meta.discourse.org/t/-/376095/6?silent=true) e compartilhou como desativar o tratamento de spam de IA em [Overactive spam filter? (post #3)](https://meta.discourse.org/t/-/375475/3?silent=true).  

- <a class="mention" href="/u/Lhc_fl">Lhc_fl</a> recomendou o uso de servidores ou proxies não chineses em [Build failures during Discourse updates due to a Chinese npm mirror mismatch (post #8)](https://meta.discourse.org/t/-/376095/8?silent=true).  

- <a class="mention" href="/u/NateDhaliwal">NateDhaliwal</a> perguntou sobre o tipo de instalação em [Build failures during Discourse updates due to a Chinese npm mirror mismatch (post #4)](https://meta.discourse.org/t/-/376095/4?silent=true) e perguntou sobre logs para configuração do Azure em [Configure API Keys for Azure OpenAI (post #8)](https://meta.discourse.org/t/-/282442/8?silent=true).  

- <a class="mention" href="/u/Seth_Godin">Seth_Godin</a> relatou um bloqueio de spam em comunidade privada em [Overactive spam filter? (post #1)](https://meta.discourse.org/t/-/375475/1?silent=true).  

- <a class="mention" href="/u/Jagster">Jagster</a> ofereceu uma substituição de prompt do sistema em [Overactive spam filter? (post #4)](https://meta.discourse.org/t/-/375475/4?silent=true) e exemplos de prompts em [Controlling AI responses (post #5)](https://meta.discourse.org/t/-/376066/5?silent=true).  

- <a class="mention" href="/u/nat">nat</a> verificou o uso do espelho com Lhc_fl em [Build failures during Discourse updates due to a Chinese npm mirror mismatch (post #7)](https://meta.discourse.org/t/-/376095/7?silent=true).  

- <a class="mention" href="/u/jrgong">jrgong</a> elogiou o guia de ajuda do Sam em [Why is my AI forum helper struggling? (post #2)](https://meta.discourse.org/t/-/352848/2?silent=true) e perguntou sobre a estrutura de persona baseada em logs em [AI bot - Personas (post #16)](https://meta.discourse.org/t/-/306099/16?silent=true).  

- <a class="mention" href="/u/Falco">Falco</a> explicou a exclusão de traduções via console em [Discourse AI (post #222)](https://meta.discourse.org/t/-/259214/222?silent=true), abordou a compatibilidade da API do IBM WatsonX em [LLM settings page (post #17)](https://meta.discourse.org/t/-/319903/17?silent=true) e esclareceu gatilhos de bot em [Controlling AI responses (post #3)](https://meta.discourse.org/t/-/376066/3?silent=true).  

- <a class="mention" href="/u/RBoy">RBoy</a> buscou controles sobre limites de resposta do bot em [Controlling AI responses (post #1)](https://meta.discourse.org/t/-/376066/1?silent=true), [post #2](https://meta.discourse.org/t/-/376066/2?silent=true) e [post #6](https://meta.discourse.org/t/-/376066/6?silent=true).  

- <a class="mention" href="/u/satonotdead">satonotdead</a> sugeriu prompts de transferência humana em etapas em [Controlling AI responses (post #4)](https://meta.discourse.org/t/-/376066/4?silent=true).  

- <a class="mention" href="/u/Wurzelseppi">Wurzelseppi</a> perguntou sobre a criação de referências de upload RAG em [Programmatic RAG uploads? (post #3)](https://meta.discourse.org/t/-/374408/3?silent=true).  

- <a class="mention" href="/u/Goalina">Goalina</a> perguntou sobre contagens de retradução em [Discourse AI (post #221)](https://meta.discourse.org/t/-/259214/221?silent=true).  

- <a class="mention" href="/u/ばこん">ばこん</a> relatou uma página de preferências de IA ausente em [Discourse AI - AI search (post #16)](https://meta.discourse.org/t/-/282420/16?silent=true).  

- <a class="mention" href="/u/EricGT">EricGT</a> propôs a terminologia "Sub-Agent" em [Renaming AI Persona → AI Agent (post #7)](https://meta.discourse.org/t/-/368198/7?silent=true).  

- <a class="mention" href="/u/CraigW">CraigW</a> perguntou sobre a integração do IBM WatsonX em [LLM settings page (post #16)](https://meta.discourse.org/t/-/319903/16?silent=true).  

- <a class="mention" href="/u/MachineScholar">MachineScholar</a> acompanhou a maturidade do MCP em [Is there an official Discourse MCP (post #16)](https://meta.discourse.org/t/-/364859/16?silent=true).  

- <a class="mention" href="/u/zabin">zabin</a> compartilhou uma solução alternativa Bitnami-Postgres para migração de plugins em [Bootstrap error with AI plugin (post #6)](https://meta.discourse.org/t/-/371514/6?silent=true) e registrou falhas de teste do Azure em [Configure API Keys for Azure (post #9)](https://meta.discourse.org/t/-/282442/9?silent=true).  

---

Obrigado pela leitura, e vejo vocês novamente na próxima semana! :slight_smile:
81

Weekly AI Activity Summary (2025-08-04 to 2025-08-11)

Overview

Over the past week, the Discourse AI ecosystem saw multiple fronts of progress:

Interesting Topics

Activity

Below is a breakdown of contributions by user, with links to topics and posts they engaged in last week:

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

82 
# Weekly AI Activity Summary on meta.discourse.org
**Period:** 2025-08-11 to 2025-08-18  
**New posts:** 32 • **New topics:** 3  
**Top users:** <a class="mention" href="/u/sam">sam</a> (14 likes, 9 posts), <a class="mention" href="/u/pfaffman">pfaffman</a> (7 likes, 1 post), <a class="mention" href="/u/mcwumbly">mcwumbly</a> (7 likes, 3 posts), <a class="mention" href="/u/jrgong">jrgong</a> (4 likes, 2 posts), <a class="mention" href="/u/Roman">Roman</a> (3 likes, 2 posts), <a class="mention" href="/u/Lilly">Lilly</a> (3 likes, 1 post), <a class="mention" href="/u/maiki">maiki</a> (2 likes, 1 post), <a class="mention" href="/u/Lee_Ars">Lee_Ars</a> (2 likes, 2 posts), <a class="mention" href="/u/awesomerobot">awesomerobot</a> (2 likes, 2 posts), <a class="mention" href="/u/ozkn">ozkn</a> (2 likes, 1 post)  

## Overview
This week’s discussions spanned new #Feature requests, #Bug reports, and #Plugin tweaks across Discourse’s AI stack. Key themes included:
- *Housekeeping & history management* on Ask Discourse  
- *Answer reliability*, with calls to eliminate “hallucinated” links  
- *Retrospective spam cleanup* using AI  
- Provider-specific configuration fixes in the core #ai plugin  
- Challenges in *self-hosting sentiment/emotion* models on CPU  
- A #Bug in the admin usage page’s custom date-range UI  
- A minor #UX enhancement converting the AI icon to a link  
- Expanded translator support via LLM providers  
- An emerging *Model Context Protocol* initiative  
- A bug where the Proofread helper unintentionally alters quoted text  

---

## Interesting Topics
- **Improve managing history on Ask Discourse** (#Feature, #ai, #ask-discourse)  
  <a class="mention" href="/u/jrgong">jrgong</a> requested the ability to delete/archive Ask conversations in [post 1](https://meta.discourse.org/t/-/378924/1?silent=true), <a class="mention" href="/u/mcwumbly">mcwumbly</a> suggested surfacing search/bookmarks in [post 2](https://meta.discourse.org/t/-/378924/2?silent=true) and pointed to a sidebar search prototype in [post 3](https://meta.discourse.org/t/-/378924/3?silent=true), while <a class="mention" href="/u/sam">sam</a> proposed emulating ChatGPT’s delete-conversation UI in [post 4](https://meta.discourse.org/t/-/378924/4?silent=true).

- **Feedback for Ask Discourse returning invalid links** (#Feature, #feedback, #ai, #ask-discourse)  
  <a class="mention" href="/u/one1">one1</a> highlighted AI answers linking to non-existent posts in [post 8](https://meta.discourse.org/t/-/336805/8?silent=true); <a class="mention" href="/u/Canapin">Canapin</a> confirmed the issue in [post 10](https://meta.discourse.org/t/-/336805/10?silent=true); <a class="mention" href="/u/one1">one1</a> proposed validating links against actual posts in [post 11](https://meta.discourse.org/t/-/336805/11?silent=true); <a class="mention" href="/u/mcwumbly">mcwumbly</a> urged flagging poor results in [post 12](https://meta.discourse.org/t/-/336805/12?silent=true); <a class="mention" href="/u/Lee_Ars">Lee_Ars</a> praised the overall flow in [post 13](https://meta.discourse.org/t/-/336805/13?silent=true); <a class="mention" href="/u/NateDhaliwal">NateDhaliwal</a> compared to AI Search in [post 14](https://meta.discourse.org/t/-/336805/14?silent=true); and <a class="mention" href="/u/sam">sam</a> revisited Ask history controls in [post 15](https://meta.discourse.org/t/-/336805/15?silent=true).

- **Spam: Retroactively get AI to review recent posts and delete spam** (#Sysadmins, #ai, #spam)  
  <a class="mention" href="/u/pfaffman">pfaffman</a> detailed a Rails-based workflow to flag/remove ~30 spam posts/hour by running AI over a backup site in [post 1](https://meta.discourse.org/t/-/378956/1?silent=true).

- **Discourse AI Azure endpoint missing settings** (#Plugin, #official, #included-in-core, #ai)  
  <a class="mention" href="/u/Roman">Roman</a> noted Falco’s fix covers both Azure/OpenAI in [post 233](https://meta.discourse.org/t/-/259214/233?silent=true); <a class="mention" href="/u/ozkn">ozkn</a> found the setting still absent after choosing Azure in [post 234](https://meta.discourse.org/t/-/259214/234?silent=true); and Roman merged provider-specific options in [post 235](https://meta.discourse.org/t/-/259214/235?silent=true).

- **Self-Hosting Sentiment and Emotion for DiscourseAI** (#Self-Hosting, #ai, #ai-sentiment)  
  <a class="mention" href="/u/Lee_Ars">Lee_Ars</a> hit a CPU-only EC2 brick wall loading HF models in [post 8](https://meta.discourse.org/t/-/334451/8?silent=true), and <a class="mention" href="/u/sam">sam</a> confirmed plans to offload sentiment analysis to LLMs like Gemini Flash in [post 9](https://meta.discourse.org/t/-/334451/9?silent=true).

- **Discourse AI admin usage page – custom date range issues** (#Bug, #ai)  
  <a class="mention" href="/u/Lilly">Lilly</a> demonstrated that selecting off-current date ranges requires two refreshes to render correct metrics in [post 1](https://meta.discourse.org/t/-/378959/1?silent=true).

- **Change AI Bot Icon to Link Element** (#Feature, #ai, #ai-bot, #completed)  
  <a class="mention" href="/u/maiki">maiki</a> thanked <a class="mention" href="/u/awesomerobot">awesomerobot</a> for PR #98d594a moving the icon into a link in [post 3](https://meta.discourse.org/t/-/377435/3?silent=true), confirmed in [post 5](https://meta.discourse.org/t/-/377435/5?silent=true).

- **Allow LLM providers for discourse-translate plugin** (#translator, #completed, #ai)  
  <a class="mention" href="/u/sam">sam</a> announced completion of LLM-backed translation support in [post 6](https://meta.discourse.org/t/-/319383/6?silent=true) and pointed to the new localization hub.

- **Official Discourse Model Context Protocol (MCP)** (#Feature, #ai)  
  <a class="mention" href="/u/sam">sam</a> launched the MCP repo in [post 18](https://meta.discourse.org/t/-/364859/18?silent=true), with <a class="mention" href="/u/EricGT">EricGT</a> urging stars and review in [post 19](https://meta.discourse.org/t/-/364859/19?silent=true).

- **Proofread breaks quotes** (#Bug, #pr-welcome, #ai, #ai-helper)  
  <a class="mention" href="/u/bksubhuti">bksubhuti</a> reported quoted text getting rewritten in [post 6](https://meta.discourse.org/t/-/365102/6?silent=true); <a class="mention" href="/u/sam">sam</a> labeled it a bug and added #pr-welcome in [post 7](https://meta.discourse.org/t/-/365102/7?silent=true) & [post 8](https://meta.discourse.org/t/-/365102/8?silent=true); and <a class="mention" href="/u/Jagster">Jagster</a> weighed scope in [post 9](https://meta.discourse.org/t/-/365102/9?silent=true).

---

## Activity
- <a class="mention" href="/u/jrgong">jrgong</a> contributed to [Improve managing history on Ask Discourse](https://meta.discourse.org/t/-/378924/1?silent=true) and [AI bot - Personas](https://meta.discourse.org/t/-/306099/17?silent=true).  
- <a class="mention" href="/u/mcwumbly">mcwumbly</a> engaged in [Improve managing history on Ask Discourse](https://meta.discourse.org/t/-/378924/2?silent=true), [sidebar search proto](https://meta.discourse.org/t/-/378924/3?silent=true), and [feedback for Ask Discourse](https://meta.discourse.org/t/-/336805/12?silent=true).  
- <a class="mention" href="/u/sam">sam</a> posted in [Improve managing history on Ask Discourse](https://meta.discourse.org/t/-/378924/4?silent=true), [feedback for Ask Discourse](https://meta.discourse.org/t/-/336805/15?silent=true), [Self-Hosting Sentiment](https://meta.discourse.org/t/-/334451/9?silent=true), [admin API for AI artifacts](https://meta.discourse.org/t/-/371297/8?silent=true), [MCP repo kickoff](https://meta.discourse.org/t/-/364859/18?silent=true), [Proofread breaks quotes](https://meta.discourse.org/t/-/365102/7?silent=true), [Proofread teardown](https://meta.discourse.org/t/-/365102/8?silent=true), and [persona engineering tips](https://meta.discourse.org/t/-/376342/9?silent=true).  
- <a class="mention" href="/u/pfaffman">pfaffman</a> shared the AI spam cleanup workflow in [Spam review & delete](https://meta.discourse.org/t/-/378956/1?silent=true).  
- <a class="mention" href="/u/one1">one1</a> filed AI link bugs in [feedback for Ask Discourse](https://meta.discourse.org/t/-/336805/8?silent=true) and [invalid link proposal](https://meta.discourse.org/t/-/336805/11?silent=true).  
- <a class="mention" href="/u/Lee_Ars">Lee_Ars</a> tested AI results in [feedback for Ask Discourse](https://meta.discourse.org/t/-/336805/13?silent=true) and self-hosted sentiment in [Self-Hosting Sentiment](https://meta.discourse.org/t/-/334451/8?silent=true).  
- <a class="mention" href="/u/Lilly">Lilly</a> reported the admin usage date-range bug in [custom range issues](https://meta.discourse.org/t/-/378959/1?silent=true).  
- <a class="mention" href="/u/maiki">maiki</a> confirmed the AI icon link change in [AI Bot Icon PR](https://meta.discourse.org/t/-/377435/3?silent=true).  
- <a class="mention" href="/u/awesomerobot">awesomerobot</a> merged the AI bot link tweak in [AI Bot Icon](https://meta.discourse.org/t/-/377435/5?silent=true).  
- <a class="mention" href="/u/ozkn">ozkn</a> diagnosed missing Azure settings in [Discourse AI plugin](https://meta.discourse.org/t/-/259214/234?silent=true).  
- <a class="mention" href="/u/Roman">Roman</a> updated provider options in [Discourse AI plugin](https://meta.discourse.org/t/-/259214/233?silent=true) and merged fixes in [provider-specific PR](https://meta.discourse.org/t/-/259214/235?silent=true).  
- <a class="mention" href="/u/EricGT">EricGT</a> called for stars & support in [MCP repo](https://meta.discourse.org/t/-/364859/19?silent=true).  
- <a class="mention" href="/u/bksubhuti">bksubhuti</a> opened the Proofread-quote bug in [post 6](https://meta.discourse.org/t/-/365102/6?silent=true).  
- <a class="mention" href="/u/Jagster">Jagster</a> debated quoted-text scope in [post 9](https://meta.discourse.org/t/-/365102/9?silent=true).  
- <a class="mention" href="/u/NateDhaliwal">NateDhaliwal</a> requested PM deletion rights in [feedback for Ask Discourse](https://meta.discourse.org/t/-/336805/14?silent=true).  
- <a class="mention" href="/u/Canapin">Canapin</a> echoed link-hallucination issues in [feedback for Ask Discourse](https://meta.discourse.org/t/-/336805/10?silent=true).  
- <a class="mention" href="/u/pi_dwg">pi_dwg</a> briefly posted in [Content Localization & Automatic Translations](https://meta.discourse.org/t/-/370969/14?silent=true).

Thanks for reading, and I'll see you again next week! :)
83 
## Overview

Over the past week, the #meta.discourse.org AI category saw **lively discussions** across three broad areas:

1. **New and evolving features** – from the community-driven design of a Discourse Model Context Protocol ([MCP](https://meta.discourse.org/t/-/364859/20?silent=true)) to improvements in ask.discourse history management and AI-driven content localization.  
2. **Plugin innovation** – with the release of a customizable summary-gist plugin and ongoing work around AI bot personas, PDF support, and potential persistent memory enhancements.  
3. **Bug fixes and stability** – several #Bug reports addressed AI spam misclassifications, embedding toggle errors, and a critical 500 Internal Server Error during manual AI configuration.

Below are the **10 most interesting topics** from August 18–25, followed by a breakdown of **who posted where**.

---

## Interesting Topics

- **[Is there an official Discourse Model Context Protocol (MCP)?](https://meta.discourse.org/t/-/364859/20?silent=true)**  
  In this #Feature #ai thread, <a class="mention" href="/u/sam">sam</a> kicked things off on August 18 with a request for MCP use-cases ([post 20](https://meta.discourse.org/t/-/364859/20?silent=true)). <a class="mention" href="/u/MachineScholar">MachineScholar</a> outlined an open-source cognitive agent desire ([post 21](https://meta.discourse.org/t/-/364859/21?silent=true)), while <a class="mention" href="/u/EricGT">EricGT</a> proposed “chat-with-forum” and morning briefs ([post 22](https://meta.discourse.org/t/-/364859/22?silent=true)). <a class="mention" href="/u/jrgong">jrgong</a> requested dev-centric MCP docs ([post 23](https://meta.discourse.org/t/-/364859/23?silent=true)), and <a class="mention" href="/u/sam">sam</a> published initial MCP configs on GitHub ([post 24](https://meta.discourse.org/t/-/364859/24?silent=true), [post 25](https://meta.discourse.org/t/-/364859/25?silent=true)), then clarified fall-back behavior ([post 27](https://meta.discourse.org/t/-/364859/27?silent=true)).

- **[What is stopping you from trying out Discourse AI?](https://meta.discourse.org/t/-/306059/32?silent=true)**  
  In this #Community #ai discussion, <a class="mention" href="/u/eisammy">eisammy</a> asked about model learning and caching ([post 32](https://meta.discourse.org/t/-/306059/32?silent=true)), <a class="mention" href="/u/sam">sam</a> clarified that Discourse AI doesn’t train on forum data ([post 33](https://meta.discourse.org/t/-/306059/33?silent=true)), and <a class="mention" href="/u/Lee_Ars">Lee_Ars</a> shared cost-tracking and trust concerns ([post 35](https://meta.discourse.org/t/-/306059/35?silent=true), [post 38](https://meta.discourse.org/t/-/306059/38?silent=true), [post 40](https://meta.discourse.org/t/-/306059/40?silent=true)). 

- **[AI spam bot says it is not spam but scan log says it is spam](https://meta.discourse.org/t/-/379375/1?silent=true)**  
  A #Bug #ai report by <a class="mention" href="/u/J-Ha_Hasegawa">J-Ha_Hasegawa</a> detailed a spam post passing through despite a “SPAM” scan log ([post 1](https://meta.discourse.org/t/-/379375/1?silent=true)). <a class="mention" href="/u/Roman">Roman</a> diagnosed TL and test-code issues ([post 2](https://meta.discourse.org/t/-/379375/2?silent=true)), pushed a fix in PR 34442, and clarified post-skip conditions ([post 5](https://meta.discourse.org/t/-/379375/5?silent=true), [post 8](https://meta.discourse.org/t/-/379375/8?silent=true)). After using a TL0 account, <a class="mention" href="/u/J-Ha_Hasegawa">J-Ha_Hasegawa</a> confirmed it now works as expected ([post 9](https://meta.discourse.org/t/-/379375/9?silent=true)).

- **[AI bot – Personas](https://meta.discourse.org/t/-/306099/18?silent=true)**  
  Under #Site Management #how-to #ai #ai-bot, <a class="mention" href="/u/jrgong">jrgong</a> hit a 100-post limit ([post 18](https://meta.discourse.org/t/-/306099/18?silent=true)), <a class="mention" href="/u/MachineScholar">MachineScholar</a> suggested the Forum Researcher persona ([post 19](https://meta.discourse.org/t/-/306099/19?silent=true)), and <a class="mention" href="/u/sam">sam</a> recommended switching personas for image and author-filter use cases ([post 21](https://meta.discourse.org/t/-/306099/21?silent=true), [post 23](https://meta.discourse.org/t/-/306099/23?silent=true)). <a class="mention" href="/u/jrgong">jrgong</a> also proposed a “read only topic owner” checkbox ([post 24](https://meta.discourse.org/t/-/306099/24?silent=true)).

- **[Custom Summary Gist](https://meta.discourse.org/t/-/380060/1?silent=true)**  
  In this #Plugin #ai announcement, <a class="mention" href="/u/Lhc_fl">Lhc_fl</a> introduced a plugin to customize AI summary blocks ([post 1](https://meta.discourse.org/t/-/380060/1?silent=true)), linking to <https://github.com/Lhcfl/discourse-custom-summary-gist> and noting dependency on [Summarize – Gists](https://meta.discourse.org/t/summarize-gists/340269), with an install guide at [How to install plugins in Discourse](https://meta.discourse.org/t/install-plugins-in-discourse/19157).

- **[Impossible to disable AI embeddings when models have been removed](https://meta.discourse.org/t/-/380088/1?silent=true)**  
  A #Bug #ai report by <a class="mention" href="/u/RGJ">RGJ</a> showed an error when toggling off embeddings without a selected model ([post 1](https://meta.discourse.org/t/-/380088/1?silent=true)). <a class="mention" href="/u/sam">sam</a> tagged <a class="mention" href="/u/Roman">Roman</a> for a quick look ([post 2](https://meta.discourse.org/t/-/380088/2?silent=true)), and <a class="mention" href="/u/Roman">Roman</a> investigated config validations in [embeddings_module_validator.rb](https://github.com/discourse/discourse/blob/main/plugins/discourse-ai/lib/configuration/embeddings_module_validator.rb#L10) ([post 3](https://meta.discourse.org/t/-/380088/3?silent=true)).

- **[Content Localization – Manual and Automatic with Discourse AI](https://meta.discourse.org/t/-/370969/15?silent=true)**  
  Under #Site Management #ai #content-localization, <a class="mention" href="/u/tvavrda">tvavrda</a> noted untranslated sidebar docs and unexpected auto-switching ([post 15](https://meta.discourse.org/t/-/370969/15?silent=true)), <a class="mention" href="/u/sam">sam</a> assigned <a class="mention" href="/u/nat">nat</a> to track sidebar translations ([post 16](https://meta.discourse.org/t/-/370969/16?silent=true)), and <a class="mention" href="/u/nat">nat</a> linked a related feature topic on user-bio translations ([post 17](https://meta.discourse.org/t/show-translated-user-bios/378908?silent=true)). <a class="mention" href="/u/tvavrda">tvavrda</a> shared a video and further edge cases ([post 18](https://meta.discourse.org/t/-/370969/18?silent=true), [post 19](https://meta.discourse.org/t/-/370969/19?silent=true)), and <a class="mention" href="/u/nat">nat</a> pointed to outdated-translation indicators ([post 20](https://meta.discourse.org/t/-/370969/20?silent=true), [post 21](https://meta.discourse.org/t/-/370969/21?silent=true)).

- **[Improve managing history on Ask discourse](https://meta.discourse.org/t/-/378924/5?silent=true)**  
  In this #Feature #ai #ask-discourse topic, <a class="mention" href="/u/awesomerobot">awesomerobot</a> reported progress porting Ask’s custom implementation over to `/discourse-ai/ai-bot/conversations` ([post 5](https://meta.discourse.org/t/-/378924/5?silent=true)), referencing PR 28 on GitHub (https://github.com/discourse/discourse-ask-theme/pull/28), the unified conversations sidebar, and the existing [ask-discourse tag](https://meta.discourse.org/tag/ask-discourse).

- **[PDF support in Discourse AI](https://meta.discourse.org/t/-/352829/19?silent=true)**  
  Under #Site Management #how-to #ai, <a class="mention" href="/u/MachineScholar">MachineScholar</a> asked about RAG “chat-with-your-PDFs” support ([post 19](https://meta.discourse.org/t/-/352829/19?silent=true)), referenced Sam’s earlier “wait a few more weeks” advice ([post 5](https://meta.discourse.org/t/-/352829/5?silent=true)), and posted additional details on upload limits ([post 20](https://meta.discourse.org/t/-/352829/20?silent=true)).

- **[Internal Server Error 500 – Manual configuration [ Discourse AI]](https://meta.discourse.org/t/-/379557/1?silent=true)**  
  In this #Support #ai case, <a class="mention" href="/u/viswanatha">viswanatha</a> reported a 500 error when setting up Manual LLMs ([post 1](https://meta.discourse.org/t/-/379557/1?silent=true)). <a class="mention" href="/u/Roman">Roman</a> suggested checking `/logs` and API key quirks ([post 2](https://meta.discourse.org/t/-/379557/2?silent=true)), and <a class="mention" href="/u/viswanatha">viswanatha</a> shared an error trace pointing to `chat_gpt.rb` ([post 3](https://meta.discourse.org/t/-/379557/3?silent=true)), with code available in [chat_gpt.rb on GitHub](https://github.com/discourse/discourse/blob/main/plugins/discourse-ai/lib/completions/dialects/chat_gpt.rb).

---

## Activity

Below is a rundown of **who posted where** from August 18–25 (all links include `?silent=true`):

- <a class="mention" href="/u/sam">sam</a> (9 posts, 21 likes) contributed to:  
  • [MCP Protocol](https://meta.discourse.org/t/-/364859/20?silent=true), [24](https://meta.discourse.org/t/-/364859/24?silent=true), [25](https://meta.discourse.org/t/-/364859/25?silent=true), [27](https://meta.discourse.org/t/-/364859/27?silent=true)  
  • [Discourse AI adoption](https://meta.discourse.org/t/-/306059/33?silent=true)  
  • [AI bot Personas](https://meta.discourse.org/t/-/306099/21?silent=true), [23](https://meta.discourse.org/t/-/306099/23?silent=true)  
  • [Content Localization](https://meta.discourse.org/t/-/370969/16?silent=true)  
  • [AI embeddings toggle bug](https://meta.discourse.org/t/-/380088/2?silent=true)

- <a class="mention" href="/u/jrgong">jrgong</a> (5 posts, 9 likes) participated in:  
  • [MCP Protocol](https://meta.discourse.org/t/-/364859/23?silent=true)  
  • [AI bot Personas](https://meta.discourse.org/t/-/306099/18?silent=true), [20](https://meta.discourse.org/t/-/306099/20?silent=true), [22](https://meta.discourse.org/t/-/306099/22?silent=true), [24](https://meta.discourse.org/t/-/306099/24?silent=true)

- <a class="mention" href="/u/Roman">Roman</a> (5 posts, 8 likes) helped resolve:  
  • [AI spam bot issue](https://meta.discourse.org/t/-/379375/2?silent=true), [5](https://meta.discourse.org/t/-/379375/5?silent=true), [8](https://meta.discourse.org/t/-/379375/8?silent=true)  
  • [AI embeddings bug](https://meta.discourse.org/t/-/380088/3?silent=true)  
  • [500 Error debug](https://meta.discourse.org/t/-/379557/2?silent=true)

- <a class="mention" href="/u/Lee_Ars">Lee_Ars</a> (3 posts, 8 likes) shared insights in [Discourse AI adoption](https://meta.discourse.org/t/-/306059/35?silent=true), [38](https://meta.discourse.org/t/-/306059/38?silent=true), [40](https://meta.discourse.org/t/-/306059/40?silent=true).

- <a class="mention" href="/u/Lhc_fl">Lhc_fl</a> (1 post, 7 likes) unveiled [Custom Summary Gist](https://meta.discourse.org/t/-/380060/1?silent=true).

- <a class="mention" href="/u/nat">nat</a> (3 posts, 3 likes) tracked localization: [370969/17](https://meta.discourse.org/t/show-translated-user-bios/378908?silent=true), [370969/20](https://meta.discourse.org/t/-/370969/20?silent=true), and supported [Translator summaries](https://meta.discourse.org/t/-/380067/2?silent=true).

- <a class="mention" href="/u/J-Ha_Hasegawa">J-Ha_Hasegawa</a> (4 posts, 3 likes) tested AI spam handling in [379375/1](https://meta.discourse.org/t/-/379375/1?silent=true), [4](https://meta.discourse.org/t/-/379375/4?silent=true), [6](https://meta.discourse.org/t/-/379375/6?silent=true), [9](https://meta.discourse.org/t/-/379375/9?silent=true).

- <a class="mention" href="/u/RGJ">RGJ</a> (1 post, 3 likes) reported [AI embeddings toggle bug](https://meta.discourse.org/t/-/380088/1?silent=true).

- <a class="mention" href="/u/awesomerobot">awesomerobot</a> (1 post, 3 likes) updated Ask.discourse history via [378924/5](https://meta.discourse.org/t/-/378924/5?silent=true).

- <a class="mention" href="/u/tvavrda">tvavrda</a> (3 posts, 3 likes) surfaced localization edge cases in [370969/15](https://meta.discourse.org/t/-/370969/15?silent=true), [18](https://meta.discourse.org/t/-/370969/18?silent=true), [19](https://meta.discourse.org/t/-/370969/19?silent=true).

- <a class="mention" href="/u/BrianC">BrianC</a> (1 post) inquired about [AI persistent memory](https://meta.discourse.org/t/-/380054/1?silent=true).

- <a class="mention" href="/u/viswanatha">viswanatha</a> (2 posts) debugged a 500 error in [379557/1](https://meta.discourse.org/t/-/379557/1?silent=true) and [379557/3](https://meta.discourse.org/t/-/379557/3?silent=true).

- <a class="mention" href="/u/MachineScholar">MachineScholar</a> (4 posts) explored MCP use-cases ([364859/21](https://meta.discourse.org/t/-/364859/21?silent=true)), PDF support ([352829/19](https://meta.discourse.org/t/-/352829/19?silent=true), [352829/20](https://meta.discourse.org/t/-/352829/20?silent=true)), and bot personas ([306099/19](https://meta.discourse.org/t/-/306099/19?silent=true)).

- <a class="mention" href="/u/jimkleiber">jimkleiber</a> (1 post) asked about extending the gist plugin at [380060/2](https://meta.discourse.org/t/-/380060/2?silent=true).

---

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

Overview

Over the past week, the content-localization and ai tags have seen the most engagement on Meta. Tordanik kicked off a lively debate on translation fidelity in Multilingual user feedback on Automatic Translations, prompting hellekin and tvavrda to share real-world concerns about cultural nuance loss. sam unveiled Google’s new multi-modal LLM in Gemini Flash 2.5 Image - now on Discourse, complete with demos and setup tips. Core contributors Jagster and nat traced UI inconsistencies in AI setting tells translations are disabled when enabled and Ai自定义提示如何给用户使用, while Moin provided essential workarounds for custom AI prompts and Android tablet quirks in AI helper hiding on Android tablets. Administrators also refined moderation tools in Discourse AI - Spam detection and experimented with ai-bot continuity in Discourse AI persistent memory. Self-hosters wrestled with ai-sentiment models in Self-Hosting Sentiment and Emotion for DiscourseAI, and the flagship announcement Content Localization and Automatic Translations for Your Community was officially archived.

Interesting Topics

Activity

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

85

Visão Geral

Esta semana no Meta Discourse, os recursos de IA continuaram a evoluir em fluxos de trabalho de marcação, integração de modelos, pesquisa, localização e moderação. A discussão sobre marcação automatizada em Usando IA para Marcar e Categorizar Posts de Fórum destacou melhorias potenciais com embeddings (#Suporte ai), enquanto um mergulho profundo em LLMs Personalizados - Exceção de Job lançou luz sobre incompatibilidades de persona-ferramenta e tratamento de erros (#Suporte ai). Conversas sobre as melhores práticas de detecção de spam e triagem, incluindo a evitação de marcações duplas, foram levantadas em Melhores práticas para antispam de IA mais triagem de posts de IA operando juntas? (#Suporte ai #moderação). Enquanto isso, prévias de recursos como Pesquisa de IA Conversacional chegando ao Discourse AI demonstraram soluços iniciais com visibilidade de fonte e contagem de requisições (#Recurso ai-search). Na frente de gerenciamento de site, os usuários avaliaram o custo e o fluxo de trabalho de Localização de Conteúdo - Manual e Automática com Discourse AI e compartilharam experiências de tradução (#Gerenciamento de Site ai content-localization). Finalmente, ferramentas de IA legadas como análise de sentimento e legendagem automática viram novos relatórios de bugs em Discourse AI - Sentimento e Helper - Legenda Automática (#Gerenciamento de Site ai).

Tópicos Interessantes

Atividade

Obrigado pela leitura, e nos vemos na próxima semana! :slight_smile:

86

Visão Geral

Os destaques desta semana incluem uma proposta para expandir o scanner de spam de IA com detecção de número de telefone em Devemos dizer ao scanner de spam de IA para sinalizar postagens contendo números de telefone por padrão? spam, o refinamento da verificação O modelo LLM padrão é necessário antes de habilitar o “Chat”? Bug content-localization, um debate renovado sobre um Protocolo de Contexto de Modelo oficial do Discourse (MCP) Feature ai, uma correção crítica para Persona de IA do Discourse, suporte para upload Announcements ai-bot, e a resolução completa de Preenchimento de tradução de IA não funcionando após todas as configurações configuradas Support content-localization.

Tópicos Interessantes

Atividade

  • \u003ca class="mention" href="/u/awesomerobot"\u003eawesomerobot\u003c/a\u003e (2 postagens, 3 curtidas) contribuiu para a discussão do filtro de spam de número de telefone na postagem um e postagem três.
  • \u003ca class="mention" href="/u/pfaffman"\u003epfaffman\u003c/a\u003e (2 postagens, 2 curtidas) participou na postagem dois e postagem quatro.
  • \u003ca class="mention" href="/u/nat"\u003enat\u003c/a\u003e (2 postagens, 1 curtida) interveio na verificação do LLM padrão na postagem três e compartilhou diagnósticos para preenchimento de tradução na postagem dezesseis.
  • \u003ca class="mention" href="/u/jrgong"\u003ejrgong\u003c/a\u003e (1 postagem, 1 curtida) comentou sobre MCP na postagem vinte e oito.
  • \u003ca class="mention" href="/u/Falco"\u003eFalco\u003c/a\u003e (1 postagem, 1 curtida) sugeriu remover a verificação de LLM na postagem quatro.
  • \u003ca class="mention" href="/u/GrahamM"\u003eGrahamM\u003c/a\u003e (3 postagens, 1 curtida) impulsionou a solução de problemas de preenchimento de tradução na postagem dez, postagem doze e postagem quatorze.
  • \u003ca class="mention" href="/u/kiefferr"\u003ekiefferr\u003c/a\u003e (1 postagem, 1 curtida) relatou o problema de upload da Persona de IA na postagem vinte e cinco.
  • \u003ca class="mention" href="/u/tpetrov"\u003etpetrov\u003c/a\u003e (1 postagem, 0 curtidas) explorou a mecânica RAG na postagem três.
  • \u003ca class="mention" href="/u/RGJ"\u003eRGJ\u003c/a\u003e (2 postagens, 0 curtidas) investigou as configurações de tradução na postagem oito e verificações de log na postagem treze.
  • \u003ca class="mention" href="/u/Jagster"\u003eJagster\u003c/a\u003e (1 postagem, 0 curtidas) compartilhou notas de desempenho do GPT-5 na postagem quinze.

Obrigado por ler, e nos vemos novamente na próxima semana! :slight_smile:

87

Resumo Semanal de Atividade de IA (15/09/2025 – 22/09/2025)

Visão Geral

As discussões desta semana em meta.discourse.org focaram em aprimorar a localização de conteúdo, correções de bugs em recursos com IA e novos fluxos de trabalho para assistentes de IA. Vimos depuração mais aprofundada em Localização de Conteúdo - Manual e Automática com Discourse AI através de logs detalhados, uma proposta para um botão imediato de “Traduzir Agora” para contornar o estrangulamento, e planejamento para traduções de tags e notificações por e-mail nos idiomas dos usuários. Ao mesmo tempo, vários relatórios de Bug — especialmente em torno de vídeos do YouTube em traduções de IA e notificações de cota do plugin de automação — foram triados, e as melhores práticas para antispam e triagem de IA foram refinadas.

Tópicos Interessantes

  • Em Localização de Conteúdo – Manual e Automática com Discourse AI, \u003ca class="mention" href="/u/asa"\u003easa\u003c/a\u003e relatou que o contador de posts traduzidos permaneceu travado em 52; \u003ca class="mention" href="/u/nat"\u003enat\u003c/a\u003e recomendou habilitar SiteSetting.ai_translation_verbose_logs = true para exibir erros de detecção de localidade e retomar o preenchimento retroativo. #localizacao-de-conteudo #gerenciamento-de-site
  • \u003ca class="mention" href="/u/nat"\u003enat\u003c/a\u003e abriu Adicionar botão “Traduzir Agora” visível para grupos permitidos para traduções desatualizadas, capturando vários pedidos (de \u003ca class="mention" href="/u/carlh-foa"\u003ecarlh-foa\u003c/a\u003e e \u003ca class="mention" href="/u/Don"\u003eDon\u003c/a\u003e) para forçar re-traduções imediatas além do limite padrão de duas vezes ao dia. #Recurso #ia #localizacao-de-conteudo
  • \u003ca class="mention" href="/u/asa"\u003easa\u003c/a\u003e descreveu em Vídeos do YouTube não são incorporados em traduções de IA que vídeos incorporados se tornam links simples após a tradução; \u003ca class="mention" href="/u/Falco"\u003eFalco\u003c/a\u003e reconheceu que é um problema conhecido e que o trabalho está em andamento. Bug #ia #localizacao-de-conteudo
  • Em Traduzir Tags, \u003ca class="mention" href="/u/asa"\u003easa\u003c/a\u003e observou que as tags não são traduzidas automaticamente, e \u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e confirmou que a localização de tags é “uma das últimas peças do quebra-cabeça” no roteiro. #Recurso #ia #localizacao
  • \u003ca class="mention" href="/u/tvavrda"\u003etvavrda\u003c/a\u003e levantou Usar posts traduzidos ao enviar e-mails para usuários com o idioma do usuário definido, apontando que as notificações por e-mail ainda são padrão em inglês; \u003ca class="mention" href="/u/nat"\u003enat\u003c/a\u003e verificou que não está implementado e está programado para uma atualização futura. #Recurso #ia #localizacao-de-conteudo
  • \u003ca class="mention" href="/u/asa"\u003easa\u003c/a\u003e descobriu em Tradução de TOS e outros tópicos do sistema que posts gerados pelo sistema ou bot (como TOS) não são traduzidos automaticamente; \u003ca class="mention" href="/u/Falco"\u003eFalco\u003c/a\u003e explicou que estes são ignorados e requerem traduções manuais com ícone de globo. #Suporte #tradutor #ia
  • Em As respostas de IA geradas pelo plugin de automação não notificam o usuário quando a cota é esgotada, \u003ca class="mention" href="/u/kuaza"\u003ekuaza\u003c/a\u003e relatou alertas ausentes de “cota esgotada” em respostas de automação, levando a discussões sobre fallback para modelos gratuitos e notificações de usuários. Bug #automacao #ia
  • \u003ca class="mention" href="/u/kuaza"\u003ekuaza\u003c/a\u003e também encontrou Llm_tagger: Falha ao analisar a resposta JSON para o post … caractere inesperado, e \u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e sinalizou a necessidade de melhorias na sanitização de JSON e ajustes de prompt. Bug #automacao #ia
  • Em Melhores práticas para antispam de IA e triagem de posts de IA operando juntas?, \u003ca class="mention" href="/u/Lee_Ars"\u003eLee_Ars\u003c/a\u003e e \u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e debateram se devem sequenciar ou combinar personas de antispam e triagem para evitar sinalizações conflitantes. #Suporte #ia
  • \u003ca class="mention" href="/u/Falco"\u003eFalco\u003c/a\u003e atualizou Pesquisa de IA Conversacional chegando ao Discourse AI, observando o trabalho retomado em uma persona padrão para corrigir a visibilidade de respostas branco sobre branco e atingir limites de chamadas de ferramentas. #Recurso #busca-ia

Atividade

Obrigado pela leitura, e nos vemos novamente na próxima semana! :slight_smile:

88 
## Visão Geral

Na semana passada, em #ai e #content-localization, houve uma enxurrada de discussões sobre a melhoria de recursos impulsionados por IA, desde o refinamento de sugestões de tópicos e traduções até o fortalecimento de ferramentas de automação. O debate sobre links "Sugeridos vs. Relacionados", iniciado por <a class="mention" href="/u/tobiaseigen">tobiaseigen</a> em [Do we want to tweak "suggested" and "Related" links at bottom of posts?](https://meta.discourse.org/t/-/384030/1?silent=true), gerou várias melhorias na pontuação de relevância e nos fluxos de trabalho de curadoria manual. Aprimoramentos de tradução estiveram em destaque, com <a class="mention" href="/u/nat">nat</a> implementando um [Add "Translate Now" button visible to allowed groups](https://meta.discourse.org/t/-/383544/3?silent=true), enquanto casos de borda de localização surgiram em [Discourse AI translations bug？](https://meta.discourse.org/t/-/384214/1?silent=true), solicitando diagnósticos mais profundos. Na frente de automação, problemas de análise de JSON em [llm_tagger: Failed to parse JSON response…](https://meta.discourse.org/t/-/383444/5?silent=true) foram resolvidos, e membros da comunidade traçaram as melhores práticas para integrar LLMs — seja via llms.txt ([ref](https://meta.discourse.org/t/-/383088/1?silent=true)) ou configuração manual de plugin ([Setup Inquiry: AI Summarization…](https://meta.discourse.org/t/-/383836/1?silent=true)).

---

## Tópicos Interessantes

- <a class="mention" href="/u/tobiaseigen">tobiaseigen</a> iniciou um tópico em [Do we want to tweak "suggested" and "Related" links at bottom of posts?](https://meta.discourse.org/t/-/384030/1?silent=true) explorando se novos usuários deveriam ver sugestões geradas por IA. <a class="mention" href="/u/jenmck">jenmck</a> defendeu a curadoria manual [ref](https://meta.discourse.org/t/-/384030/3?silent=true), enquanto <a class="mention" href="/u/Falco">Falco</a> ajustou a penalidade de idade em tópicos mais antigos para melhorar a relevância [ref](https://meta.discourse.org/t/-/384030/5?silent=true).

- <a class="mention" href="/u/nat">nat</a> entregou um aprimoramento de UX adicionando um botão [“Translate Now” button visible to allowed groups](https://meta.discourse.org/t/-/383544/3?silent=true), dando aos content_localization_allowed_groups controle de tradução com um clique.

- Em #automation, <a class="mention" href="/u/awesomerobot">awesomerobot</a> e <a class="mention" href="/u/kuaza">kuaza</a> lidaram com [llm_tagger: Failed to parse JSON response…](https://meta.discourse.org/t/-/383444/5?silent=true). Eles refinaram o esquema JSON — movendo tags para arrays [ref](https://meta.discourse.org/t/-/383444/7?silent=true) e isolando a confiança como um inteiro [ref](https://meta.discourse.org/t/-/383444/9?silent=true).

- <a class="mention" href="/u/dennisjbr">dennisjbr</a> propôs indexar ativos não-HTML em [Index File Contents for Search](https://meta.discourse.org/t/-/31884/10?silent=true) para desbloquear a pesquisa de texto completo de PDF e imagens via Postgres.

- Para auxiliar os crawlers de LLM, <a class="mention" href="/u/fzngagan">fzngagan</a> ilustrou como [Add llms.txt to your site](https://meta.discourse.org/t/-/383088/1?silent=true) usando tópicos privados e permalinks personalizados.

- No mobile, <a class="mention" href="/u/NateDhaliwal">NateDhaliwal</a> sinalizou que o botão [AI Gists button shown for PMs, but with no summary text](https://meta.discourse.org/t/-/384243/1?silent=true) aparece, mas não renderiza gists [ref](https://meta.discourse.org/t/-/384243/2?silent=true), solicitando mais diagnósticos de UI.

- <a class="mention" href="/u/昊毅_周">昊毅_周</a> descobriu um [Discourse AI translations bug？](https://meta.discourse.org/t/-/384214/1?silent=true) onde descrições de categorias criadas pelo sistema foram mal detectadas como inglês. <a class="mention" href="/u/nat">nat</a> recomendou uma consulta no explorador de dados para auditoria de locale [ref](https://meta.discourse.org/t/-/384214/10?silent=true) e alternâncias manuais de locale [ref](https://meta.discourse.org/t/-/384214/9?silent=true).

- <a class="mention" href="/u/S.AAKASH_MUTHIAH">S.AAKASH_MUTHIAH</a> lançou uma [Setup Inquiry: AI Summarization in Discourse & LLM Integration](https://meta.discourse.org/t/-/383836/1?silent=true), com <a class="mention" href="/u/NateDhaliwal">NateDhaliwal</a> guiando para a documentação do plugin [ref](https://meta.discourse.org/t/-/383836/2?silent=true) e dicas de configuração manual de LLM [ref](https://meta.discourse.org/t/-/383836/6?silent=true).

- Em [Suggestions for displaying AI response areas beneath threads](https://meta.discourse.org/t/-/384212/1?silent=true), <a class="mention" href="/u/kuaza">kuaza</a> compartilhou mockups de UI para incorporar um painel de resposta "HelperBot" sob os tópicos para tranquilizar os usuários durante as automações.

- O debate contínuo de #content-localization atingiu o pico quando <a class="mention" href="/u/southpaw">southpaw</a> apontou traduções desatualizadas em [Content Localization - Manual and Automatic with Discourse AI](https://meta.discourse.org/t/-/370969/36?silent=true), e <a class="mention" href="/u/nat">nat</a> opinou sobre limites de edição de tradução e indicadores desatualizados [ref](https://meta.discourse.org/t/-/370969/37?silent=true).

---

## Atividade

- <a class="mention" href="/u/nat">nat</a> (14 curtidas, 6 posts) liderou recursos de localização, lançando o [Translate Now button](https://meta.discourse.org/t/-/383544/3?silent=true), diagnosticando o [translations bug](https://meta.discourse.org/t/-/384214/4?silent=true) e planejando limites de content-localization [ref](https://meta.discourse.org/t/-/370969/37?silent=true).

- <a class="mention" href="/u/Falco">Falco</a> (13 curtidas, 4 posts) ajustou sugestões de IA desabilitando penalidades de idade em [Suggested vs Related links](https://meta.discourse.org/t/-/384030/5?silent=true), testou gists mobile em [AI Gists PMs](https://meta.discourse.org/t/-/384243/2?silent=true) e discutiu notificações de cota em [automation AI responses](https://meta.discourse.org/t/-/383581/2?silent=true).

- <a class="mention" href="/u/JammyDodger">JammyDodger</a> (8 curtidas, 2 posts) destacou regressões de qualidade em [Suggested vs Related](https://meta.discourse.org/t/-/384030/4?silent=true) e acompanhou ajustes de relevância [ref](https://meta.discourse.org/t/-/384030/7?silent=true).

- <a class="mention" href="/u/fzngagan">fzngagan</a> (7 curtidas, 1 post) demonstrou a integração de llms.txt em [Add llms.txt to your site](https://meta.discourse.org/t/-/383088/1?silent=true).

- <a class="mention" href="/u/NateDhaliwal">NateDhaliwal</a> (5 curtidas, 5 posts) expôs o bug [AI Gists PMs bug](https://meta.discourse.org/t/-/384243/1?silent=true) e guiou através da [AI Summarization setup](https://meta.discourse.org/t/-/383836/4?silent=true).

- <a class="mention" href="/u/awesomerobot">awesomerobot</a> (4 curtidas, 2 posts) depurou a análise de JSON em [llm_tagger](https://meta.discourse.org/t/-/383444/5?silent=true) e refinou dicas de esquema [ref](https://meta.discourse.org/t/-/383444/7?silent=true).

- <a class="mention" href="/u/tobiaseigen">tobiaseigen</a> (4 curtidas, 2 posts) escreveu a proposta [Suggested vs Related links](https://meta.discourse.org/t/-/384030/1?silent=true) e aplicou linking silencioso no tutorial de boas-vindas.

- <a class="mention" href="/u/Moin">Moin</a> (4 curtidas, 1 post) compartilhou casos de uso para [Related Topics merging](https://meta.discourse.org/t/-/384030/6?silent=true).

- <a class="mention" href="/u/kuaza">kuaza</a> (4 curtidas, 6 posts) prototipou painéis de resposta de IA [ref](https://meta.discourse.org/t/-/384212/1?silent=true), refinou arrays llm_tagger [ref](https://meta.discourse.org/t/-/383444/6?silent=true) e propôs restrições de tags em [automation AI](https://meta.discourse.org/t/-/384300/1?silent=true).

- <a class="mention" href="/u/jenmck">jenmck</a> (3 curtidas, 2 posts) defendeu a curadoria manual em [Suggested vs Related](https://meta.discourse.org/t/-/384030/3?silent=true) e opinou sobre riscos de moderação de IA em [AI Forum Moderation: Seeking Insights and Experiences](https://meta.discourse.org/t/-/299018/11?silent=true).

---

Obrigado por ler, e nos vemos na próxima semana! :slight_smile:
89

Resumo Semanal de Atividade de IA (29/09/2025 a 06/10/2025)

Visão Geral

Na semana passada, a tag de IA apresentou uma gama diversificada de discussões, desde falhas no ícone de tradução e erros de formatação JSON até solicitações de recursos e correções de bugs. Notavelmente, @Smooth_Play resolveu botões de tradução ausentes em Por que o Ícone de Tradução de IA do Discourse Não Está Aparecendo? [#Suporte #localização-de-conteúdo], enquanto @Rubi e @Moin lidaram com um pequeno erro de digitação no plugin Discourse AI principal [Plugin #oficial #incluído-no-core]. Membros da comunidade também navegaram pelos requisitos de saída estruturada para DeepSeek em Lidando com Problemas de Formato de Resposta JSON do DeepSeek [#Suporte #ia], verificaram correções de prompts de IA personalizados em Como os usuários podem usar prompts de IA personalizados [Bug ai-helper] e discutiram melhorias nos Gists de IA em dispositivos móveis em Botão de Gists de IA exibido para MPs, mas sem texto de resumo [Bug mobile #ia]. Tópicos adicionais cobriram sugestões de aprimoramento de UI, integração de pesquisa e testes de reranker:

Tópicos Interessantes

Atividade

Obrigado por ler, e vejo você novamente na próxima semana! :slight_smile:

90

Resumo Semanal de Atividade de IA (06/10/2025 a 13/10/2025)

Visão Geral

Esta semana, nas categorias ai e content-localization, vimos discussões vibrantes sobre:

Tópicos Interessantes

Atividade

Obrigado pela leitura, e nos vemos novamente na próxima semana! :slight_smile: