Include IPFS Companion and Google Translate views in main Countly dashboard

[terichadbourne]

Right now, the main Countly dashboard only captures visits from the domain proto.school, and other domains get logged in the test dashboard. The original intention of this was to ensure that developers using localhost, Fleek or Netlify previews, etc., could play around without affecting the real data. However, we're now finding activity in the test dashboard that doesn't appear to be from devs, suggesting that we should add at least two more domains to the main dashboard:

• the domain used by folks visiting via IPFS Companion (need to confirm this will always be consistent)
• the domain used by folks visiting with Google Translate turned on (discovered this use case because we're seeing /translate_c in page views)

It would also be useful to start logging domains through which people are visiting so that we can track IPFS Companion and Google Translate usage moving forward.

[terichadbourne]

@lidel As our resident IPFS Companion and localization expert, you might be able to help us confirm...

• Will the domain used by folks visiting ProtoSchool via IPFS Companion always be consistent (ie no CID as part of it that's always changing, etc.)
• Do you know of any translation services other than Google Translate that would use a different domain to serve up our content?

[lidel]

Regarding the domain of IPFS Companion users, those usually run local gateway on a port that can be changed. I would look for these patterns:

• http://*.ipfs.localhost:*/
  • Someone loaded a static snapshot of the website from a local gateway (CID before .ipfs. was changing). (This happened for a while until Fleek removed X-Ipfs-Path header)
• http://proto.school.ipns.localhost:*/
  • Someone loaded the website from a local gateway at the time when DNSLink was enabled (I think this happened for a while, and is something we want to support in the future)

As for translation websites, most likely all of them do this, but targeting the biggest players should cover the most of uses:

• Bing delegates translation to URLs like https://www.translatetheweb.com/?ref=TVert&from=&to=zh-Hans&a=https%3A%2F%2Fproto.school%2F
• Yandex is even more bizzare:
  • https://translate.yandex.com/translate embedds iframe which is loaded from URL that looks like this: https://z5h64q92x9.net/proxy_u/en-zh.en/https/proto.school/
• Baidu
  • https://fanyi.baidu.com well.. I tried but failed ¯_(ツ)_/¯
  • unsure if it supports full-page translation, but worth looking into due to the size of our community in Asia (perhaps ask folks what is the most popular English-to-Chinese-Simplified translator they use)