A platform for community discussion. Free, open, simple.
Go to file
Sam 7b12be866d
FIX: never skip push notifications (#25099)
* FIX: never skip push notifications

According to Apple, silent push notifications are automatically punished per:

https://developer.apple.com/videos/play/wwdc2022/10098/?time=814

> As mentioned when I showed you the code on how to request a push
> subscription, you must promise that pushes will be user visible.
> Handling a push event is not an invitation for your JavaScript to
> get silent background runtime. Doing so would violate both a user’s
> trust and a user’s battery life. When handling a push event, you are
> in fact required to post a notification to Notification Center.
> Other browsers all have countermeasures against violating the promise
> to make pushes user visible, and so does Safari.
> In the beta build of macOS Ventura, after three push events where you
> fail to post a notification in a timely manner, your site’s push
> subscription will be revoked. You will need to go through the permission
> workflow again.

The isIdle check was causing certain push notifications to be silent

Additionally, the auto dismissal logic was causing delays which may cause
the device to think the push was a silent one.

By removing this we hope to ensure push notification delivery is more robust
and consistent on iOS.
2024-01-03 12:23:04 +11:00
.devcontainer DEV: Replace postCreateCommand with postStartCommand (#16665) 2022-05-05 23:52:35 +02:00
.github DEV: Add "migrations-tooling" label to PRs for import scripts (#25062) 2023-12-28 21:26:05 +01:00
.vscode-sample DEV: introduce Ember <template> tag support (.gjs) (#22719) 2023-07-20 21:01:12 +01:00
app FIX: never skip push notifications (#25099) 2024-01-03 12:23:04 +11:00
bin DEV: Only retry and log flaky tests on the main branch (#24889) 2023-12-14 09:41:30 +08:00
config Update translations (#25088) 2024-01-02 15:25:58 +01:00
db DEV: Convert min_trust_to_allow_self_wiki to groups (#25009) 2023-12-27 09:21:39 +08:00
docs Fix typos and internal links in INSTALL-cloud (#25058) 2023-12-28 20:27:43 +01:00
documentation DEV: Fix random typos (#20937) 2023-04-03 19:27:32 +02:00
images Replace README logo with PNG (#14044) 2021-08-13 14:23:49 -04:00
lib FIX: github onebox styles for commits (#25098) 2024-01-02 17:29:56 -05:00
log
migrations DEV: Add initial structure for migrations-tooling 2023-10-13 16:03:55 +02:00
plugins Update translations (#25088) 2024-01-02 15:25:58 +01:00
public DEV: Use webpack to load table-builder dependencies (#25018) 2024-01-02 10:47:47 +00:00
script DEV: Use webpack to load table-builder dependencies (#25018) 2024-01-02 10:47:47 +00:00
spec FIX: Allow the flags to be cleaned up (#25085) 2024-01-02 18:32:50 +08:00
test DEV: Drop /theme-qunit from smoke test (#23562) 2023-09-13 16:14:27 +01:00
vendor UX: update "discourse-sparkles" icon (#24863) 2023-12-13 15:10:30 +05:30
.editorconfig DEV: Update .editorconfig to match new hbs rules (#19816) 2023-01-10 16:21:16 +01:00
.eslintignore DEV: convert I18n pseudo package into real package (discourse-i18n) (#23867) 2023-10-12 14:44:01 +01:00
.eslintrc.cjs DEV: Use @discourse/lint-configs (#24038) 2023-10-23 12:08:35 +02:00
.git-blame-ignore-revs DEV: Add recent formatting commits to .git-blame-ignore-revs (#19799) 2023-01-09 14:51:48 +00:00
.gitattributes DEV: Remove GitHub gjs highlighting workaround (#24791) 2023-12-08 11:55:20 +00:00
.gitignore FEATURE: Bundle discourse-spoiler-alert plugin into core (#24030) 2023-10-23 13:50:43 -06:00
.jsdoc DEV: Chat service object initial implementation (#19814) 2023-02-13 13:09:57 +01:00
.licensed.yml Build(deps): Bump oj from 3.16.1 to 3.16.2 (#24781) 2023-12-07 23:33:14 +01:00
.licensee.json DEV: Update eslint/prettier (#22226) 2023-06-21 20:59:03 +02:00
.npmrc DEV: Prevent npm usage (#13945) 2021-08-04 22:04:58 +02:00
.prettierignore DEV: Patch deprecated-run-loop-and-computed-dot-access in production (#25074) 2024-01-02 10:44:26 +00:00
.prettierrc.cjs DEV: Use @discourse/lint-configs (#24038) 2023-10-23 12:08:35 +02:00
.rspec Add RSpec 4 compatibility (#17652) 2022-07-28 10:27:38 +08:00
.rspec_parallel
.rubocop.yml Build(deps-dev): Bump rubocop-discourse from 3.4.0 to 3.4.1 (#24375) 2023-11-14 22:56:30 +01:00
.ruby-gemset.sample
.ruby-version.sample DEV: Update recommended Ruby to 3.2.1 (#20444) 2023-02-24 12:51:34 -03:00
.streerc DEV: Apply syntax_tree formatting to app/* 2023-01-09 14:14:59 +00:00
.template-lintrc.js DEV: Use @discourse/lint-configs (#24038) 2023-10-23 12:08:35 +02:00
Brewfile DEV: enable frozen string literal on all files 2019-05-13 09:31:32 +08:00
CODEOWNERS DEV: Add "migrations-tooling" label to PRs for import scripts (#25062) 2023-12-28 21:26:05 +01:00
config.ru DEV: enable frozen string literal on all files 2019-05-13 09:31:32 +08:00
CONTRIBUTING.md
COPYRIGHT.md DEV: Absorb onebox gem into core (#12979) 2021-05-26 15:11:35 +05:30
d
discourse.sublime-project
Gemfile DEV: Update Rails to 7.0.8 (#25084) 2024-01-02 10:19:08 +08:00
Gemfile.lock Build(deps-dev): Bump shoulda-matchers from b8d04ee to 2a2b062 (#25096) 2024-01-02 22:40:23 +01:00
jsconfig.json Enable Embroider/Webpack code spliting for Wizard (#24919) 2023-12-20 13:15:06 +00:00
lefthook.yml DEV: Add syntax_tree check to lefthook (#19877) 2023-01-17 10:16:07 +10:00
LICENSE.txt DEV: Absorb onebox gem into core (#12979) 2021-05-26 15:11:35 +05:30
package.json DEV: Modernise highlightjs loading (#24197) 2023-11-10 20:39:48 +00:00
Rakefile FIX: Do not dump schema during production database migrations (#12785) 2021-04-21 16:26:20 +01:00
README.md FIX: correct link to meta.discourse.org 2023-08-29 13:17:05 +02:00
translator.yml DEV: Fix translator-bot configuration for footnote plugin (#24065) 2023-10-23 23:10:17 +02:00
yarn.lock DEV: Modernise highlightjs loading (#24197) 2023-11-10 20:39:48 +00:00

Discourse is the online home for your community. We offer a 100% open source community platform to those who want complete control over how and where their site is run.

Our platform has been battle-tested for over a decade and continues to evolve to meet users needs for a powerful community platform. Discourse allows you to create discussion topics and connect using real-time chat, as well as access an ever-growing number of official and community themes. In addition, we offer a wide variety of plugins for features ranging from chatbots powered by Discourse AI to functionalities like SQL analysis using the Data Explorer plugin.

To learn more, visit discourse.org and join our support community at meta.discourse.org.

Screenshots

Discourse 3.1

Boing Boing

Mobile

Browse lots more notable Discourse instances.

Development

To get your environment set up, follow the community setup guide for your operating system.

  1. If you're on macOS, try the macOS development guide.
  2. If you're on Ubuntu, try the Ubuntu development guide.
  3. If you're on Windows, try the Windows 10 development guide.
  4. If you're looking to use a simpler Docker-based install, try the Docker development guide.

If you're familiar with how Rails works and are comfortable setting up your own environment, you can also try out the Discourse Advanced Developer Guide, which is aimed primarily at Ubuntu and macOS environments.

Before you get started, ensure you have the following minimum versions: Ruby 3.2+, PostgreSQL 13, Redis 7. If you're having trouble, please see our TROUBLESHOOTING GUIDE first!

Setting up Discourse

If you want to set up a Discourse forum for production use, see our Discourse Install Guide.

If you're looking for official hosting, see discourse.org/pricing.

Requirements

Discourse is built for the next 10 years of the Internet, so our requirements are high.

Discourse supports the latest, stable releases of all major browsers and platforms:

Browsers Tablets Phones
Apple Safari iPadOS iOS
Google Chrome Android Android
Microsoft Edge
Mozilla Firefox

Additionally, we aim to support Safari on iOS 15.7+.

Built With

  • Ruby on Rails — Our back end API is a Rails app. It responds to requests RESTfully in JSON.
  • Ember.js — Our front end is an Ember.js app that communicates with the Rails API.
  • PostgreSQL — Our main data store is in Postgres.
  • Redis — We use Redis as a cache and for transient data.
  • BrowserStack — We use BrowserStack to test on real devices and browsers.

Plus lots of Ruby Gems, a complete list of which is at /main/Gemfile.

Contributing

Build Status

Discourse is 100% free and open source. We encourage and support an active, healthy community that accepts contributions from the public including you!

Before contributing to Discourse:

  1. Please read the complete mission statements on discourse.org. Yes we actually believe this stuff; you should too.
  2. Read and sign the Electronic Discourse Forums Contribution License Agreement.
  3. Dig into CONTRIBUTING.MD, which covers submitting bugs, requesting new features, preparing your code for a pull request, etc.
  4. Always strive to collaborate with mutual respect.
  5. Not sure what to work on? We've got some ideas.

We look forward to seeing your pull requests!

Security

We take security very seriously at Discourse; all our code is 100% open source and peer reviewed. Please read our security guide for an overview of security measures in Discourse, or if you wish to report a security issue.

The Discourse Team

The original Discourse code contributors can be found in AUTHORS.MD. For a complete list of the many individuals that contributed to the design and implementation of Discourse, please refer to the official Discourse blog and GitHub's list of contributors.

Copyright 2014 - 2023 Civilized Discourse Construction Kit, Inc.

Licensed under the GNU General Public License Version 2.0 (or later); you may not use this work except in compliance with the License. You may obtain a copy of the License in the LICENSE file, or at:

https://www.gnu.org/licenses/old-licenses/gpl-2.0.txt

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Discourse logo and “Discourse Forum” ®, Civilized Discourse Construction Kit, Inc.

Accessibility

To guide our ongoing effort to build accessible software we follow the W3Cs Web Content Accessibility Guidelines (WCAG). If you'd like to report an accessibility issue that makes it difficult for you to use Discourse, email accessibility@discourse.org. For more information visit discourse.org/accessibility.

Dedication

Discourse is built with love, Internet style.