ポリニアンはやたらとデフォルメのきいた体型が良いよねー
@BoF@mstdn.fr also keeping streaming connection wastes server's resource, I can't provide "listeners for any instances " on my app server. then I made system that allows the user himself can provide server's listener part.
if the user already build his listener server, he already knows the settings for ST.
https://github.com/tateisu/mastodon-streaming-listener
currently mastodon has push subscription API, the listener is deprecated feature.
@BoF@mstdn.fr Old mastodon has no push subscription API, then the app server have to connect and listen to mastodon's notification stream endpoint with the user's access token. ( like as tootdon still does it.)
of course sending access token is very dangerous, it is off by default in the setting you pointed.
@BoF@mstdn.fr ST's custom notification listener is used for between app server and mastodon server, not for between app server and app client.
also CNL is deprecated because current mastodon has push subscription API, but CNL is still works for old mastodon instances.
@BoF@mstdn.fr SSE is just streaming protocol, it can't works with deep sleeped devices. I think ST should not disallow deep sleep the devices by running services that continually listen stream. (if it is allowed, the app can connect to mastodon's stream endpoint, no need to use SSE.) FCM can wake up deep sleeped device, SSE is not alternative choice for this purpose.