Riassunto settimanale degli argomenti sull'AI

Feedback sul sito Riassunti del forum
48

Panoramica

Le discussioni di questa settimana su meta.discourse.org si sono concentrate sull’esplorazione di nuovi modelli AI, sulla configurazione del rilevamento dello spam basato sull’AI, sulla gestione di persona AI e prompt e sullo sfruttamento delle capacità di ricerca semantica. Gli utenti hanno condiviso le loro esperienze con vari modelli linguistici, discusso potenziali miglioramenti e cercato indicazioni sull’ottimizzazione delle funzionalità AI all’interno della piattaforma Discourse.

Argomenti Interessanti

Attività

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

49

Panoramica

Questa settimana sul forum meta di Discourse, le discussioni si sono concentrate sulla funzionalità di rilevamento dello spam basata sull’IA, sullo strumento proposto “Solved Finder”, sui problemi di riepilogo dell’IA e su varie segnalazioni di bug e feedback relativi alle capacità dell’IA. Gli utenti hanno condiviso approfondimenti, segnalato bug e suggerito miglioramenti, promuovendo un ambiente collaborativo per migliorare l’integrazione dell’IA all’interno della piattaforma Discourse.

Argomenti Interessanti

  • Rilevamento spam basato sull’IA: gli utenti hanno discusso del rilascio della funzionalità di rilevamento dello spam basata sull’IA, inclusa la confusione sull’abilitazione negli account ospitati e i problemi con il comportamento dell’interruttore. \u003ca class="mention" href="/u/sam"\u003e@sam\u003c/a\u003e ha fornito chiarimenti sul processo e \u003ca class="mention" href="/u/Saif"\u003e@Saif\u003c/a\u003e ha menzionato una correzione imminente per il problema dell’interruttore.

  • Ricerca soluzioni: \u003ca class="mention" href="/u/Don"\u003e@Don\u003c/a\u003e ha proposto di aggiungere un pulsante per gli utenti dello staff per trovare potenziali soluzioni all’interno di un argomento, simile alla funzionalità di riepilogo dell’IA. \u003ca class="mention" href="/u/sam"\u003e@sam\u003c/a\u003e ha suggerito di esplorare prompt personalizzati o un’opzione “Parla con il mio argomento” per soddisfare questa esigenza.

  • [grid] dalla visione IA in chat: \u003ca class="mention" href="/u/zogstrip"\u003e@zogstrip\u003c/a\u003e ha condiviso che \u003ca class="mention" href="/u/joffreyjaffeux"\u003e@j.jaffeux\u003c/a\u003e aveva risolto un problema relativo alla visualizzazione di immagini generate dall’IA nella funzionalità di chat, fornendo uno screenshot della soluzione funzionante.

  • Il backfill del riepilogo IA sta sprecando token riassumendo i PM: \u003ca class="mention" href="/u/markschmucker"\u003e@markschmucker\u003c/a\u003e ha sollevato una preoccupazione riguardo al processo di backfill del riepilogo IA che riassume messaggi privati (PM), il che potrebbe essere inefficiente. \u003ca class="mention" href="/u/Falco"\u003e@Falco\u003c/a\u003e ha riconosciuto il problema e ha menzionato la possibilità di introdurre un’impostazione per saltare i PM, simile all’impostazione esistente per gli embedding.

  • Impossibile modificare ai_embeddings_model: \u003ca class="mention" href="/u/Overgrow"\u003e@Overgrow\u003c/a\u003e ha segnalato un problema con la modifica dell’impostazione ai_embeddings_model e l’abilitazione degli embedding tramite il pannello di amministrazione. \u003ca class="mention" href="/u/sam"\u003e@sam\u003c/a\u003e ha fornito un link a una pull request che mirava a risolvere il problema.

  • Come funziona la rigenerazione dei riepiloghi?: \u003ca class="mention" href="/u/markschmucker"\u003e@markschmucker\u003c/a\u003e ha condiviso la propria esperienza con la rigenerazione dei riepiloghi utilizzando un LLM diverso e le sfide affrontate quando il processo di backfill si è interrotto dopo aver raggiunto il limite di età specificato, nonostante alcuni argomenti fallissero a causa dei limiti di frequenza.

  • Feedback sulla riassunzione IA: \u003ca class="mention" href="/u/markschmucker"\u003e@markschmucker\u003c/a\u003e ha cercato chiarimenti su come gestire i riepiloghi non validi, facendo riferimento a un commento precedente di \u003ca class="mention" href="/u/sam"\u003e@sam\u003c/a\u003e riguardo a potenziali correzioni tramite refactoring o aggiustamento delle persone.

