关于中国大陆安卓推送生态问题 || about the ecological issue of Android push in mainland China

因为众所周知的原因目前国内安卓推送生态复杂

难点:

各个厂商都有自己的一套推送渠道，必须各大厂商都适配
限额严重，普通的推送机制每天只能推送1到5条消息不等
如要解除限额，必须将应用上架到对应平台的市场，上架需要审核、并提供隐私声明、使用权限说明、软件著作权等内容，对于开源软件特别是自部署用户来说非常不友好。后面还有没有什么坑不知道

目前能想到方法有:

通过公司的身份统一注册一个应用，然后后续通过代理人机制帮忙推送
从即时消息推送修改为每日汇总（机制类似邮箱每日提醒）
通过第三方的接入了各大厂商的应用做转发（目前没有看到特别好用的解决方案）

如果有什么想法欢迎留言

Because of well-known reasons, the current domestic Android push ecology is complicated

difficulty:

Each manufacturer has its own set of push channels, which must be adapted by all major manufacturers
The limit is serious, the ordinary push mechanism can only push 1 to 5 messages per day
To remove the quota, the application must be put on the market of the corresponding platform, which needs to be reviewed and provided with privacy statement, usage permission description, software copyright and other content, which is very unfriendly to open source software, especially self-deployment users. I don't know if there are any holes in the back

Currently conceivable methods are:

Unified registration of an application through the company's identity, and then help push it through the agent mechanism
Changed from instant message push to daily summary (the mechanism is similar to the daily reminder of mailbox)
Through the third-party access to the applications of major manufacturers for forwarding (I have not seen a particularly easy-to-use solution so far)

If you have any ideas, please leave a message

其实推送这一块，想要真正像个正常的app推送是不太可能实现的了，很多做通知类app的尴尬之处。

In fact, it is impossible to push this piece like a normal app. There are many embarrassing places for notification apps.

@moonrailgun 您好，我有在关注Rocket.chat和您的项目，

在这里向您和同类应用提出一个中国Android应用推送解决方案建议。我参考了其他安卓应用的推送解决方案，这个应用名称是 APKPure 。

猜想和建议：

APKPure 以后台始终保持运行的方式，创建了一个顶层显示（类似于悬浮窗），利用这个方法实现了在极端环境下的消息通知。我希望Rocket.chat的安卓客户端和同类应用，可以参考这个方法，来满足这个非常必要且急切的普遍需求。希望可以作为可选功能被添加到应用中。

Rocket.chat的相同issues链接： https://github.com/RocketChat/Rocket.Chat.ReactNative/issues/5342

@moonrailgun Hello, I am following Rocket.chat and your project,

Here we propose a Chinese Android app push solution to you and similar apps. I referred to the push solutions of other Android applications, The app name is APKPure.

Guesses and suggestions:

APKPure keeps running in the background, Creates a top-level display (similar to a floating window), This method is used to implement message notification in extreme environments. I hope Rocket.chat’s Android client and similar applications can refer to this method. to meet this very necessary and urgent universal need. Hopefully this can be added to the app as an optional feature.

Same issues link for Rocket.chat: https://github.com/RocketChat/Rocket.Chat.ReactNative/issues/5342

@XJY00

感谢你的留言，你的方案我们也考虑过，其问题在于虽然可能可以解决部分手机的问题，让推送能够触达用户，但是面临的问题在于对于用户本身是不友好的，也是不环保的。另一方面来说，这种方案是被各大厂商所不允许的，事实上各个厂商对于这种形式的应用处理方式是不同的，有的厂商会严一点有的厂商会比较松。随着android规范越来越完备以及厂商对应用的监管越来越严，这种像是病毒一样的非正常方式是会逐渐消失的，而我们作为开源项目来说也很难做到和厂商进行长久的对抗（类似的有以前的安卓的1px保活之类的）当然非常感谢你的留言

@XJY00

