Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove browser-update.org from privacy list or reclassify as annoyance #7084

Closed
josselex opened this issue Mar 10, 2020 · 14 comments
Closed

Comments

@josselex
Copy link

Browser-update.org is not tracking users in any way. As such I think it should be removed from the privavy list.

Browser-update.org is an open source project to inform about insecure and unsupported old browsers.
No identifying cookie is set, see
https://github.com/browser-update/browser-update/wiki/Privacy

The only cookie set always has the value browserupdateorg=pause and is justed used to show a message once per visitor in order not to annoy visitors.

It may be filed unter annoyances, but I think we are trying to be less annoying than all custom solutions that websites implement, and think that it would be better if it is not blocked.

Some discussion on what we do is already here:
#5795 (comment)

@uBlock-user
Copy link
Contributor

This was already discussed once via internal discussion, so whats changed after all these months ?

@okiehsch
Copy link
Contributor

Some discussion on what we do is already here:
#5795

browser-update-org has since been added to EasyPrivacy.
image
easylist/easylist@2a028cb

@uBlock-user
Copy link
Contributor

@okiehsch In that case, we should remove it from uBO-Privacy.

@okiehsch
Copy link
Contributor

Yes, it has become redundant.

@uBlock-user
Copy link
Contributor

41d7811

@josselex
Copy link
Author

This was already discussed once via internal discussion, so whats changed after all these months ?

I just wanted to say that we do not track in anyway and respect privacy. That's why it should not be filed under privacy. I guess this is useful information.

@okiehsch
Copy link
Contributor

okiehsch commented Mar 10, 2020

browser-update.org is also blocked in Adguards Tracking Protection filter

@uBlock-user
Copy link
Contributor

I just wanted to say that we do not track in anyway and respect privacy.

You collect some data no matter how insiginificant you think it may be, and obviously other filter lists disagree with you too.

@josselex
Copy link
Author

josselex commented Mar 10, 2020

But we do not track! For every 1000th visitor we record which browser was used. That's all (see the code). And for me it seems the lists copy from each other.

@okiehsch
Copy link
Contributor

and for me it seems the lists copy from each other.

Well, we did not copy it, we added it because at the time EasyPrivacy did not block it.
@ryanbr do you want to chime in?

@ryanbr
Copy link
Contributor

ryanbr commented Mar 10, 2020

A third-party script checking user agents and setting cookies, that is tracking. It's staying

@josselex
Copy link
Author

josselex commented Mar 11, 2020

But we are not tracking.

  1. The cookie is the same for all users. It has no specific information. it just says: browserupdateorg=pause.
    So we can not identify users in any way.
  2. The cookie only lasts 24 hours by default. It is only set to the current domain. We cannot track in any way across domains. It is just used to show a message only once per user and 24hours.
  3. We do not record data except for a random sample of the browser used for every 1000th user. This can not be used in any way to track anybody. You can check the script to verify this.

Please, if you say it's tracking, say why or what your definition is.

@krystian3w
Copy link
Contributor

krystian3w commented Mar 12, 2020

https://updatemybrowser.org/widget

<script>
(function(u) {
    var s = document.createElement('script'); s.async = true; s.src = u;
    var b = document.getElementsByTagName('script')[0]; b.parentNode.insertBefore(s, b);
})('//updatemybrowser.org/umb.js');
</script>

no blocked:

+10
axa.mx
3
script
https://updatemybrowser.org/umb.js
+0
https://axa.mx/personas/inicio

@Kristinita
Copy link

Type: Question

But we are not tracking.

  1. The cookie is the same for all users. It has no specific information. it just says: browserupdateorg=pause.

  2. So we can not identify users in any way.

  3. The cookie only lasts 24 hours by default. It is only set to the current domain. We cannot track in any way across domains. It is just used to show a message only once per user and 24hours.

We do not record data except for a random sample of the browser used for every 1000th user. This can not be used in any way to track anybody. You can check the script to verify this.

Please, if you say it's tracking, say why or what your definition is.

@josselex, could you give arguments why it’s so important that you left it, despite the fact that Browser Update is included in the ad blockers blocklists? 32.8% of internet users worldwide use ad blocking tools at least sometimes, many of them may not see notifications from Browser Update. Also, website developers may refuse to use Browser Update because ad blockers block it. I would do what the blocklist developers require, so that Browser Update is removed from the blocklists. It seems to me that the benefit of removing Browser Update from blocklists far outweighs the benefit of retaining features that are unwanted, in the opinion of blocklist developers.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants