I’m sure a lot of this is going on … but this article is pretty poor.
First of all, they are hawking a VPN product. So it is in their interest to make the problem seem big.
Second, they argue VPN can shield against cookies. That’s to do with the browser, not the connection.
Third, their frequent use of the loaded “artificial intelligence” just bothers me … most of the algorithms they describe has nothing to do with AI/ML, but sounds like fairly simple, rules-based decisions. In fact, if I was interested is giving a discount to people who lived close to a competitor of mine, training an ML algorithm to do it sounds error-prone and poor.
We are recommending VPNs in general, but are not “hawking” or selling a specific one.
Second, we did not say a VPN hides against cookies. Cookies can easily be erased in the browser. This article is discussing browser fingerprints, which neither a VPN nor cookies deal with. Your reading comprehension is shockingly low.
“Simplified Privacy is here to help with a VPN solution that can obscure your browser fingerprint and enable you to step back and more clearly see discrimination.”
That sounded like hawking a specific product; I’m sure you could understand why.
You are arguing in the article that a VPN helps obscuring your browser fingerprint - and then say in your response to me that it can’t.
Don’t get me wrong - I support the aims of what you’re trying to achieve. My criticism is to address specific points in the article, not reject your noble aim.
Ah ok, that was meant for someone who wants to setup OpenVPN on a VPS that they can SSH into. But this person does not want to do the work. So the company can provide the service of setting up what you like on a VPS
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !privacyguides@lemmy.one
In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We’ve tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the “official” Privacy Guides community on Lemmy, which can be verified here. Other “Privacy Guides” communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
We prefer posting about open-source software whenever possible.
No soliciting engagement: Don’t ask for upvotes, follows, etc.
Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
Be civil, no violence, hate speech. Assume people here are posting in good faith.
Don’t repost topics which have already been covered here.
News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
No help vampires: This is not a tech support subreddit, don’t abuse our community’s willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
No misinformation: Extraordinary claims must be matched with evidence.
Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.
I’m sure a lot of this is going on … but this article is pretty poor.
First of all, they are hawking a VPN product. So it is in their interest to make the problem seem big.
Second, they argue VPN can shield against cookies. That’s to do with the browser, not the connection.
Third, their frequent use of the loaded “artificial intelligence” just bothers me … most of the algorithms they describe has nothing to do with AI/ML, but sounds like fairly simple, rules-based decisions. In fact, if I was interested is giving a discount to people who lived close to a competitor of mine, training an ML algorithm to do it sounds error-prone and poor.
We are recommending VPNs in general, but are not “hawking” or selling a specific one.
Second, we did not say a VPN hides against cookies. Cookies can easily be erased in the browser. This article is discussing browser fingerprints, which neither a VPN nor cookies deal with. Your reading comprehension is shockingly low.
Or maybe it wasn’t written well?
“Simplified Privacy is here to help with a VPN solution that can obscure your browser fingerprint and enable you to step back and more clearly see discrimination.”
That sounded like hawking a specific product; I’m sure you could understand why.
You are arguing in the article that a VPN helps obscuring your browser fingerprint - and then say in your response to me that it can’t.
Don’t get me wrong - I support the aims of what you’re trying to achieve. My criticism is to address specific points in the article, not reject your noble aim.
Ah ok, that was meant for someone who wants to setup OpenVPN on a VPS that they can SSH into. But this person does not want to do the work. So the company can provide the service of setting up what you like on a VPS