UnifiedPush uses third-party gateway server

[WGH-]

I assume that UnifiedPush implemention was taken from MercuryGram mostly as is, including the use of third-party simple push gateway hosted on https://p2p.belloworld.it/:

TelegramAndroid/TMessagesProj/src/main/java/org/telegram/messenger/UnifiedPushReceiver.java

Lines 27 to 44 in abe07f4

	@Override
	public void onNewEndpoint(Context context, String endpoint, String instance){
	Utilities.globalQueue.postRunnable(() -> {
	SharedConfig.pushStringGetTimeEnd = SystemClock.elapsedRealtime();
	String savedDistributor = UnifiedPush.getSavedDistributor(context);
	if (savedDistributor.equals("io.heckel.ntfy")) {
	PushListenerController.sendRegistrationToServer(PushListenerController.PUSH_TYPE_SIMPLE, endpoint);
	} else {
	try {
	PushListenerController.sendRegistrationToServer(PushListenerController.PUSH_TYPE_SIMPLE, "https://p2p.belloworld.it/" + URLEncoder.encode(endpoint, "UTF-8"));
	} catch (UnsupportedEncodingException e) {
	FileLog.e(e);
	}
	}
	});
	}

Telegram is supposed to support Web Push directly, without third-party gateway. MercuryGram however claims that Web Push is unreliable. Perhaps that's true, but relying on random third-party gateway server isn't ok either.

[23rd]

I'm not a user of UnifiedPush that was recently integrated.
I'm pretty happy with permanent pinned notification.
So feel free to open a PR.

[prurigro]

It does bypass the gateway if you're using ntfy on that note, though I've been finding push for telegram kind of unreliable lately. I wonder if web push would be more reliable than that?

[nidamanx]

I believe it should be better if UnifiedPush server is not hardcoded because the service could be self-hosted
In that way, a user could choose between the MercuryGram one or it's own one
This, could be a nice way
And, perhaps, also a way to choose to use permanent pinned notifications as @23rd wrote

[prurigro]

The default is actually to use a permanent pinned notification, you simply don't disable "background connection"