Discourse
discourse.orgA fully open-source, self-hostable discussion platform usable as a mailing list, discussion forum, or long-form chat room.
- Homepage: discourse.org
- GitHub: github.com/discourse/discourse
- Privacy: discourse.org/privacy
- Web info: web-check.xyz/results/discourse.org
Discourse Privacy Policy
Privacy Policy Summary
- Third-party cookies are used for statistics
- Third-party cookies are used for advertising
- A list of all cookies set by the website is provided
- Your personal data is not sold
- Information is provided about how your personal data is used
- Third parties are involved in operating the service
- Information is provided about how they collect personal data
- You can opt out of promotional communications
- Do Not Track (DNT) headers are ignored and you are tracked anyway even if you set this header.
- The service claims to be GDPR compliant for European users
- You can request access, correction and/or deletion of your data
- This Service provides a list of Third Parties involved in its operation.
- This service gives your personal data to third parties involved in its operation
- Instructions are provided on how to submit a copyright claim
- Your data may be processed and stored anywhere in the world
- The service claims to be CCPA compliant for California users
- The service is open-source
- Your personal data is aggregated into statistics
- There is a date of the last update of the agreements
- Under the GDPR, a complaint mechanism is provided for the handling of personal data
- If you are the target of a copyright holder's take down notice, this service gives you the opportunity to defend yourself
Documents
- Privacy PolicyCreated 16 Jan 21, Last modified 1 year ago
- Copyright PolicyCreated 16 Jan 21, Last modified 1 year ago
Domains Covered by Policy
- discourse.org
- rubytalk.org
About the Data
This data is kindly provided by tosdr.org. Read full report at: #1340
Discourse Source Code
Author
Description
A platform for community discussion. Free, open, simple.
Homepage
https://www.discourse.orgLicense
GPL-2.0
Created
12 Jan 13
Last Updated
29 Apr 24
Latest version
Primary Language
Ruby
Size
630,640 KB
Stars
40,520
Forks
8,134
Watchers
40,520
Language Usage
Star History
Top Contributors
- @SamSaffron (6649)
- @eviltrout (6610)
- @tgxworld (4460)
- @ZogStriP (3590)
- @nlalonde (2678)
- @jjaffeux (2673)
- @coding-horror (2166)
- @davidtaylorhq (2122)
- @arpitjalan (1938)
- @dependabot[bot] (1861)
- @awesomerobot (1447)
- @CvX (1250)
- @pmusaraj (1162)
- @martin-brennan (1145)
- @gschlager (1046)
- @nbianca (762)
- @vinothkannans (734)
- @riking (506)
- @OsamaSayegh (436)
- @lis2 (416)
- @romanrizzi (416)
- @oblakeerickson (414)
- @danielwaterworth (397)
- @dependabot-preview[bot] (385)
- @udan11 (380)
- @xfalcox (365)
- @markvanlan (364)
- @AndrewPrigorshnev (283)
- @janzenisaac (229)
- @discourse-translator-bot (215)
Recent Commits
- Jarek Radosz (29 Apr 24)
DEV: Convert topic-title to glimmer/gjs (#26808) This reverts commit 5d568d0bab1ccbb1e6e89e9f151958b3566bfe1c. (reland of #26775) Now with removed unnecessary `?.` operators to workaround a terser/babel/??? issue.
- Régis Hanol (29 Apr 24)
DEV: fix the fix for flakey test 😓 We should not be clearing **all** the advanced search filters and orders, because some are required by the application.
- Gerhard Schlager (29 Apr 24)
DEV: Import script should use case-insensitive lookup for tags (#26780)
- Gerhard Schlager (29 Apr 24)
DEV: Add support for `user_associated_accounts` to import script (#26779)
- Gerhard Schlager (29 Apr 24)
DEV: Import script should use case-insensitive check for tag names (#26699)
- Jan Cernik (29 Apr 24)
DEV: Refactor topic admin menu to use `<DMenu>` (#26678) * DEV: Refactor topic admin menu to use `<DMenu>` This PR also introduces a new plugin API to add buttons to the topic admin menu ```javascript api.addTopicAdminMenuButton((topic) => { return { action: () => { alert('Sunrise!'); }, icon: 'sun', className: 'sunrise-button', label: 'actions.rise', }; }); ``` The plugins that needed to be updated are: - [discourse-zoom](https://github.com/discourse/discourse-zoom/pull/73) - [discourse-salesforce](https://github.com/discourse/discourse-salesforce/pull/74) - [discourse-topic-noindex](https://github.com/discourse/discourse-topic-noindex/pull/11)
- Jan Cernik (29 Apr 24)
FIX: Do not show hidden posts in search results (#26800)
- Régis Hanol (29 Apr 24)
DEV: cleanup custom filters to prevent leaks Ensures we clean up any custom filters added in the specs to prevent any leaks when running the specs. Follow up to https://github.com/discourse/discourse/pull/26770#discussion_r1582464760
- Joffrey JAFFEUX (29 Apr 24)
FIX: correctly check the user id of the original message (#26805) Followup: write a test for this
- Vinoth Kannan (29 Apr 24)
FEATURE: Allow watched words to be created as a group (#26632) At the moment, there is no way to create a group of related watched words together. If a user needed a set of words to be created together, they'll have to create them individually one at a time. This change attempts to allow related watched words to be created as a group. The idea here is to have a list of words be tied together via a common `WatchedWordGroup` record. Given a list of words, a `WatchedWordGroup` record is created and assigned to each `WatchedWord` record. The existing WatchedWord creation behaviour remains largely unchanged. Co-authored-by: Selase Krakani <[email protected]> Co-authored-by: Martin Brennan <[email protected]>
- David Battersby (29 Apr 24)
FEATURE: encourage users to set chat thread titles (#26617) This change encourages users to title their threads to make it easier for other users to join in on conversations that matter to them. The creator of the chat thread will receive a toast notification prompting them to add a thread title when on mobile and the thread has at least 5 sent replies.
- David Taylor (29 Apr 24)
DEV: Log original exception/backtrace for RequestTracker errors (#26802)
- Joffrey JAFFEUX (29 Apr 24)
FIX: correctly enable/disable body scroll on modal (#26784)
- Joffrey JAFFEUX (29 Apr 24)
FIX: correctly rename scroller everywhere (#26783)
- Martin Brennan (29 Apr 24)
UX: Fix report color duplication (#26799) In the "Consolidated Pageviews with Browser Detection (Experimental)" report we used the same color for "Known Crawler" and "Other pageviews" which makes the report confusing to look at, this commit makes them different.
- Martin Brennan (29 Apr 24)
DEV: Try fix flaky sidebar filter spec (#26797) We were getting this error causing it to flake when creating users: ``` ActiveRecord::StatementInvalid: PG::ReadOnlySqlTransaction: ERROR: cannot execute INSERT in a read-only transaction ```
- Krzysztof Kotlarek (29 Apr 24)
DEV: fix flaky admin_customize_themes spec (#26798) Because spec is searching for "5", we need to be sure that "Cool theme 5" is created.
- Krzysztof Kotlarek (29 Apr 24)
FEATURE: new admin sidebar for moderators (#26795) Enable a new sidebar for moderators with limited links.
- Charley Sheets (29 Apr 24)
DEV: Fix confusing comment (#26781)
- Jarek Radosz (29 Apr 24)
Revert "DEV: Convert topic-title to glimmer/gjs (#26775)" (#26794) This reverts commit 261ef8404ee63a013037fd25322b02843ec6500b.
- Martin Brennan (29 Apr 24)
FIX: Better tracking of topic visibility changes (#26709) This commit introduces a few changes as a result of customer issues with finding why a topic was relisted. In one case, if a user edited the OP of a topic that was unlisted and hidden because of too many flags, the topic would get relisted by directly changing topic.visible, instead of going via TopicStatusUpdater. To improve tracking we: * Introduce a visibility_reason_id to topic which functions in a similar way to hidden_reason_id on post, this column is set from the various places we change topic visibility * Fix Post#unhide! which was directly modifying topic.visible, instead we use TopicStatusUpdater which sets visibility_reason_id and also makes a small action post * Show the reason topic visibility changed when hovering the unlisted icon in topic status on topic titles
- Martin Brennan (29 Apr 24)
DEV: Add pry-stack_explorer again (#26763) This was reverted in 26a387c9c63ea86c2620bfaea2ecb3d32a3327cf because the other pry gem changes there broke prod -- it should be safe to just add this dev/test dependency
- dependabot[bot] (29 Apr 24)
Build(deps-dev): Bump selenium-webdriver from 4.20.0 to 4.20.1 (#26793)
- dependabot[bot] (28 Apr 24)
Build(deps-dev): Bump babel-import-util from 2.0.3 to 3.0.0 (#26786) Bumps [babel-import-util](https://github.com/ef4/babel-import-util) from 2.0.3 to 3.0.0. - [Release notes](https://github.com/ef4/babel-import-util/releases) - [Changelog](https://github.com/ef4/babel-import-util/blob/main/CHANGELOG.md) - [Commits](https://github.com/ef4/babel-import-util/compare/v2.0.3...v3.0.0) --- updated-dependencies: - dependency-name: babel-import-util dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- dependabot[bot] (28 Apr 24)
Build(deps-dev): Bump rubocop from 1.63.3 to 1.63.4 (#26789) Bumps [rubocop](https://github.com/rubocop/rubocop) from 1.63.3 to 1.63.4. - [Release notes](https://github.com/rubocop/rubocop/releases) - [Changelog](https://github.com/rubocop/rubocop/blob/master/CHANGELOG.md) - [Commits](https://github.com/rubocop/rubocop/compare/v1.63.3...v1.63.4) --- updated-dependencies: - dependency-name: rubocop dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- dependabot[bot] (28 Apr 24)
Build(deps-dev): Bump @floating-ui/dom from 1.6.3 to 1.6.4 (#26785) Bumps [@floating-ui/dom](https://github.com/floating-ui/floating-ui/tree/HEAD/packages/dom) from 1.6.3 to 1.6.4. - [Release notes](https://github.com/floating-ui/floating-ui/releases) - [Changelog](https://github.com/floating-ui/floating-ui/blob/master/packages/dom/CHANGELOG.md) - [Commits](https://github.com/floating-ui/floating-ui/commits/@floating-ui/[email protected]/packages/dom) --- updated-dependencies: - dependency-name: "@floating-ui/dom" dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- dependabot[bot] (28 Apr 24)
Build(deps-dev): Bump parallel_tests from 4.7.0 to 4.7.1 (#26791) Bumps [parallel_tests](https://github.com/grosser/parallel_tests) from 4.7.0 to 4.7.1. - [Changelog](https://github.com/grosser/parallel_tests/blob/master/CHANGELOG.md) - [Commits](https://github.com/grosser/parallel_tests/compare/v4.7.0...v4.7.1) --- updated-dependencies: - dependency-name: parallel_tests dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- dependabot[bot] (28 Apr 24)
Build(deps-dev): Bump parser from 3.3.0.5 to 3.3.1.0 (#26790) Bumps [parser](https://github.com/whitequark/parser) from 3.3.0.5 to 3.3.1.0. - [Changelog](https://github.com/whitequark/parser/blob/master/CHANGELOG.md) - [Commits](https://github.com/whitequark/parser/compare/v3.3.0.5...v3.3.1.0) --- updated-dependencies: - dependency-name: parser dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- dependabot[bot] (28 Apr 24)
Build(deps-dev): Bump ember-cli from 5.8.0 to 5.8.1 (#26787) Bumps [ember-cli](https://github.com/ember-cli/ember-cli) from 5.8.0 to 5.8.1. - [Release notes](https://github.com/ember-cli/ember-cli/releases) - [Changelog](https://github.com/ember-cli/ember-cli/blob/master/CHANGELOG.md) - [Commits](https://github.com/ember-cli/ember-cli/compare/v5.8.0...v5.8.1) --- updated-dependencies: - dependency-name: ember-cli dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- Jarek Radosz (27 Apr 24)
DEV: Inline cancel-link code (#26778) No need for this small component (and its unused and empty admin component twin)
Discourse Website
Website
Discourse is the place to build civilized communities | Discourse - Civilized Discussion
Discourse is modern forum software for your community. Use it as a mailing list, discussion forum, long-form chat room, and more!
Redirects
Does not redirect
Security Checks
All 66 security checks passed
Server Details
- IP Address 18.160.78.66
- Hostname server-18-160-78-66.atl59.r.cloudfront.net
- Location Atlanta, Georgia, United States of America, NA
- ISP Amazon.com Inc.
- ASN AS16509
Associated Countries
- US
Saftey Score
Website marked as safe
100%
Blacklist Check
www.discourse.org was found on 0 blacklists
- ThreatLog
- OpenPhish
- PhishTank
- Phishing.Database
- PhishStats
- URLhaus
- RPiList Not Serious
- AntiSocial Blacklist
- PhishFeed
- NABP Not Recommended Sites
- Spam404
- CRDF
- Artists Against 419
- CERT Polska
- PetScams
- Suspicious Hosting IP
- Phishunt
- CoinBlockerLists
- MetaMask EthPhishing
- EtherScamDB
- EtherAddressLookup
- ViriBack C2 Tracker
- Bambenek Consulting
- Badbitcoin
- SecureReload Phishing List
- Fake Website Buster
- TweetFeed
- CryptoScamDB
- StopGunScams
- ThreatFox
- PhishFort
Website Preview
Discourse Reviews
More Social Networks
-
Offers self-governing communities with auditable moderation, akin to Reddit but prioritizing privacy, democracy, and transparency. Aether is peer-to-peer and open source, available for Windows, Mac, and Linux.
-
An open-source, distributed social media platform functioning similarly to Twitter, without algorithmic timeline manipulations. It operates across independent servers.
-
A social media platform designed to foster open conversations and community engagement. Rewards content creation.
About the Data: Discourse
API
You can access Discourse's data programmatically via our API.
Simply make a GET
request to:
https://api.awesome-privacy.xyz/social/social-networks/discourse
The REST API is free, no-auth and CORS-enabled. To learn more, view the Swagger Docs or read the API Usage Guide.
About the Data
Beyond the user-submitted YAML you see above, we also augment each listing with additional data dynamically fetched from several sources. To learn more about where the rest of data included in this page comes from, and how it is computed, see the About the Data section of our About page.
Share Discourse
Help your friends compare Social Networks, and pick privacy-respecting software and services.
Share Discourse and Awesome Privacy with your network!