Thank you for your message. We have also considered your solution. The problem is that although it may be able to solve the problems of some mobile phones and allow push notifications to reach users, the problem is that it is not friendly to users themselves and is not environmentally friendly. On the other hand, this solution is not allowed by major manufacturers. In fact, each manufacturer has different ways of handling this form of application. Some manufacturers will be more strict and some will be more lenient. As Android specifications become more and more complete and manufacturers supervise applications more and more strictly, this abnormal method like viruses will gradually disappear, and as an open source project, it is difficult for us to negotiate with manufacturers. Long-term confrontation (similar to the previous Android's 1px keep-alive) Of course thank you very much for your message

我有些疑问哈，应用图标上的小红点，和消息推送接口是一起的吗？对于我个人来说，只要知道有即时消息或者小红点就行了，完全可以放弃消息内容预览。

简单分析一下，根据g0v目前的规定，要求消息内容需要进行审查，选择正规推送方式：开源项目的消息内容不可控，必然会选择接受审查或者放弃通知的预览信息。选择悬浮窗方式：同样因为劣币驱逐良币，可能导致平台对悬浮窗的更多限制（这是您提到的可能性）对于悬浮窗方式我的看法是，如果要限制就等于割肉，因为正常的录屏工具要用到。（小声bb:只是个可选功能哪里不好了(╯°□°）╯︵ ┻━┻）

g0v的app备案和审查，可能会迫使开源项目进行最后的抉择，y割披羊皮？还是钻狗洞？最坏最节省成本的结果是直接放弃支持中国地区，因为开源app最后可能不准被接入网络。

Bad idea&End：

统统钻狗洞进行最后的狂欢，最后因未备案不准接入网络，开源app已死

i kill myself？：

老老实实放弃内容预览，y割自己绕过审查。堂堂正正审查后接入平台，y割用户开启特色开源商业化新生

some idea：

webPush，利用第三方浏览器对于网站服务的推送通知，搭建web应用依靠浏览器app推送？ https://zhuanlan.zhihu.com/p/269036804
实时修改桌面图标，模拟小红点？
邮箱服务器推送（比如通过outlook邮箱smtp发送新消息通知）我原本准备自建邮箱服务器却发现租用的服务器运营商不支持

一些可能有关推送的github项目： PushDeer 有关无法推送的反馈与回复 Server酱 https://sct.ftqq.com 其中提到了他们计划开发快应用http://www.so-quick.cn

《互联网弹窗信息推送服务管理规定》 **部关于开展移动互联网应用程序备案工作的通知推必安

最后的请求：

如果悬浮窗确实不合适，希望SMTP服务支持这一扩展选项：在线新消息邮件推送（Rocket.chat只支持离线消息的邮箱通知，但通常我在电脑上会保持登录就无法接到通知了）

I have some questions, Is the little red dot on the application icon the same as the message push interface? For me personally, as long as I know there is an instant message or a little red dot, I can completely give up previewing the message content.

A brief analysis shows that according to g0v’s current regulations, message content needs to be reviewed. Choose a formal push method: The message content of open source projects is uncontrollable, and you will inevitably choose to accept review or abandon the preview information of the notification. Choose the floating window method: Also because bad coins drive out good coins, it may lead to more restrictions on the floating window on the platform (this is the possibility you mentioned) My opinion on the floating window method is that if you want to restrict it, it is equivalent to cutting off the meat, because normal screen recording tools need to be used. (whisper bb: What’s wrong with it being just an optional feature (╯°□°)╯︵ ┻━┻)

g0v’s app registration and review may force open source projects to make final decisions, and cut them off in sheep’s clothing? Or drill into a dog hole? The worst and most cost-effective result is to simply give up support for China, because open source apps may not be allowed to be connected to the network in the end.

Bad idea&End:

They all went into a dog hole to have the last carnival, and in the end they were not allowed to access the Internet because they were not registered. The open source app is dead.

i kill myself? :

Honestly give up content previews and cut yourself to bypass censorship. Access to the platform after a dignified review, y-cut users open up a new life of characteristic open source commercialization

some ideas:

webPush, using third-party browsers to push notifications for website services, building web applications that rely on browser app push? https://zhuanlan.zhihu.com/p/269036804
Modify desktop icons in real time and simulate little red dots?
Email server push (such as sending new message notifications through Outlook email SMTP) I originally planned to build my own email server but found that the server operator I rented did not support it.

Some github projects that may be relevant for pushing: PushDeer Feedback and replies about the inability to push Server sauce https://sct.ftqq.com It mentioned that they plan to develop quick applications http://www.so-quick.cn

"Internet pop-up information push service management regulations" Ministry of **Notice on Carrying out the Registration of Mobile Internet Applications Tuibian

Last request:

If the floating window is really not suitable, I hope the SMTP service supports this extended option: online new message email push (Rocket.chat only supports email notifications for offline messages, but usually I stay logged in on my computer and cannot receive notifications)

@XJY00 感谢你的回复。你的消息每一行我都认真看了，对于你的疑问我做出了如下的回复:

应用图标上的小红点，和消息推送接口是一起的吗？

是的

选择正规推送方式：开源项目的消息内容不可控，必然会选择接受审查或者放弃通知的预览信息。

营销消息有审查。IM没有但是有门槛。

webPush

需要google支持。如果国内用户可以接受谷歌那就统一同FCM推送就不存在问题了。

实时修改桌面图标，模拟小红点？

进程被杀死了，没有办法操作了

一些可能有关推送的github项目：

事实上已经接入wxpusher. 具体可以看官方文档: https://tailchat.msgbyte.com/zh-Hans/docs/advanced-usage/plugins/com.msgbyte.wxpusher

如果悬浮窗确实不合适，希望SMTP服务支持这一扩展选项：在线新消息邮件推送

邮件发信作为IM替代是一种很低效的方案，每一条都发很容易被视为骚扰邮件被拒信。合并消息控制发送数量在时效性上有一些缺失，而且国内用邮箱的用户比较少。

不过如果是电脑网页用户/桌面端用户的话保持标签页开启的话这方面问题就比较少，因为这些方案不存在手机考虑电量因素导致的杀进程行为，应用可以长期活跃

@XJY00 Thanks for your reply. I have read every line of your message carefully, and I have responded to your questions as follows:

Is the little red dot on the application icon the same as the message push interface?

Yes

Choose a formal push method: The message content of open source projects is uncontrollable, and you will inevitably choose to accept review or give up the preview information of the notification.

Marketing messages are censored. IM doesn't have it but there are thresholds.

webPush

Requires Google support. If domestic users can accept Google, then unified push with FCM will not be a problem.

Modify desktop icons in real time and simulate little red dots?

The process has been killed and there is no way to operate it.

Some github projects that may be related to push:

In fact, wxpusher has been connected. For details, please see the official documentation: https://tailchat.msgbyte.com/zh-Hans/docs/advanced-usage/plugins/com.msgbyte.wxpusher

If the floating window is really not suitable, I hope the SMTP service supports this extended option: online new message email push

Sending emails as an alternative to IM is a very inefficient solution. Sending every email can easily be regarded as a harassing email and be rejected. There are some shortcomings in the timeliness of combining the number of messages to be sent, and there are relatively few users in China who use email.

However, if you are a computer web user/desktop user, if you keep the tab open, there will be less problems in this regard, because these solutions do not have the process killing behavior caused by the mobile phone considering the power factor, and the application can be active for a long time

明白了，感谢解答

Got it, thanks for the answer

msgbyte / tailchat