Crimea sanctions
esr 68.9.0 Since May 26, synchronization of cloud tabs and plugins has stopped in Crimea region.
It was determined that synchronization works fine through vpn, which means that the problem is in sanctions. I think mozilla sync using some hosting that, following sanctions, bans Crimean ip-addresses.
But there is a very important point about sanctions, they apply only to the services from which you can make a profit. For example, google search engine works, but AdSense is not.
So maybe open-source browser can be able to configure the synchronization service, which does not receive profit, to work normally with users from the Crimea?
所有回复 (3)
Hi, I've sent your request to https://bugzilla.mozilla.org/show_bug.cgi?id=1646012 . We'll see what Mozilla say about it.
They want you to provide error logs to analyze.
here is last sync error log as u can see some servers respond 403, im sure because of sanctions