Riassunto settimanale degli argomenti sull'AI

Feedback sul sito Riassunti del forum
68

Panoramica

Le conversazioni sull’IA di questa settimana su Meta si sono concentrate sulla gestione dei contenuti basata sull’IA, sui perfezionamenti dell’interfaccia utente e sulle correzioni interne. I temi chiave includevano:

  1. Suddivisione degli argomenti guidata dall’IA: il lancio di Utilizzo del ricercatore del forum per aiutare a organizzare e suddividere argomenti di grandi dimensioni (Community, ai) ha innescato confronti affiancati di flussi di lavoro manuali e assistiti dall’IA, con \u003ca class="mention" href="/u/JammyDodger"\u003eJammyDodger\u003c/a\u003e che ha condiviso consigli dettagliati per la suddivisione manuale.
  2. Maggiore visibilità della persona IA: le discussioni in Creare un collegamento più evidente per la persona IA (Support, ai) hanno esplorato l’inserimento di un’icona chatbot più grande nell’interfaccia utente e persino la sostituzione di immagini personalizzate per una maggiore prominenza.
  3. Trasformazione della homepage: l’idea di trasformare la pagina di destinazione in un’interfaccia bot IA è stata prototipata in Come impostare la homepage come bot IA? es: ask.discourse.com (Support, ai), con \u003ca class="mention" href="/u/Lilly"\u003eLilly\u003c/a\u003e che ha suggerito automazioni di invito di gruppo.
  4. Passaggio dati artefatto: in Come passo i dati a un artefatto? (Feature, ai-artifacts), \u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e ha introdotto una correzione API basata su postMessage, successivamente unita come pull request.
  5. Correzioni schema e payload: un bug critico nell’analisi JSON è stato risolto in Riassumi argomento con IA si carica indefinitamente, payload JSON non valido ricevuto? (Bug, ai) tramite modifiche al gestore dello schema Gemini.
  6. Modifiche al posizionamento UX: gli aggiustamenti per evitare che il pulsante mobile AI Docs si sovrapponga ai controlli nativi sono stati delineati in Pulsante sovrapposto AI Docs mal posizionato (UX, accessibility, ai).
  7. Considerazioni sui costi: gli avvisi sulle costose chiamate ai modelli sono emersi in Problemi nella configurazione manuale della ricerca approfondita sonar di perplexity (Dev, ai), notando che una singola risposta potrebbe costare oltre $0,70.
  8. Flussi di lavoro estesi per la suddivisione degli argomenti: post di follow-up in Utilizzo del ricercatore del forum per aiutare a organizzare e suddividere argomenti di grandi dimensioni hanno testato lo strumento su altri thread “kitchen sink”.
  9. Ulteriori miglioramenti della persona: i membri della community hanno iterato sull’approccio di \u003ca class="mention" href="/u/Lilly"\u003eLilly\u003c/a\u003e in Creare un collegamento più evidente per la persona IA, costruendo componenti personalizzati tramite il plugin Discourse Custom Components.
  10. Monitoraggio patch backend: ulteriori correzioni sono state tracciate tramite aggiornamenti PR in Come passo i dati a un artefatto? e modifiche ai margini in Pulsante sovrapposto AI Docs mal posizionato.

Argomenti Interessanti

  • Utilizzo del ricercatore del forum per aiutare a organizzare e suddividere argomenti di grandi dimensioni (argomento 366188, Community, ai)
    \u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e ha demoed una persona IA disabilitata di default per la ricerca approfondita, mostrando schemi automatizzati per l’argomento Kanban Board.

  • Creare un collegamento più evidente per la persona IA (argomento 365884, Support, ai)
    \u003ca class="mention" href="/u/Angela_MRS"\u003eAngela_MRS\u003c/a\u003e ha chiesto come ingrandire l’icona del chatbot, e \u003ca class="mention" href="/u/Lilly"\u003eLilly\u003c/a\u003e ha condiviso hack per la barra laterale e il menu a tendina.

  • Pulsante sovrapposto AI Docs mal posizionato (argomento 366138, UX, accessibility, ai)
    \u003ca class="mention" href="/u/SvenPuschmann"\u003eSvenPuschmann\u003c/a\u003e ha segnalato che il pulsante mobile AI Docs ostruiva i controlli iOS, con \u003ca class="mention" href="/u/pmusaraj"\u003epmusaraj\u003c/a\u003e che ha suggerito semplici correzioni di margine CSS.

  • Come passo i dati a un artefatto? (argomento 350791, Feature, ai-artifacts)
    Una soluzione postMessage che richiede sandboxing è stata implementata da \u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e, tracciata in PR #1346.

  • Riassumi argomento con IA si carica indefinitamente, payload JSON non valido ricevuto? (argomento 365587, Bug, ai)
    \u003ca class="mention" href="/u/Roman_Rizzi"\u003eRoman_Rizzi\u003c/a\u003e ha confermato che la modifica del formato dello schema JSON in PR #1340 ha risolto gli errori di caricamento infinito.

  • Problemi nella configurazione manuale della ricerca approfondita sonar di perplexity (argomento 365572, Dev, ai)
    Ostacoli di configurazione e costi per token sono stati segnalati da \u003ca class="mention" href="/u/aas"\u003eaas\u003c/a\u003e dopo aver citato l’avvertimento di \u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e sulle spese.

  • Come impostare la homepage come bot IA? es: ask.discourse.com (argomento 365126, Support, ai)
    Le proposte includevano script di automazione per l’iscrizione automatica tramite campi utente personalizzati, dimostrati da \u003ca class="mention" href="/u/Lilly"\u003eLilly\u003c/a\u003e.

Attività

Grazie per la lettura e ci vediamo la prossima settimana! :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

Riassunto settimanale delle attività sull’IA
Data di inizio: 2025-06-30
Data di fine: 2025-07-07

Panoramica
Le conversazioni sull’IA di questa settimana su meta.discourse.org hanno riguardato preoccupazioni ambientali, flessibilità dei plugin, personalizzazione delle funzionalità e correzioni di bug. pHneutre ha guidato un dibattito sul green computing in AI-free Discourse (vedere il post #2 per la risposta di merefield).
La stabilità del modello di visione è stata verificata in Quick welfare check on the AI caption bot con passaggi di risoluzione nel post #2 e nel post #3.
Gli amministratori hanno perfezionato i controlli delle persona in Is it possible to enable only one AI persona? poiché Falco ha dettagliato gli interruttori nel post #2.
La flessibilità di riassunto si è evoluta tramite Can you customize the Ai Summarize prompt? e Customizing AI summarizer to use non-English languages, con follow-up in 372448/2 e 372644/2.
L’estensione del contesto tramite RAG è stata esplorata in Another added context for AI Bot (dettagli nel post #2).
Le correzioni di bug chiave includevano l’errore “no implicit conversion of Array into String” in Error "no implicit conversion of Array into String" (risolto nel post #5), i campi opzionali reimpostati in Small bug in AI Persona Editor e le omissioni delle etichette del modello in Model name not showing in AI bot.
I thread di automazione e integrazione della ricerca hanno guadagnato slancio in Discourse AI - AI triage e Discourse AI - AI search.

Argomenti interessanti

Attività

Grazie per aver letto, ci vediamo la prossima settimana! :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 
# Riepilogo settimanale attività AI su meta.discourse.org  
**Periodo:** 21/07/2025 - 28/07/2025  
**Nuovi post:** 43 · **Nuovi argomenti:** 16  
\n---\n\n## Panoramica  
Questa settimana ha visto un mix di risoluzione di problemi tecnici, richieste di funzionalità e discussioni sulla roadmap relative alle offerte AI di Discourse. I temi chiave includevano:\n\n- **Problemi di aggiornamento e build** causati da uno specchio npm cinese obsoleto #Bug #ai.  \n- **Ottimizzazione della protezione antispam**, con community private che disabilitano i filtri antispam AI #Bug #ai.  \n- **Inclusione del plugin Discourse AI** nel core e relative domande di integrazione #Plugin #official #included-in-core #ai.  \n- **Flussi di lavoro di traduzione**, che coprono la ritraduzione di post generati dall'AI e le stranezze della cache #ai #ai-helper.  \n- **Controllo del comportamento dei bot**, dai limiti di risposta alle opzioni di trigger #Support #ai-bot.  \n- **Integrazioni LLM di terze parti** (Azure OpenAI, IBM WatsonX) e caricamenti RAG #Integrations #ai #ai-bot.  \n- **Ingegneria delle persona**, inclusa la conversione di log Slack e l'esplorazione di sotto-agenti #SiteManagement #ai-bot.  \n- Discussioni sull'adozione del **Model Context Protocol (MCP)** #Feature #ai.  \n\n---\n\n## Argomenti Interessanti  \n\n- Errori di build durante gli aggiornamenti di Discourse a causa di una discrepanza nello specchio npm cinese  \n  ([Build failures during Discourse updates due to a Chinese npm mirror mismatch](https://meta.discourse.org/t/-/376095/1?silent=true)) #Bug #ai  \n\n- Filtro antispam AI troppo attivo nelle community private e come disabilitarlo  \n  ([Overactive spam filter?](https://meta.discourse.org/t/-/375475/1?silent=true)) #Bug #ai  \n\n- Inclusione ufficiale del plugin Discourse AI nel core e note di aggiornamento  \n  ([Discourse AI](https://meta.discourse.org/t/-/259214/219?silent=true)) #Plugin #official #included-in-core #ai  \n\n- Ritraduzione di contenuti generati dall'AI e gestione di traduzioni obsolete  \n  ([Discourse AI](https://meta.discourse.org/t/-/259214/221?silent=true)) &  \n  ([AI helper does not always use user's locale](https://meta.discourse.org/t/-/298867/6?silent=true)) #ai #ai-helper  \n\n- Controllo dei trigger di risposta dell'AI helper, limiti per argomento o per utente  \n  ([Controlling AI responses in forum discussions](https://meta.discourse.org/t/-/376066/1?silent=true)) #Support #ai-bot  \n\n- Configurazione delle chiavi API Azure OpenAI e risoluzione degli errori 500  \n  ([Configure API Keys for Azure OpenAI](https://meta.discourse.org/t/-/282442/7?silent=true)) #Integrations #ai  \n\n- Progettazione e gestione di persona AI utilizzando fonti di conoscenza esterne  \n  ([AI bot - Personas](https://meta.discourse.org/t/-/306099/16?silent=true)) #SiteManagement #ai-bot  \n\n- Roadmap e stato di adozione del Model Context Protocol (MCP)  \n  ([Is there an official Discourse Model Context Protocol (MCP)](https://meta.discourse.org/t/-/364859/16?silent=true)) #Feature #ai  \n\n- Personalizzazione dell'icona del robot AI nell'intestazione e nella barra laterale  \n  ([Replacing the robot icon in header](https://meta.discourse.org/t/-/375472/1?silent=true)) #Support #ai  \n\n- Caricamenti programmatici per flussi di lavoro di Retrieval-Augmented Generation (RAG)  \n  ([Programmatic RAG uploads?](https://meta.discourse.org/t/-/374408/3?silent=true)) #Support #ai-bot  \n\n---\n\n## Attività  \nEcco chi ha postato questa settimana e dove:\n\n- \u003ca class=\"mention\" href=\"/u/cshll\"\u003ecshll\u003c/a\u003e ha aperto un problema sull'errore dello specchio npm in [Build failures during Discourse updates due to a Chinese npm mirror mismatch (post #1)](https://meta.discourse.org/t/-/376095/1?silent=true) e ha aggiunto dettagli di follow-up in [post #3](https://meta.discourse.org/t/-/376095/3?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/sam\"\u003esam\u003c/a\u003e ha suggerito una ricompilazione della console in [Build failures during Discourse updates due to a Chinese npm mirror mismatch (post #2)](https://meta.discourse.org/t/-/376095/2?silent=true), è intervenuto sulla configurazione del filtro antispam in [Overactive spam filter? (post #5)](https://meta.discourse.org/t/-/375475/5?silent=true) e ha confermato la cache delle localizzazioni in [AI helper does not always use user's locale (post #6)](https://meta.discourse.org/t/-/298867/6?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/david\"\u003edavid\u003c/a\u003e ha chiarito gli errori di pacchetti mancanti in [Build failures during Discourse updates due to a Chinese npm mirror mismatch (post #5)](https://meta.discourse.org/t/-/376095/5?silent=true) e ha celebrato l'inclusione del plugin in [Discourse AI (post #219)](https://meta.discourse.org/t/-/259214/219?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/Moin\"\u003eMoin\u003c/a\u003e ha segnalato problemi di cache delle traduzioni in [Build failures during Discourse updates due to a Chinese npm mirror mismatch (post #6)](https://meta.discourse.org/t/-/376095/6?silent=true) e ha spiegato come disabilitare la gestione dello spam AI in [Overactive spam filter? (post #3)](https://meta.discourse.org/t/-/375475/3?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/Lhc_fl\"\u003eLhc_fl\u003c/a\u003e ha raccomandato l'uso di server o proxy non cinesi in [Build failures during Discourse updates due to a Chinese npm mirror mismatch (post #8)](https://meta.discourse.org/t/-/376095/8?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/NateDhaliwal\"\u003eNateDhaliwal\u003c/a\u003e ha chiesto informazioni sul tipo di installazione in [Build failures during Discourse updates due to a Chinese npm mirror mismatch (post #4)](https://meta.discourse.org/t/-/376095/4?silent=true) e ha richiesto log per la configurazione Azure in [Configure API Keys for Azure OpenAI (post #8)](https://meta.discourse.org/t/-/282442/8?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/Seth_Godin\"\u003eSeth_Godin\u003c/a\u003e ha segnalato un blocco antispam per community private in [Overactive spam filter? (post #1)](https://meta.discourse.org/t/-/375475/1?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/Jagster\"\u003eJagster\u003c/a\u003e ha offerto un override del prompt di sistema in [Overactive spam filter? (post #4)](https://meta.discourse.org/t/-/375475/4?silent=true) ed esempi di prompt in [Controlling AI responses (post #5)](https://meta.discourse.org/t/-/376066/5?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/nat\"\u003enat\u003c/a\u003e ha verificato l'uso degli specchi con Lhc_fl in [Build failures during Discourse updates due to a Chinese npm mirror mismatch (post #7)](https://meta.discourse.org/t/-/376095/7?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/jrgong\"\u003ejrgong\u003c/a\u003e ha elogiato la guida dell'helper di Sam in [Why is my AI forum helper struggling? (post #2)](https://meta.discourse.org/t/-/352848/2?silent=true) e ha chiesto informazioni sulla struttura delle persona basata sui log in [AI bot - Personas (post #16)](https://meta.discourse.org/t/-/306099/16?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/Falco\"\u003eFalco\u003c/a\u003e ha spiegato come eliminare le traduzioni tramite console in [Discourse AI (post #222)](https://meta.discourse.org/t/-/259214/222?silent=true), ha affrontato la compatibilità delle API IBM WatsonX in [LLM settings page (post #17)](https://meta.discourse.org/t/-/319903/17?silent=true) e ha chiarito i trigger dei bot in [Controlling AI responses (post #3)](https://meta.discourse.org/t/-/376066/3?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/RBoy\"\u003eRBoy\u003c/a\u003e ha cercato controlli sui limiti di risposta dei bot in [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).  \n\n- \u003ca class=\"mention\" href=\"/u/satonotdead\"\u003esatonotdead\u003c/a\u003e ha suggerito prompt di passaggio umano graduale in [Controlling AI responses (post #4)](https://meta.discourse.org/t/-/376066/4?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/Wurzelseppi\"\u003eWurzelseppi\u003c/a\u003e ha chiesto informazioni sulla creazione di riferimenti per il caricamento RAG in [Programmatic RAG uploads? (post #3)](https://meta.discourse.org/t/-/374408/3?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/Goalina\"\u003eGoalina\u003c/a\u003e ha chiesto informazioni sui conteggi di ritraduzione in [Discourse AI (post #221)](https://meta.discourse.org/t/-/259214/221?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/ばこん\"\u003eばこん\u003c/a\u003e ha segnalato una pagina di preferenze AI mancante in [Discourse AI - AI search (post #16)](https://meta.discourse.org/t/-/282420/16?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/EricGT\"\u003eEricGT\u003c/a\u003e ha proposto la terminologia "Sub-Agent" in [Renaming AI Persona → AI Agent (post #7)](https://meta.discourse.org/t/-/368198/7?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/CraigW\"\u003eCraigW\u003c/a\u003e ha chiesto informazioni sull'integrazione IBM WatsonX in [LLM settings page (post #16)](https://meta.discourse.org/t/-/319903/16?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/MachineScholar\"\u003eMachineScholar\u003c/a\u003e ha fatto seguito sulla maturità dell'MCP in [Is there an official Discourse MCP (post #16)](https://meta.discourse.org/t/-/364859/16?silent=true).  \n\n- \u003ca class=\"mention\" href=\"/u/zabin\"\u003ezabin\u003c/a\u003e ha condiviso una soluzione alternativa Bitnami-Postgres per la migrazione del plugin in [Bootstrap error with AI plugin (post #6)](https://meta.discourse.org/t/-/371514/6?silent=true) e ha registrato fallimenti nei test Azure in [Configure API Keys for Azure (post #9)](https://meta.discourse.org/t/-/282442/9?silent=true).  \n\n---\n\nGrazie per aver letto, ci vediamo la prossima settimana! :slight_smile:\n```
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

Panoramica

Questa settimana su Meta Discourse, le funzionalità dell’IA hanno continuato a evolversi in flussi di lavoro di tagging, integrazione di modelli, ricerca, localizzazione e moderazione. La discussione sul tagging automatizzato in Utilizzare l’IA per taggare e categorizzare i post del forum ha evidenziato potenziali miglioramenti con gli embedding (Support ai), mentre un’analisi approfondita di Custom LLMs-Job exception ha fatto luce su disallineamenti tra persona e strumento e sulla gestione degli errori (Support ai). Le conversazioni sulle best practice per il rilevamento dello spam e il triage, inclusa l’evitare il doppio flag, sono state sollevate in Best practices for AI antispam plus AI post triage operating together? (Support ai moderation). Nel frattempo, anteprime di funzionalità come Conversational AI Search coming to Discourse AI hanno mostrato intoppi iniziali con la visibilità dei font e il conteggio delle richieste (Feature ai-search). Sul fronte della gestione del sito, gli utenti hanno valutato i costi e i flussi di lavoro di Content Localization - Manual and Automatic with Discourse AI e condiviso esperienze di traduzione (#Site Management ai content-localization). Infine, strumenti IA legacy come l’analisi del sentiment e l’auto-captioning hanno visto nuovi report di bug in Discourse AI - Sentiment e Helper - Auto caption (#Site Management ai).

Argomenti Interessanti

Attività

Grazie per aver letto, ci vediamo la prossima settimana! :slight_smile:

86

Panoramica

I punti salienti di questa settimana includono una proposta per espandere lo scanner di spam AI con il rilevamento di numeri di telefono in Dovremmo dire allo scanner di spam AI di segnalare i post contenenti numeri di telefono per impostazione predefinita? spam, il perfezionamento del controllo È richiesto un modello LLM predefinito prima di abilitare “Chat”? Bug content-localization, un rinnovato dibattito su un protocollo ufficiale di contesto del modello Discourse (MCP) Feature ai, una correzione critica per Discourse AI Persona, supporto per il caricamento Announcements ai-bot e la completa risoluzione di Il riempimento delle traduzioni AI non funziona dopo aver configurato tutte le impostazioni Support content-localization.

Argomenti Interessanti

  • In spam, \u003ca class="mention" href="/u/awesomerobot"\u003eawesomerobot\u003c/a\u003e ha avviato Dovremmo dire allo scanner di spam AI di segnalare i post contenenti numeri di telefono per impostazione predefinita? suggerendo che i numeri di telefono spesso segnalano spam indesiderato di assistenza clienti. \u003ca class="mention" href="/u/pfaffman"\u003epfaffman\u003c/a\u003e ha indagato sull’offuscamento unicode in post due, \u003ca class="mention" href="/u/awesomerobot"\u003eawesomerobot\u003c/a\u003e ha commentato il rilevamento basato su prompt in post tre, e \u003ca class="mention" href="/u/pfaffman"\u003epfaffman\u003c/a\u003e ha confermato la flessibilità dell’AI rispetto alle regex in post quattro.

  • In Bug \u0026 content-localization, la discussione È richiesto un modello LLM predefinito prima di abilitare “Chat”? ha visto \u003ca class="mention" href="/u/nat"\u003enat\u003c/a\u003e incapace di riprodurre il problema in post tre e \u003ca class="mention" href="/u/Falco"\u003eFalco\u003c/a\u003e proporre la rimozione del controllo obsoleto in post quattro.

  • In Feature, \u003ca class="mention" href="/u/jrgong"\u003ejrgong\u003c/a\u003e ha ripreso la discussione di lunga data sul protocollo ufficiale di contesto del modello Discourse (MCP) notando che i fornitori di AI probabilmente hanno raccolto tutti i post pubblici e ricordando ai collaboratori di chiudere correttamente le loro parentesi graffe JSON.

  • In Announcements \u0026 ai-bot, \u003ca class="mention" href="/u/kiefferr"\u003ekiefferr\u003c/a\u003e ha elogiato la nuova funzionalità Discourse AI Persona, supporto per il caricamento ma ha segnalato un bug per cui i link caricati restituivano “accesso negato”.

  • In Support \u0026 content-localization, la discussione “Il riempimento delle traduzioni AI non funziona dopo aver configurato tutte le impostazioni” ha visto un’ampia risoluzione dei problemi:
    • \u003ca class="mention" href="/u/tyronejv"\u003etyronejv\u003c/a\u003e ha inizialmente segnalato un riempimento parziale in post sette e ha chiarito le impostazioni in post otto.
    • Screenshot di traduzioni bloccate sono apparsi in post nove e post undici.
    • \u003ca class="mention" href="/u/GrahamM"\u003eGrahamM\u003c/a\u003e ha confermato il problema in post dieci e ha perfezionato la configurazione in post dodici.
    • La risoluzione dei problemi basata sui log è stata guidata da \u003ca class="mention" href="/u/RGJ"\u003eRGJ\u003c/a\u003e in post tredici.
    • La correzione finale è stata condivisa da \u003ca class="mention" href="/u/GrahamM"\u003eGrahamM\u003c/a\u003e in post quattordici.
    • \u003ca class="mention" href="/u/Jagster"\u003eJagster\u003c/a\u003e ha commentato le prestazioni di GPT-5 in post quindici, e \u003ca class="mention" href="/u/nat"\u003enat\u003c/a\u003e ha fornito diagnostiche più approfondite in post sedici.
    Per la guida completa, vedere il Manuale e Automatico di Localizzazione dei Contenuti con Discourse AI.

  • In Support \u0026 ai-bot, \u003ca class="mention" href="/u/tpetrov"\u003etpetrov\u003c/a\u003e ha analizzato i processi RAG e ha posto domande di follow-up sul consolidamento del contesto dopo la panoramica di \u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e in post tre.

Attività

  • \u003ca class="mention" href="/u/awesomerobot"\u003eawesomerobot\u003c/a\u003e (2 post, 3 like) ha contribuito alla discussione sul filtro spam per numeri di telefono in post uno e post tre.
  • \u003ca class="mention" href="/u/pfaffman"\u003epfaffman\u003c/a\u003e (2 post, 2 like) si è unito in post due e post quattro.
  • \u003ca class="mention" href="/u/nat"\u003enat\u003c/a\u003e (2 post, 1 like) è intervenuto sul controllo LLM predefinito in post tre e ha condiviso diagnostiche per il riempimento delle traduzioni in post sedici.
  • \u003ca class="mention" href="/u/jrgong"\u003ejrgong\u003c/a\u003e (1 post, 1 like) ha commentato MCP in post ventotto.
  • \u003ca class="mention" href="/u/Falco"\u003eFalco\u003c/a\u003e (1 post, 1 like) ha suggerito di rimuovere il controllo LLM in post quattro.
  • \u003ca class="mention" href="/u/GrahamM"\u003eGrahamM\u003c/a\u003e (3 post, 1 like) ha guidato la risoluzione dei problemi di riempimento delle traduzioni in post dieci, post dodici e post quattordici.
  • \u003ca class="mention" href="/u/kiefferr"\u003ekiefferr\u003c/a\u003e (1 post, 1 like) ha segnalato il problema di caricamento di AI Persona in post venticinque.
  • \u003ca class="mention" href="/u/tpetrov"\u003etpetrov\u003c/a\u003e (1 post, 0 like) ha esplorato la meccanica RAG in post tre.
  • \u003ca class="mention" href="/u/RGJ"\u003eRGJ\u003c/a\u003e (2 post, 0 like) ha indagato sulle impostazioni di traduzione in post otto e sui controlli dei log in post tredici.
  • \u003ca class="mention" href="/u/Jagster"\u003eJagster\u003c/a\u003e (1 post, 0 like) ha condiviso note sulle prestazioni di GPT-5 in post quindici.

Grazie per aver letto, ci vediamo la prossima settimana! :slight_smile:

87

Riepilogo settimanale attività AI (15/09/2025 – 22/09/2025)

Panoramica

Le discussioni di questa settimana su meta.discourse.org si sono concentrate sul miglioramento della localizzazione dei contenuti, sulla correzione di bug nelle funzionalità basate sull’IA e sui nuovi flussi di lavoro per gli helper AI. Abbiamo approfondito il debug in Localizzazione dei contenuti - Manuale e Automatica con Discourse AI tramite log dettagliati, una proposta per un pulsante immediato “Traduci ora” per aggirare il throttling e la pianificazione delle traduzioni dei tag e delle notifiche email nelle lingue degli utenti. Allo stesso tempo, diversi report Bug—in particolare relativi ai video di YouTube nelle traduzioni AI e alle notifiche di quota del plugin di automazione—sono stati smistati, e le best practice per l’antispam e il triage AI sono state affinate.

Argomenti Interessanti

Attività

Grazie per la lettura e ci vediamo la prossima settimana! :slight_smile:

88 
## Panoramica

La scorsa settimana, #ai e #content-localization hanno visto un'ondata di discussioni sul miglioramento delle funzionalità guidate dall'IA, dal perfezionamento dei suggerimenti di argomenti e delle traduzioni al potenziamento degli strumenti di automazione. Il dibattito sui link "Suggeriti vs Correlati" avviato da <a class="mention" href="/u/tobiaseigen">tobiaseigen</a> in [Vogliamo modificare i link "suggeriti" e "correlati" in fondo ai post?](https://meta.discourse.org/t/-/384030/1?silent=true) ha innescato molteplici miglioramenti ai flussi di lavoro di punteggio di pertinenza e di curatela manuale. I miglioramenti della traduzione sono stati al centro della scena quando <a class="mention" href="/u/nat">nat</a> ha implementato un [Aggiungi pulsante "Traduci ora" visibile ai gruppi autorizzati](https://meta.discourse.org/t/-/383544/3?silent=true), mentre i casi limite di localizzazione sono emersi in [Bug nelle traduzioni di Discourse AI?](https://meta.discourse.org/t/-/384214/1?silent=true), richiedendo diagnosi più approfondite. Sul fronte dell'automazione, i problemi di analisi JSON in [llm_tagger: Impossibile analizzare la risposta JSON...](https://meta.discourse.org/t/-/383444/5?silent=true) sono stati risolti e i membri della community hanno delineato le migliori pratiche per l'integrazione degli LLM, sia tramite llms.txt ([ref](https://meta.discourse.org/t/-/383088/1?silent=true)) sia tramite la configurazione manuale dei plugin ([Richiesta di configurazione: Riassunto AI...](https://meta.discourse.org/t/-/383836/1?silent=true)).

---

## Argomenti Interessanti

- <a class="mention" href="/u/tobiaseigen">tobiaseigen</a> ha avviato una discussione in [Vogliamo modificare i link "suggeriti" e "correlati" in fondo ai post?](https://meta.discourse.org/t/-/384030/1?silent=true) esplorando se i nuovi utenti dovrebbero vedere suggerimenti generati dall'IA. <a class="mention" href="/u/jenmck">jenmck</a> ha sostenuto la curatela manuale [ref](https://meta.discourse.org/t/-/384030/3?silent=true), mentre <a class="mention" href="/u/Falco">Falco</a> ha modificato la penalità di età sugli argomenti più vecchi per migliorare la pertinenza [ref](https://meta.discourse.org/t/-/384030/5?silent=true).

- <a class="mention" href="/u/nat">nat</a> ha fornito un miglioramento dell'UX aggiungendo un [pulsante "Traduci ora" visibile ai gruppi autorizzati](https://meta.discourse.org/t/-/383544/3?silent=true), dando ai `content_localization_allowed_groups` il controllo della traduzione con un clic.

- Sotto #automation, <a class="mention" href="/u/awesomerobot">awesomerobot</a> e <a class="mention" href="/u/kuaza">kuaza</a> hanno affrontato il problema [llm_tagger: Impossibile analizzare la risposta JSON...](https://meta.discourse.org/t/-/383444/5?silent=true). Hanno perfezionato lo schema JSON, spostando i tag in array [ref](https://meta.discourse.org/t/-/383444/7?silent=true) e isolando la confidenza come intero [ref](https://meta.discourse.org/t/-/383444/9?silent=true).

- <a class="mention" href="/u/dennisjbr">dennisjbr</a> ha proposto di indicizzare asset non HTML in [Indicizza i contenuti dei file per la ricerca](https://meta.discourse.org/t/-/31884/10?silent=true) per sbloccare la ricerca full-text di PDF e immagini tramite Postgres.

- Per aiutare i crawler LLM, <a class="mention" href="/u/fzngagan">fzngagan</a> ha illustrato come [Aggiungere llms.txt al tuo sito](https://meta.discourse.org/t/-/383088/1?silent=true) utilizzando argomenti privati e permalink personalizzati.

- Su mobile, <a class="mention" href="/u/NateDhaliwal">NateDhaliwal</a> ha segnalato che il [pulsante AI Gists mostrato per i PM, ma senza testo di riepilogo](https://meta.discourse.org/t/-/384243/1?silent=true) appare ma non renderizza i gists [ref](https://meta.discourse.org/t/-/384243/2?silent=true), richiedendo ulteriori diagnosi dell'interfaccia utente.

- <a class="mention" href="/u/昊毅_周">昊毅_周</a> ha scoperto un [Bug nelle traduzioni di Discourse AI?](https://meta.discourse.org/t/-/384214/1?silent=true) in cui le descrizioni delle categorie create dal sistema venivano erroneamente rilevate come inglesi. <a class="mention" href="/u/nat">nat</a> ha raccomandato una query del data explorer per l'audit della locale [ref](https://meta.discourse.org/t/-/384214/10?silent=true) e interruttori manuali della locale [ref](https://meta.discourse.org/t/-/384214/9?silent=true).

- <a class="mention" href="/u/S.AAKASH_MUTHIAH">S.AAKASH_MUTHIAH</a> ha avviato una [Richiesta di configurazione: Riassunto AI in Discourse e integrazione LLM](https://meta.discourse.org/t/-/383836/1?silent=true), con <a class="mention" href="/u/NateDhaliwal">NateDhaliwal</a> che ha guidato verso la documentazione dei plugin [ref](https://meta.discourse.org/t/-/383836/2?silent=true) e suggerimenti per la configurazione manuale degli LLM [ref](https://meta.discourse.org/t/-/383836/6?silent=true).

- In [Suggerimenti per la visualizzazione delle aree di risposta AI sotto i thread](https://meta.discourse.org/t/-/384212/1?silent=true), <a class="mention" href="/u/kuaza">kuaza</a> ha condiviso mockup dell'interfaccia utente per incorporare un pannello di risposta "HelperBot" sotto gli argomenti per rassicurare gli utenti durante le automazioni.

- Il dibattito in corso su #content-localization ha raggiunto il culmine quando <a class="mention" href="/u/southpaw">southpaw</a> ha segnalato traduzioni obsolete in [Content Localization - Manuale e Automatico con Discourse AI](https://meta.discourse.org/t/-/370969/36?silent=true), e <a class="mention" href="/u/nat">nat</a> è intervenuto sui limiti di modifica delle traduzioni e sugli indicatori obsoleti [ref](https://meta.discourse.org/t/-/370969/37?silent=true).

---

## Attività

- <a class="mention" href="/u/nat">nat</a> (14 like, 6 post) ha guidato le funzionalità di localizzazione, rilasciando il [pulsante Traduci ora](https://meta.discourse.org/t/-/383544/3?silent=true), diagnosticando il [bug delle traduzioni](https://meta.discourse.org/t/-/384214/4?silent=true) e definendo strategie per i limiti di content-localization [ref](https://meta.discourse.org/t/-/370969/37?silent=true).

- <a class="mention" href="/u/Falco">Falco</a> (13 like, 4 post) ha perfezionato i suggerimenti AI disabilitando le penalità di età in [Link suggeriti vs correlati](https://meta.discourse.org/t/-/384030/5?silent=true), ha testato i gists mobili in [AI Gists PM](https://meta.discourse.org/t/-/384243/2?silent=true) e ha discusso le notifiche di quota in [risposte AI di automazione](https://meta.discourse.org/t/-/383581/2?silent=true).

- <a class="mention" href="/u/JammyDodger">JammyDodger</a> (8 like, 2 post) ha evidenziato regressioni di qualità in [Suggeriti vs Correlati](https://meta.discourse.org/t/-/384030/4?silent=true) e ha dato seguito alle modifiche di pertinenza [ref](https://meta.discourse.org/t/-/384030/7?silent=true).

- <a class="mention" href="/u/fzngagan">fzngagan</a> (7 like, 1 post) ha dimostrato l'integrazione di llms.txt in [Aggiungere llms.txt al tuo sito](https://meta.discourse.org/t/-/383088/1?silent=true).

- <a class="mention" href="/u/NateDhaliwal">NateDhaliwal</a> (5 like, 5 post) ha segnalato il [bug dei gists AI nei PM](https://meta.discourse.org/t/-/384243/1?silent=true) e ha illustrato la [configurazione del riassunto AI](https://meta.discourse.org/t/-/383836/4?silent=true).

- <a class="mention" href="/u/awesomerobot">awesomerobot</a> (4 like, 2 post) ha debuggato l'analisi JSON in [llm_tagger](https://meta.discourse.org/t/-/383444/5?silent=true) e ha perfezionato i suggerimenti dello schema [ref](https://meta.discourse.org/t/-/383444/7?silent=true).

- <a class="mention" href="/u/tobiaseigen">tobiaseigen</a> (4 like, 2 post) ha redatto la proposta [Link suggeriti vs correlati](https://meta.discourse.org/t/-/384030/1?silent=true) e ha applicato il linking silenzioso al tutorial di benvenuto.

- <a class="mention" href="/u/Moin">Moin</a> (4 like, 1 post) ha condiviso casi d'uso per la [fusione di argomenti correlati](https://meta.discourse.org/t/-/384030/6?silent=true).

- <a class="mention" href="/u/kuaza">kuaza</a> (4 like, 6 post) ha prototipato pannelli di risposta AI [ref](https://meta.discourse.org/t/-/384212/1?silent=true), ha perfezionato gli array di llm_tagger [ref](https://meta.discourse.org/t/-/383444/6?silent=true) e ha proposto restrizioni sui tag in [automazione AI](https://meta.discourse.org/t/-/384300/1?silent=true).

- <a class="mention" href="/u/jenmck">jenmck</a> (3 like, 2 post) ha sostenuto la curatela manuale in [Suggeriti vs Correlati](https://meta.discourse.org/t/-/384030/3?silent=true) ed è intervenuto sui rischi di moderazione AI in [Moderazione AI del forum: Ricerca di spunti ed esperienze](https://meta.discourse.org/t/-/299018/11?silent=true).

---

Grazie per aver letto, ci vediamo la prossima settimana! :slight_smile:
89

Riepilogo settimanale attività AI (29/09/2025 - 06/10/2025)

Panoramica

La scorsa settimana, il tag AI ha visto una varietà di discussioni, da glitch nelle icone di traduzione ed errori di formattazione JSON, a richieste di funzionalità e correzioni di bug. In particolare, Smooth_Play ha risolto la mancanza di pulsanti di traduzione in Why Is the Discourse AI Translation Icon Not Appearing? [Support content-localization], mentre Rubi e Moin hanno affrontato un piccolo refuso nel Discourse AI plugin principale [Plugin official included-in-core]. I membri della community hanno anche affrontato i requisiti di output strutturato per DeepSeek in Dealing with DeepSeek JSON Response Format Issues [Support ai], verificato correzioni per prompt AI personalizzati in Ai自定义提示如何给用户使用 [Bug ai-helper], e discusso miglioramenti per gli AI Gists su mobile in AI Gists button shown for PMs, but with no summary text [Bug mobile ai]. Discussioni aggiuntive hanno coperto suggerimenti per il miglioramento dell’UI, integrazione della ricerca e test del reranker:

Argomenti Interessanti

Attività

Grazie per aver letto, ci vediamo la prossima settimana! :slight_smile:

90

Riepilogo settimanale attività AI (06-10-2025 al 13-10-2025)

Panoramica

Questa settimana nelle categorie ai e content-localization, abbiamo assistito a discussioni vivaci su:

Argomenti Interessanti

Attività

Grazie per aver letto, ci vediamo la prossima settimana! :slight_smile: