starred/ntfy

Fork 0

mirror of https://github.com/binwiederhier/ntfy.git synced 2026-05-09 08:26:00 +02:00

[GH-ISSUE #1491] Mi Push or JPush support #1052

New issue

Open

opened 2026-05-07 00:29:52 +02:00 by BreizhHardware · 5 comments

BreizhHardware commented

2026-05-07 00:29:52 +02:00

Owner

Originally created by @pdone on GitHub (Nov 20, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1491

When using ntfy.sh in China, due to the inability for China to use push services like GCM and FCM, there is a hope to integrate domestic push services into the ntfy Android app. This integration is aimed at enabling normal reception of messages even when the ntfy app is not running.

No.	Name	Type	Official Website	Remarks
1	Aurora Push (JPush)	Third-party	https://www.jiguang.cn/push	Largest existing access volume, unified encapsulation of multiple manufacturer channels
2	Getui	Third-party	https://www.getui.com	Same source as top apps, supports SMS complement
3	Umeng+ U-Push	Third-party	https://push.umeng.com	Alibaba ecosystem, one-click integration with Umeng analytics
4	Tencent XG Push	Third-party	https://cloud.tencent.com/product/xg	Tencent internal tech, high adoption in gaming/social apps
5	Baidu Cloud Push	Third-party	https://cloud.baidu.com/product/push.html	Free basic push permanently, integrated with Baidu analytics
6	Alibaba Cloud Mobile Push	Third-party	https://www.aliyun.com/product/cps	Integrates six major manufacturer channels, overseas FCM linkage
7	Mi Push	Manufacturer	https://dev.mi.com/console/appservice/push.html	MIUI system-level, marketing messages limited to 5/day
8	Huawei HMS Push	Manufacturer	https://developer.huawei.com/consumer/cn/hms/huawei-pushkit	HarmonyOS/EMUI system-level, overseas AppGallery linkage
9	OPPO HeyTap Push	Manufacturer	https://open.oppomobile.com/wiki/doc#id=10104	ColorOS system-level, strict marketing controls
10	vivo Push	Manufacturer	https://dev.vivo.com.cn/documentCenter/doc/180	Funtouch/OriginOS system-level, suitable for vivo/iQOO devices

在中国使用ntfy.sh时，由于中国无法使用GCM、FCM等推送服务，希望可以在ntfy Android APP中集成中国国内推送服务，以实现在ntfy app未启动的时候，正常接收消息。

序号	名称	类型	官网链接	备注
1	极光推送（JPush）	第三方	https://www.jiguang.cn/push	存量接入量最大，统一封装多厂商通道
2	个推（Getui）	第三方	https://www.getui.com	与头部 App 同源，支持短信补量
3	友盟 + U-Push	第三方	https://push.umeng.com	阿里系，与 Umeng 统计一键打通
4	腾讯云信鸽（XG Push）	第三方	https://cloud.tencent.com/product/xg	腾讯内部技术，游戏/社交类采用率高
5	百度云推送	第三方	https://cloud.baidu.com/product/push.html	永久免费基础推送，与百度统计打通
6	阿里云移动推送	第三方	https://www.aliyun.com/product/cps	整合六大厂商通道，出海可联动 FCM
7	小米推送（Mi Push）	厂商	https://dev.mi.com/console/appservice/push.html	MIUI 系统级，营销消息限 5 条/日
8	华为推送（HMS Push）	厂商	https://developer.huawei.com/consumer/cn/hms/huawei-pushkit	鸿蒙+EMUI 系统级，海外可联动 AppGallery
9	OPPO 推送（HeyTap Push）	厂商	https://open.oppomobile.com/wiki/doc#id=10104	ColorOS 系统级，营销管控严格
10	vivo 推送（vivo Push）	厂商	https://dev.vivo.com.cn/documentCenter/doc/180	Funtouch/OriginOS 系统级，适合 vivo/iQOO

Originally created by @pdone on GitHub (Nov 20, 2025). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1491 When using ntfy.sh in China, due to the inability for China to use push services like GCM and FCM, there is a hope to integrate domestic push services into the ntfy Android app. This integration is aimed at enabling normal reception of messages even when the ntfy app is not running. | No. | Name | Type | Official Website | Remarks | |-----|------------------------|----------------|---------------------------------------------------------------|-------------------------------------------------------------------------| | 1 | Aurora Push (JPush) | Third-party | <https://www.jiguang.cn/push> | Largest existing access volume, unified encapsulation of multiple manufacturer channels | | 2 | Getui | Third-party | <https://www.getui.com> | Same source as top apps, supports SMS complement | | 3 | Umeng+ U-Push | Third-party | <https://push.umeng.com> | Alibaba ecosystem, one-click integration with Umeng analytics | | 4 | Tencent XG Push | Third-party | <https://cloud.tencent.com/product/xg> | Tencent internal tech, high adoption in gaming/social apps | | 5 | Baidu Cloud Push | Third-party | <https://cloud.baidu.com/product/push.html> | Free basic push permanently, integrated with Baidu analytics | | 6 | Alibaba Cloud Mobile Push | Third-party | <https://www.aliyun.com/product/cps> | Integrates six major manufacturer channels, overseas FCM linkage | | 7 | Mi Push | Manufacturer | <https://dev.mi.com/console/appservice/push.html> | MIUI system-level, marketing messages limited to 5/day | | 8 | Huawei HMS Push | Manufacturer | <https://developer.huawei.com/consumer/cn/hms/huawei-pushkit> | HarmonyOS/EMUI system-level, overseas AppGallery linkage | | 9 | OPPO HeyTap Push | Manufacturer | <https://open.oppomobile.com/wiki/doc#id=10104> | ColorOS system-level, strict marketing controls | | 10 | vivo Push | Manufacturer | <https://dev.vivo.com.cn/documentCenter/doc/180> | Funtouch/OriginOS system-level, suitable for vivo/iQOO devices | --- 在中国使用ntfy.sh时，由于中国无法使用GCM、FCM等推送服务，希望可以在ntfy Android APP中集成中国国内推送服务，以实现在ntfy app未启动的时候，正常接收消息。 | 序号 | 名称 | 类型 | 官网链接 | 备注 | | -- | -------------------- | --- | ------------------------------------------------------------- | ---------------------------------- | | 1 | 极光推送（JPush） | 第三方 | <https://www.jiguang.cn/push> | 存量接入量最大，统一封装多厂商通道 | | 2 | 个推（Getui） | 第三方 | <https://www.getui.com> | 与头部 App 同源，支持短信补量 | | 3 | 友盟 + U-Push | 第三方 | <https://push.umeng.com> | 阿里系，与 Umeng 统计一键打通 | | 4 | 腾讯云信鸽（XG Push） | 第三方 | <https://cloud.tencent.com/product/xg> | 腾讯内部技术，游戏/社交类采用率高 | | 5 | 百度云推送 | 第三方 | <https://cloud.baidu.com/product/push.html> | 永久免费基础推送，与百度统计打通 | | 6 | 阿里云移动推送 | 第三方 | <https://www.aliyun.com/product/cps> | 整合六大厂商通道，出海可联动 FCM | | 7 | 小米推送（Mi Push） | 厂商 | <https://dev.mi.com/console/appservice/push.html> | MIUI 系统级，营销消息限 5 条/日 | | 8 | 华为推送（HMS Push） | 厂商 | <https://developer.huawei.com/consumer/cn/hms/huawei-pushkit> | 鸿蒙+EMUI 系统级，海外可联动 AppGallery | | 9 | OPPO 推送（HeyTap Push） | 厂商 | <https://open.oppomobile.com/wiki/doc#id=10104> | ColorOS 系统级，营销管控严格 | | 10 | vivo 推送（vivo Push） | 厂商 | <https://dev.vivo.com.cn/documentCenter/doc/180> | Funtouch/OriginOS 系统级，适合 vivo/iQOO |

BreizhHardware added the

enhancement

android-app

labels

2026-05-07 00:29:52 +02:00

BreizhHardware commented

2026-05-07 00:29:53 +02:00

Author

Owner

@binwiederhier commented on GitHub (Jan 18, 2026):

I don't know anything about any of these. It's very unlikely that I'll ever proactively implement this myself, but unless it brings a ton of dependencies, I'd be willing to merge a PR.

@binwiederhier commented on GitHub (Jan 18, 2026): I don't know anything about any of these. It's very unlikely that I'll ever proactively implement this myself, but unless it brings a ton of dependencies, I'd be willing to merge a PR.

BreizhHardware commented

2026-05-07 00:29:53 +02:00

Author

Owner

@kkkgo commented on GitHub (Mar 21, 2026):

In China, all message push platforms must connect to the censorship system. Apps are required to apply for real-name filing (real-name registration) before they can access these services. There are also strict limits on push frequency and prohibited sensitive words. Developers must take legal responsibility for the content sent through push notifications. For open-source applications, these requirements are practically impossible to fulfill.

@kkkgo commented on GitHub (Mar 21, 2026): In China, all message push platforms must connect to the censorship system. Apps are required to apply for real-name filing (real-name registration) before they can access these services. There are also strict limits on push frequency and prohibited sensitive words. Developers must take legal responsibility for the content sent through push notifications. For open-source applications, these requirements are practically impossible to fulfill.

BreizhHardware commented

2026-05-07 00:29:53 +02:00

Author

Owner

@pdone commented on GitHub (Mar 21, 2026):

In China, all message push platforms must connect to the censorship system. Apps are required to apply for real-name filing (real-name registration) before they can access these services. There are also strict limits on push frequency and prohibited sensitive words. Developers must take legal responsibility for the content sent through push notifications. For open-source applications, these requirements are practically impossible to fulfill.

I know, there is no way.

@pdone commented on GitHub (Mar 21, 2026): > In China, all message push platforms must connect to the censorship system. Apps are required to apply for real-name filing (real-name registration) before they can access these services. There are also strict limits on push frequency and prohibited sensitive words. Developers must take legal responsibility for the content sent through push notifications. For open-source applications, these requirements are practically impossible to fulfill. I know, there is no way.

BreizhHardware commented

2026-05-07 00:29:54 +02:00

Author

Owner

@LucidaLu commented on GitHub (Mar 29, 2026):

I understand that the officially distributed APK cannot include out-of-the-box support for Chinese push platforms due to regulatory compliance and the liability it would place on the maintainers.

However, I propose implementing these push platforms as a build-time configuration. Under this approach, users who wish to use a specific service (e.g., MiPush) must register for their own credentials on the respective developer platform. The required push dependencies will only be compiled into the final APK if these credentials are provided during the build process.

I believe this is a highly feasible workaround and hope the maintainers will consider it an acceptable solution. I think I might be interested in implementing this.

@LucidaLu commented on GitHub (Mar 29, 2026): I understand that the officially distributed APK cannot include out-of-the-box support for Chinese push platforms due to regulatory compliance and the liability it would place on the maintainers. However, I propose implementing these push platforms as a build-time configuration. Under this approach, users who wish to use a specific service (e.g., MiPush) must register for their own credentials on the respective developer platform. The required push dependencies will only be compiled into the final APK if these credentials are provided during the build process. I believe this is a highly feasible workaround and hope the maintainers will consider it an acceptable solution. I think I might be interested in implementing this.

BreizhHardware commented

2026-05-07 00:29:54 +02:00

Author

Owner

@binwiederhier commented on GitHub (Mar 29, 2026):

That's a great idea. I'm happy to accept another build flavor for this, especially if you're doing the work.

@binwiederhier commented on GitHub (Mar 29, 2026): That's a great idea. I'm happy to accept another build flavor for this, especially if you're doing the work.

BreizhHardware referenced this issue

2026-05-07 01:02:24 +02:00

[PR #1052] Reworked adding non-root user to docker images. #1502