Attività

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

50

Panoramica

La scorsa settimana su meta.discourse.org si è assistito a una vasta gamma di discussioni sulle funzionalità AI di Discourse, con gli utenti che hanno condiviso le loro esperienze, fornito feedback e cercato supporto. La community ha esplorato l’integrazione tra Discord e Discourse, il potenziale dei bot Q&A basati sull’IA e le capacità del rilevamento spam potenziato dall’IA. Inoltre, ci sono state conversazioni sulla nuova funzionalità Smart Dates in Helper, sull’AI Persona Editor e sulla disponibilità delle funzionalità AI nei piani Standard e Business.

Argomenti Interessanti

  • Usi Discord e Discourse? ha dato il via a una discussione sull’uso simultaneo di Discord e Discourse, sui loro rispettivi punti di forza e sul potenziale di un bot Q&A Discord potenziato dall’IA che sfrutti Discourse come base di conoscenza.

  • Scrivi date più intelligenti con l’IA ha introdotto la nuova funzionalità Smart Dates in Helper, che converte tempi e date digitati dall’utente in formati compatibili con Discourse e adatti ai fusi orari.

  • Rilevamento spam potenziato dall’IA ha evidenziato l’efficienza del sistema di rilevamento spam potenziato dall’IA di Discourse, con utenti che hanno riportato esperienze positive nell’identificazione e nascondimento dei post spam.

  • Discourse AI - AI triage ha esplorato la funzionalità di triage AI, che automatizza la categorizzazione degli argomenti utilizzando modelli AI, portando a discussioni sulla scalabilità e configurazione di questa funzionalità.

  • Feedback per riassunti AI, brevi riassunti nella lista argomenti ha raccolto feedback sul valore e sui potenziali miglioramenti per i brevi riassunti generati dall’IA visualizzati nella lista argomenti.

  • Eccezione di lavoro: metodo non definito `finish’ per nil durante l’uso del bot AI ha affrontato un problema riscontrato durante l’utilizzo di un’API personalizzata compatibile con OpenAI con il plugin Discourse AI, portando a una discussione sulla compatibilità e sulla risoluzione dei problemi.

  • La correzione bozze è troppo creativa ha evidenziato un caso in cui la funzionalità di correzione bozze AI in Helper ha apportato suggerimenti eccessivamente creativi, stimolando una discussione sul livello appropriato di creatività per tali funzionalità.

  • Richieste di funzionalità per la riassunzione AI ha raccolto richieste di miglioramenti alla funzionalità di riassunzione AI, tra cui la prioritizzazione della riassunzione degli argomenti aggiornati di recente e la possibilità di saltare la riassunzione dei messaggi personali.

  • Come nascondere completamente il bot, per tutti ha affrontato la richiesta di un utente di nascondere il bot AI di Discourse dalla propria community, portando a una discussione sui limiti e sulle potenziali soluzioni.

  • Discourse AI - Helper ha continuato la discussione in corso sulla funzionalità Helper, con gli utenti che hanno fornito feedback e cercato chiarimenti sulla sua funzionalità.

Attività

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

51

Riepilogo settimanale sull’IA su meta.discourse.org

Panoramica

Questa settimana sul forum meta.discourse.org, le discussioni hanno riguardato vari aspetti del plugin Discourse AI, tra cui nuove funzionalità, miglioramenti e richieste degli utenti. Lo strumento di rilevamento spam basato sull’IA ha attirato l’attenzione, con gli utenti che cercavano chiarimenti sulla sua configurazione e utilizzo. Inoltre, è stata introdotta la funzionalità “Ask Discourse”, che consente agli utenti di interagire con un personaggio AI per assistenza alla documentazione. Altri argomenti includevano tabelle di sentiment ordinabili, gestione di contenuti dettagliati con l’IA, rigenerazione di riepiloghi di argomenti e gestione delle quote di utilizzo dell’IA.

Argomenti interessanti

  • @per1234 ha evidenziato un problema in cui gli LLM predefiniti non erano selezionabili nella scheda “Spam”, nonostante fossero configurati. @sam ha riconosciuto il problema e fornito una soluzione.

  • @Saif ha introdotto la funzionalità Ask Discourse, che consente agli utenti di interagire con un personaggio AI per cercare nella documentazione e rispondere a domande comuni relative a Discourse.

  • @noahl ha richiesto la possibilità di ordinare le tabelle di sentiment dai numeri più alti ai più bassi, rendendo più facile identificare e affrontare i sentimenti comuni.

  • @c12gene ha sollevato una preoccupazione riguardo all’incapacità del bot AI di leggere ed elaborare contenuti dettagliati racchiusi nei tag [summary], stimolando discussioni sull’ingegneria dei prompt e sull’uso degli strumenti.

  • @awesomerobot ha fornito un aggiornamento sul problema della chiusura della casella di riepilogo AI, con un link alla pull request pertinente.

  • @markschmucker ha chiesto informazioni sulla limitazione del numero di token AI che un utente può utilizzare al giorno, e @sam ha fornito un link a una pull request in arrivo che affronta questa funzionalità.

  • @EricGT ha condiviso approfondimenti sulle valutazioni dei prompt LLM, sottolineando l’importanza di comprendere l’efficacia dei prompt per lo sviluppo di LLM.

  • @sam ha annunciato una funzionalità in arrivo per limiti rigidi sull’utilizzo dell’IA per gruppi di utenti per bot AI e AI Helper, consentendo agli amministratori di definire limiti sul numero totale di token e richieste per gruppo.

  • @per1234 ha segnalato un bug in cui post e account non venivano sempre ripristinati quando una segnalazione del rilevamento spam di Discourse AI veniva rifiutata.

  • @Moin ha cercato indicazioni su come nascondere completamente il bot da tutti gli utenti, stimolando una discussione sulla visibilità del bot nei risultati di ricerca.

Attività

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

2 Mi Piace
52

Weekly AI Summary on meta.discourse.org

Overview

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

Interesting Topics

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

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

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

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

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

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

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

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

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

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

Activity

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

53

Weekly AI Activity Summary on meta.discourse.org

Overview

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

Interesting Topics

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

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

  • LLM Quotas for Discourse AI (ref)

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

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

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

  • Moderation tool for formatting code with AI (ref)

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

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

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

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

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

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

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

  • Discourse AI - AI usage (ref)

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

  • AI helper is hiding. Again (ref)

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

Activity

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

54

Panoramica

Questa settimana su meta.discourse.org, le discussioni si sono concentrate su problemi, funzionalità e integrazioni relativi all’IA. Gli argomenti chiave includevano il debug della chat IA, la configurazione del rilevamento dello spam IA, l’utilizzo di modelli di ragionamento come DeepSeek-R1 ed l’esplorazione delle capacità del plugin AI Helper. Gli utenti hanno condiviso approfondimenti su confronti di costi, valutazioni delle prestazioni e potenziali casi d’uso per vari modelli linguistici.

Argomenti Interessanti

  • @dsims ha riscontrato un problema con la funzionalità di illustrazione dei post di AI Helper, che ha portato a una discussione sull’aggiornamento delle impostazioni richieste. [ref](AI-Helper post illustration error. ai_openai_api_key missing)

  • @oppman ha cercato una guida sull’integrazione dell’IA con siti esterni e repository GitHub per una community di sviluppatori software. [ref](AI Integration with Specific External Sites and GitHub)

  • Gli utenti hanno discusso costi e prestazioni del modello di ragionamento DeepSeek-R1 rispetto ad altri modelli linguistici come GPT-4 e Claude. [ref](DeepSeek provider support? What to do when model provider isn’t in “Provider” list?)

  • @MachineScholar ha segnalato un errore casuale durante l’interazione con il modello DeepSeek-R1 tramite AI Bot. [ref](DeepSeek-R1 randomly producing “Job exception: undefined method `finish’ for nil” error)

  • @Don ha chiesto informazioni sull’aumento del numero massimo di utilizzi consecutivi degli strumenti nelle risposte dell’IA, il che ha portato a una discussione su potenziali soluzioni. [ref](Max consecutive tool usage in the answer)

  • @Eric_Platzek ha cercato assistenza per il debug della chat IA e per chiarire l’utilizzo e i costi associati ai diversi modelli linguistici. [ref](Debugging AI chat)

  • @markschmucker ha condiviso la sua esperienza con la funzionalità AI Web Artifacts e ha chiesto informazioni sull’editing del codice generato e sull’avvio di nuovi contesti con artefatti esistenti. [ref](Announcing: AI Web Artifacts)

  • @NKERIFAC_CLAUD_NBAPNON ha riscontrato un problema con la configurazione degli embedding di Discourse AI dopo un aggiornamento, che ha portato a una discussione sulla risoluzione dei problemi e sui passaggi di configurazione. [ref](Problems with Discouse AI embeddings configuration)

Attività

  • @sam ha fornito approfondimenti sull’esportazione dei post del forum per il caricamento manuale in modelli linguistici esterni utilizzando Data Explorer. [ref](Exporting all Forum Posts for Manual Upload into External LLMs?)

  • @Roman_Rizzi ha condiviso aggiornamenti sulla risoluzione dei problemi relativi al plugin AI che rendeva i post illeggibili nell’ultima versione di Discourse. [ref](AI Plugin Causes All Posts to Be Unreadable in Latest Discourse Version)

  • @BrianC ha chiesto informazioni sulla gestione dei file di testo caricati nelle persone IA e sulla possibilità di modificare i contenuti indicizzati. [ref](Discourse AI Persona, upload support)

  • @Saif ha fornito chiarimenti sulle differenze tra il rilevamento dello spam IA e il triage IA, nonché indicazioni sulla segnalazione di singoli post rispetto ad argomenti interi. [ref](Setting up spam detection in your community)

  • @per1234 ha segnalato un problema in cui i post e gli account non venivano sempre ripristinati quando le segnalazioni del rilevamento dello spam di Discourse AI venivano rifiutate, portando a una discussione su potenziali soluzioni. [ref](Posts and account not always restored when flag from Discourse AI spam detection rejected)

  • @dsims ha suggerito di aggiungere un parametro di qualità per la funzionalità di generazione di immagini Dall-E 3 per ridurre i costi. [ref](Image sizes of Dall-E 3?)

  • @bugtracker ha chiesto informazioni sull’utilizzo di DeepSeek con il plugin Discourse AI. [ref](Discourse AI)

  • @StefanoCecere ha condiviso un suggerimento per includere il nome del giorno quando si generano date con AI Helper. [ref](Write out smarter dates with AI)

  • @BrianC ha espresso interesse per il caricamento e la discussione di PDF nella funzionalità composer. [ref](Upload and discuss pdfs in composer)

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

55

Overview

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

Interesting Topics

Activity

User Contributions Across Topics

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

56

Overview

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

Interesting Topics

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

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

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

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

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

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

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

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

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

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

Activity

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

57

Overview

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

Interesting Topics

Activity

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

58

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

Interesting Topics

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

Activity

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

59

Overview

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

Interesting Topics

Activity

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

60

Overview

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

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

Interesting Topics

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

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

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

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

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

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

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

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

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

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

Activity

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

61

Overview

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

Interesting Topics

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

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

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

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

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

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

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

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

Activity

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

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

62

Overview

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

Interesting Topics

Activity

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

63

Weekly Summary of AI Activity on Meta.discourse.org

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

Overview

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

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

Interesting Topics

Activity

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

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

64

Overview

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

Interesting Topics

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

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

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

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

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

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

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

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

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

Activity

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

65

Riepilogo Attività Settimanale sull’IA (21/04/2025 - 28/04/2025)

Panoramica

Nell’ultima settimana, la community si è dedicata a migliorare le capacità, l’usabilità e la stabilità di Discourse AI. Sul fronte Feature, i membri hanno esplorato l’aggiunta di un’azione “Bozza risposta” con un clic alla barra degli strumenti dell’IA Utilizzo dell’IA per assistere nella risposta a nuovi post in Discourse e hanno presentato le prime iterazioni per elencare e filtrare le conversazioni generate dall’IA nella pagina Messaggi Elenco delle conversazioni con intelligenza artificiale su una pagina separata o filtraggio nella pagina dei messaggi. Nelle discussioni di Support, sono stati quantificati i compromessi tra costo e qualità delle dimensioni dei file dei persona Più file persona aumentano le spese di richiesta LLM?, mentre sono stati perfezionati i modelli di paternità di bot modulari Creazione di chatbot IA modulari e chiarita la visibilità degli strumenti personalizzati rispetto a quelli integrati Possiamo visualizzare tutti gli strumenti e le loro configurazioni nell’IA. Sul fronte UX, una semplice modifica CSS ha risolto il posizionamento delle icone nella composizione L’icona IA per l’helper di categoria è posizionata sopra il menu + e numerosi report Bug hanno visto chiusure dopo miglioramenti di validazione Validare il campo Nome per gli strumenti IA e la risoluzione di un problema di “generazione bloccata” L’helper IA bloccato nella generazione. Il risultato è un ecosistema più intuitivo, performante ed economicamente vantaggioso.

Argomenti Interessanti

  • \u003ca class="mention" href="/u/wlandgraf"\u003ewlandgraf\u003c/a\u003e ha promosso un pulsante Bozza risposta per consentire ai moderatori di invocare risposte generate dall’IA su richiesta, scatenando suggerimenti per collegare l’azione tramite persona e la barra degli strumenti dell’IA Utilizzo dell’IA per assistere nella risposta a nuovi post in Discourse (Feature, ai).

  • \u003ca class="mention" href="/u/isaac"\u003eisaac\u003c/a\u003e ha annunciato che la possibilità di elencare e filtrare le conversazioni assistite dall’IA è atterrata nel plugin discourse-ai, pre-visualizzata e lodata da \u003ca class="mention" href="/u/kuaza"\u003ekuaza\u003c/a\u003e in Elenco delle conversazioni con intelligenza artificiale su una pagina separata o filtraggio nella pagina dei messaggi (Feature, ai).

  • \u003ca class="mention" href="/u/wlandgraf"\u003ewlandgraf\u003c/a\u003e ha chiesto se il caricamento di molti file persona aumenti i costi delle richieste LLM, e \u003ca class="mention" href="/u/Falco"\u003eFalco\u003c/a\u003e ha spiegato la formula “Chunk di caricamento token” × “Chunk di conversazione di ricerca” per ottimizzare le spese Più file persona aumentano le spese di richiesta LLM? (Support, ai).

  • \u003ca class="mention" href="/u/Yenwod"\u003eYenwod\u003c/a\u003e e \u003ca class="mention" href="/u/kuaza"\u003ekuaza\u003c/a\u003e hanno iterato sui prompt per una famiglia di VaccineBot, mentre \u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e ha proposto uno strumento JS personalizzato per caricare solo il sottoinsieme pertinente dai caricamenti Creazione di chatbot IA modulari (Support, ai-bot).

  • \u003ca class="mention" href="/u/Moin"\u003eMoin\u003c/a\u003e ha notato l’icona IA che oscurava il menu + nella composizione, e \u003ca class="mention" href="/u/awesomerobot"\u003eawesomerobot\u003c/a\u003e ha confermato che la stessa correzione si applica come in un precedente argomento UX L’icona IA per l’helper di categoria è posizionata sopra il menu + (UX, ai-helper).

  • \u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e ha verificato che il campo Nome strumento ora applica la validazione, chiudendo un bug di lunga data Validare il campo Nome per gli strumenti IA (Bug, ai).

  • \u003ca class="mention" href="/u/wlandgraf"\u003ewlandgraf\u003c/a\u003e ha richiesto una dashboard per ispezionare gli script e i parametri di tutti gli strumenti IA, e \u003ca class="mention" href="/u/Falco"\u003eFalco\u003c/a\u003e ha chiarito che gli strumenti integrati (Ruby) differiscono dagli strumenti JS personalizzati Possiamo visualizzare tutti gli strumenti e le loro configurazioni nell’IA (Support, ai).

  • \u003ca class="mention" href="/u/keegan"\u003ekeegan\u003c/a\u003e ha stabilito che la lingua dell’helper IA del compositore segue la locale del Sito, e dopo il debug PM con \u003ca class="mention" href="/u/MachineScholar"\u003eMachineScholar\u003c/a\u003e, un aggiornamento core+plugin ha risolto il blocco della generazione del menu L’helper IA bloccato nella generazione (Bug, ai-helper).

  • \u003ca class="mention" href="/u/Justin_Gonzalez"\u003eJustin_Gonzalez\u003c/a\u003e ha chiesto informazioni sull’indicizzazione di Discourse tramite Glean, e \u003ca class="mention" href="/u/Falco"\u003eFalco\u003c/a\u003e ha suggerito di utilizzare un user-agent crawler o Discourse AI per far emergere contenuti nascosti Indicizzazione dei contenuti della community di Discourse in Glean AI (Support, ai).

  • \u003ca class="mention" href="/u/Jagster"\u003eJagster\u003c/a\u003e ha segnalato allucinazioni diffuse dalla funzione explaining, sollecitando consigli sulla scelta del modello e sulle modifiche ai prompt L’helper IA hallucina molto quando spiega qualcosa (Support, ai-helper, ai-custom-prompt).

Attività

\u003ca class="mention" href="/u/sam"\u003esam\u003c/a\u003e (14 like, 15 post)
• Ha guidato la discussione sulla funzionalità “Bozza risposta” 363298/5?silent=true
• Ha confermato la validazione del nome dello strumento 330830/2?silent=true
• Ha proposto uno strumento JS personalizzato per i flussi di VaccineBot 361807/10?silent=true
• Ha condiviso una demo dell’helper GitHub 363437/4?silent=true
• Ha gestito e chiuso più bug:
– Link a sottocartelle 278007/3?silent=true
– Rimozione bozza PM 336927/7?silent=true
– Interruzione bot chat 318546/2?silent=true
– Errore creazione utente 312281/6?silent=true
– Tab UI chat 285403/4?silent=true
– Dropdown alla selezione 305688/3?silent=true
– Supporto Gemini 312280/6?silent=true
– Modello report periodico 293762/6?silent=true
– Correzione eccezione job 344935/3?silent=true

\u003ca class="mention" href="/u/Falco"\u003eFalco\u003c/a\u003e (9 like, 4 post)
• Ha spiegato la formula dei costi nei file persona 363440/3?silent=true e 363440/5?silent=true
• Ha chiarito le differenze di visibilità degli strumenti 363437/3?silent=true
• Ha consigliato sull’approccio all’indicizzazione di Glean 363335/4?silent=true

\u003ca class="mention" href="/u/wlandgraf"\u003ewlandgraf\u003c/a\u003e (5 like, 5 post)
• Ha richiesto il pulsante IA “Bozza risposta” 363298/1?silent=true e 363298/4?silent=true
• Ha messo in discussione l’impatto dei costi dei persona 363440/1?silent=true e 363440/4?silent=true
• Ha chiesto una vista dashboard degli strumenti 363437/1?silent=true

\u003ca class="mention" href="/u/kuaza"\u003ekuaza\u003c/a\u003e (4 like, 2 post)
• Ha celebrato l’arrivo del filtraggio delle conversazioni IA 362711/8?silent=true
• Ha condiviso idee sui prompt di VaccineBot 361807/9?silent=true

\u003ca class="mention" href="/u/isaac"\u003eisaac\u003c/a\u003e (4 like, 1 post)
• Ha annunciato il merge della PR per l’elenco delle conversazioni 362711/7?silent=true

\u003ca class="mention" href="/u/keegan"\u003ekeegan\u003c/a\u003e (3 like, 2 post)
• Ha indagato sul blocco dell’helper, abilitato il debug PM 362643/7?silent=true e 362643/8?silent=true

\u003ca class="mention" href="/u/awesomerobot"\u003eawesomerobot\u003c/a\u003e (3 like, 2 post)
• Ha confermato che non esiste ancora un’opzione integrata “Bozza risposta” 363298/3?silent=true
• Ha applicato la correzione UX dalla precedente patch modale 363692/4?silent=true

\u003ca class="mention" href="/u/maiki"\u003emaiki\u003c/a\u003e (3 like, 1 post)
• Ha validato il campo nome strumento nell’interfaccia di amministrazione 330830/3?silent=true

\u003ca class="mention" href="/u/Moin"\u003eMoin\u003c/a\u003e (3 like, 1 post)
• Ha segnalato il problema di clipping dell’icona IA nel compositore 363692/1?silent=true

\u003ca class="mention" href="/u/Yenwod"\u003eYenwod\u003c/a\u003e (2 like, 2 post)
• Ha sperimentato sugli strumenti di VaccineBot 361807/8?silent=true e 361807/11?silent=true

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

66

Panoramica

“Questo componente tematico aggiunge un pulsante a ogni post, consentendo agli utenti di inviare il post a un bot AI per l’analisi tramite un messaggio di chat diretto.” — Don, AI Post Analyzer for Chat

La scorsa settimana (28/04/2025 - 05/05/2025) su #meta.discourse.org è stata ricca di miglioramenti ai e discussioni approfondite:

L’introduzione di AI Post Analyzer for Chat ha fornito un utile pulsante AI in chat, il rilascio OpenAI image generation and editing now supported in Discourse AI ha portato i flussi di lavoro GPT-image-1 in Announcements, la discussione Is an automation like this possible with Discourse AI today? ha esplorato l’automazione dei riassunti degli annunci di prodotto, A Plug-In to convert Discourse Forum Discussions into Clear Proposal Revisions with Community-Sourced Justifications ha proposto SimScore per la governance, e l’argomento di supporto AI changed quite many gists in English ha affrontato i problemi di mix linguistico guidati dai prompt.

Vivaci approfondimenti hanno rivisitato AI Post Analyzer for Chat per la guida alla ridenominazione, hanno stimolato test su OpenAI image generation and editing now supported in Discourse AI, hanno affinato la logica in Is an automation like this possible with Discourse AI today?, hanno affrontato i vincoli di hosting nella discussione del plugin SimScore (A Plug-In to convert Discourse Forum Discussions into Clear Proposal Revisions with Community-Sourced Justifications) e hanno gestito la pulizia del database in AI changed quite many gists in English.

Dal lato degli strumenti, The complete list of variables used in AI prompts ha suscitato richieste di documentazione completa, la discussione AI helper hallucinating a lot when explaining something ha rivelato le stranezze del modello, How to install and configure AI features step by step ha chiarito la configurazione dei plugin, la discussione AI Assistants with Web Search capability ha confermato la flessibilità degli agenti personalizzati e Provide visual cue when a topic is receiving an AI response ha evidenziato miglioramenti all’UX.

Aggiornamenti successivi hanno richiesto l’espansione di The complete list of variables used in AI prompts per la personalizzazione della persona, hanno offerto suggerimenti per lo scambio di modelli nella discussione AI helper hallucinating a lot when explaining something, hanno migliorato la guida all’installazione in How to install and configure AI features step by step, hanno testato l’integrazione della ricerca web in AI Assistants with Web Search capability e hanno discusso pattern di progettazione in Provide visual cue when a topic is receiving an AI response.

Argomenti Interessanti

Attività

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

67

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

Overview

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

Interesting Topics

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

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

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

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

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

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

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

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

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

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

Activity

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

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