Discourse Meta forum

This one is new when I entered inside web_only.yml : root@foorumi-hel:/var/discourse# ./launcher enter web_only x86_64 arch detected. bash: warning: setlocale: LC_CTYPE: cannot change locale (fi_FI.UTF-8): No such file or directory bash: warning: setlocale: LC_COLLATE: cannot change locale (fi_FI.UTF-8): No such file or directory bash: warning: setlocale: LC_CTYPE: cannot change locale (fi_FI.UTF-8): No such file or directory bash: warning: setlocale: LC_COLLATE: cannot change locale (fi_FI.UTF-8): No such file or directory Those are coming from this, I reckon: env: # LC_ALL: fi_FI.UTC-8 LANG: fi_FI.UTF-8 LANGUAGE: fi_FI.UTF-8 Do I need to loose my good night sleep because of that?

@pmusaraj I checked this against Rails 8.0.5.1 and 8.1.3.1. A compatibility entry shouldn’t be needed: the corrected association works on both versions. The previous declaration fails to load on Rails 8.1 because it specifies class_name alongside polymorphic: true . The initial report was posted about ~15 minutes before the fix merged, so it could have been from a rebuild without the fix. @Jagster @satonotdead could you try rebuilding again with ActivityPub enabled? If you still get a 502, please share error log from /logs .

I think so: root@foorumi-hel-web-only:/var/www/discourse# bundle exec rails --version Rails 8.1.3.1

Discourse now supports native Markdown endpoints, making it easier for AI tools and other clients to read forum content without parsing full HTML pages. This feature will be enabled by default on all hosted sites via the Upcoming Changes system. Administrators that want to opt out can do so by disabling the enable_markdown_endpoints site setting. Many thanks to @benword for creating the original Discourse to Markdown plugin , it was the precursor to this feature in Discourse core. The Markdown output is generated from posts’ rendered (“cooked”) HTML, preserving the content readers see, including expanded links and processed formatting. Discourse-specific elements such as quotes, oneboxes, code blocks, polls, and collapsible sections are converted back to Markdown. Topic responses include metadata and pagination links, and converted post bodies are cached using a content digest so edits produce fresh output. Clients can request Markdown explicitly through .md URLs or by sending an Accept: text/markdown header. Negotiation respects quality values and selects Markdown when it is preferred over HTML and JSON; explicit .md requests retain their formats. Supported HTML pages advertise their Markdown equivalent through an HTTP Link header and a element.

chapoi: We’re all using AI heavily these days to develop it. It is unfortunate it has to be like this because I still have strong ethical concerns with how AI companies basically just steal code from the Internet, destroy books, and otherwise run abusive crawlers that steal everything without respecting the host server (even when you look past the unnecessary DRAM crisis!) all to make it out first in the LLM race that nobody wanted. I’ve already stopped using a lot of apps because the quality of code has degraded so much, like VS Code, which became slow and memory-inefficient and generally buggy. Formbricks’ upgrade packages stopped working, my music player got slow and bloated (once adding features becomes so easy you begin to lose project scope and add everything), and stopped playing music half the time. But the issue is I like Discourse so I don’t want to stop using it. It’s not like an IDE or music player where I have no attachment or even my OS because I already hated Windows before I stopped using it in 2024. Unless the software gets extremely buggy or slow as a result of LLMs it’s unlikely I’ll decide to stop using it. I’m not looking to be entirely “black or white” about this whole situation but I can’t get over the ethical or privacy concerns that come attached with using a LLM.

I’ve just noticed on a forum which requires signup approval, you submit your email address, type the six-digit code, then see this: “Your account hasn’t been approved yet. You will be notified by email when you are ready to log in.” This text is a bit topsy turvy since at that point you don’t really feel that you are logging in – you are still registering. Even “Thank you for registering.” as a first sentence would be an improvement. (Also I hope for sites with custom fields, which might help decide whether to approve a user, that the custom fields get filled in before the text above is displayed.)

No, unfortunately I don’t.

I think you can do this via the Rails console. Run: ./launcher enter app rails c to enter the console. Then: DiscourseUserNotes.notes_for(user_id) Replace user_id with the user’s id. This returns a JSON of the user notes.

@darkpixlz Ich weiß nicht, wieso man die Beiträge verschiebt. Die Fehlermeldung erscheint auch mit deaktiviertem Locations-Plugin…

Looks like there was a recent fix FIX: Correct polymorphic attachment association - Pull Request #340 - discourse/discourse-activity-pub - GitHub , do you know if your Discourse core version has Rails 8.1 or not? @techAPJ we may need to add a compatibility entry for this change.

On this highly controversial topic — and given that it’s reasonable to assume AI poses significant risks to our cognitive abilities, privacy, and security… Buchodi's Threat Intel – 20 Sep 26 ChatGPT now knows what you do on other websites via ad collector OpenAI's ad collector at bzr.openai.com sets a cookie called __obi, scoped to .openai.com. The value is while you are on ChatGPT and tied to your ChatGPT account. __obi is then sent to OpenAI from ordinary websites you visit. Any company that buys... I just want to say that I’m grateful for this tool , because it pointed out errors in plugins I built with the help of LLMs that I wouldn’t have been able to find on my own. This is exactly what I commented on in the topic that led to this one. I didn’t have the technical knowledge to question the results themselves, but rather their practical application. Unfortunately, humanity as a whole does not currently always use its critical thinking skills when analyzing actions or responses, and acts on emotions — without realizing it, in a completely unconscious way. This leads us to inaccurate prejudices about the validity or value of something that, when viewed neutrally, is actually improving a given situation. I understand that this is a natural phenomenon that is changing, and not something personal. Just to show my humble support to the OP for this tool.

If you’re following the latest release channel, you can now access settings that allow you to run your own AI bot discussion site like ask.discourse.com ! The new settings are: An ai bot conversations option in the default homepage site setting. To enable this option you must first have ai_bot_enabled turned on. If a user doesn’t have permission to use AI bots, they’ll be directed to the first option in the top_menu setting as a fallback. The option to add anonymous users to the AI bot allowed groups site setting when enabled, anonymous users can’t use the bot, but they can see a preview of the page. If they ask a question, they’ll be directed to login, and the question will persist after they do. To learn more about configuring AI in Discourse check out our overview of the Discourse AI plugin. All our hosted Discourse plans include credits to use with our preconfigured Discourse-hosted LLMs .