| 24 May 2025 |
 emily | does Zulip support SSO integrations? could we allow anyone with a Discourse or GitHub account to join without registration? | 10:22:11 |
| emily | yes for GitHub: https://zulip.readthedocs.io/en/latest/production/authentication-methods.html | 10:22:43 |
| emily | and it does SAML/OIDC, so I assume we could reuse Discourse accounts, but that might not matter as much (if you are okay making a Discourse account you are more likely to be okay making one for chat) | 10:23:21 |
| emily | I don't know. I really think we should consider it. if we're going to spend a lot of time setting up a more permanent Matrix entryway, mightn't it be a good idea to try spinning up a demo Zulip and asking the SC what they think? | 10:24:03 |
| emily | (or Mattermost, or whatever.) | 10:24:16 |
 K900 | The big downside for Zulip is no mobile push on selfhosted | 10:24:43 |
| emily |
Google’s and Apple’s security model for mobile push notifications does not allow self-hosted Zulip servers to directly send mobile notifications to the Zulip mobile apps. The Zulip Mobile Push Notification Service solves this problem by forwarding mobile push notifications generated by your server to the Zulip mobile apps.
| 10:25:13 |
| emily | https://zulip.readthedocs.io/en/latest/production/mobile-push-notifications.html | 10:25:16 |
| emily | I think it's okay to rely on a central server for push. | 10:25:21 |
| emily | Matrix clients already do. | 10:25:24 |
| emily | it looks like we can still self-host Zulip. | 10:25:32 |
| emily | maybe that functionality didn't exist previously? | 10:25:47 |
| K900 |
To access the Mobile Push Notification Service, organizations with more than 10 users must upgrade to a paid plan
| 10:26:29 |
| emily | is that going to be an issue? we pay for a lot of stuff | 10:26:52 |
| emily | hmm it's pretty pricey :) | 10:27:05 |
| emily | oh | 10:27:20 |
| emily |
Free Standard plan eligibility
Open-source projects
| 10:27:24 |
| emily | no issue then? | 10:27:34 |
