| 24 May 2025 |
 emily | there's paid self-hosted too | 10:28:12 |
| emily | still:
Community plan eligibility
Open-source projects
| 10:28:18 |
 uep | yea | 10:28:18 |
 Cat | as in Policy lists are illegal due to platform rules on discord as far as i remember hearing. | 10:28:26 |
| Cat | or something stupid like that., | 10:28:32 |
| emily | so it seems fine to me? | 10:28:35 |
| emily | most likely we'd get it for free | 10:28:38 |
| emily | even if it's not strictly part of the plan there are Zulip people who are Nixpkgs contributors too :P | 10:28:49 |
| emily | (it's not clear what the Community plan includes) | 10:29:10 |
| emily |
Organizations that have up to 10 users, or do not require mobile push notifications, will likely find the Free plan to be the most convenient option. Larger organizations are encouraged to apply for the Community plan, which includes unlimited push notifications and support for many Zulip features.
| 10:29:15 |
| emily | okay yeah it includes push notifications | 10:29:20 |
| uep | yeah it's not in the list i'm looking at | 10:29:23 |
| emily | https://zulip.com/help/self-hosted-billing#free-community-plan | 10:29:28 |
| emily | seems pretty clear we can self-host the infra and get push notifs for free | 10:29:37 |
| emily | so all good on that front IMO | 10:29:59 |
| emily | okay yeah literally the only thing the paid self-hosted tiers give is access to push notifs and email/chat support | 10:30:53 |
| emily | and the base paid tier is infinite push notifs which is free for FOSS | 10:31:08 |
| emily | (makes sense, they're just charging for access to their server and support resources) | 10:31:21 |
| emily | K900: does that match your understanding or? | 10:32:10 |
| emily | I agree that push notifs matter | 10:32:16 |
 K900 | I am not entirely sure tbh | 10:32:35 |
| K900 | I have reservations about having to selfhost comms in general | 10:32:53 |
| K900 | Or relying on third party sponsorships for this | 10:33:05 |
| emily | I think "if Zulip decide to take away our push notifications we have to figure something out" is an acceptable risk. | 10:33:28 |
| emily | Element could also take away push notifs. | 10:33:32 |
| emily | both Zulip and Element could stop publishing server source code | 10:33:42 |
| emily | etc. | 10:33:44 |
| emily | I don't see "there's clearly-delineated free access to a push notification server for our project, everything else is free and the server code is FOSS" as a meaningful increase in risk compared to our current situation | 10:34:24 |
| emily | any push notification support is going to rely on the largesse of an organization that will deal with Apple/Google unless we want to publish our own apps | 10:34:44 |
| emily | so if push notifications are a requirement, either we start getting on the App Store or we accept that we rely on Element or Zulip or whatever to provide users a pipe for notifications. | 10:35:14 |
