3 ms·
if you use any kind of 3rd party analytics service you need to communicate with outside api basically every (analytically relevant) action of your user... so it
by scotu 10y ago
if you use any kind of 3rd party analytics service you need to communicate with outside api basically every (analytically relevant) action of your user... so it's pretty standard on web and native apps alike
- palerdot 10y agoIf that is the case, why all the other the other repo's star operations is not communicated to google or other analytics platform? My point was, I was blocked from starring only for this repo and not all the other repos. It was not about how analytics works in general for every user action.
- scotu 10y agoA sibilling comment was explaining it: basically your ublock (that I use too) is regularly blocking the request to google analytics everywhere, github code doesn't fail in that case, but since the repo contained the "googleanalytics" substring ublock was blocking the request (because it checks for words in the urls that get requested) to the github server thus making the starring function fail. Other repo do not have "suspicious" strings in their url, so they pass through ublock, while the real google analytics call is blocked and github does not fail. You can check the network tab in the developer tools in chrome around github and see that calls to GA gets blocked and calls to github pass while on that specific page also the call to github fails