Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Crimea sanctions

  • 3 Mbohovái
  • 2 oguereko ko apañuãi
  • 2 Hecha
  • Mbohovái ipaháva dmi3n1

more options

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?

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?

Opaite Mbohovái (3)

more options

Hi, I've sent your request to https://bugzilla.mozilla.org/show_bug.cgi?id=1646012 . We'll see what Mozilla say about it.

more options

They want you to provide error logs to analyze.

See How do I submit a bug for Firefox Sync?

more options

here is last sync error log as u can see some servers respond 403, im sure because of sanctions