I think this is worthwhile, because VPN companies love to make these sorts of things hard to find, with their expensive mass advertising campaigns to control SEO.
I think this is worthwhile, because VPN companies love to make these sorts of things hard to find, with their expensive mass advertising campaigns to control SEO.
https://deploy-preview-2010--privacytools-io.netlify.app/providers/vpn/#info
I also feel as if The Hated One's video on Tor vs VPN video has a place in that section seeing as we're editing this page. Otherwise LGTM!
I also feel as if The Hated One's video on [Tor vs VPN](https://yewtu.be/watch?v=6ohvf03NiIA) video has a place in that section seeing as we're editing this page. Otherwise LGTM!
I also feel as if The Hated One's video on Tor vs VPN video has a place in that section seeing as we're editing this page. Otherwise LGTM!
we could perhaps do what we did with the other VPN video and put it below that one? I did watch that video and thought it was pretty accurate.
> I also feel as if The Hated One's video on [Tor vs VPN](https://yewtu.be/watch?v=6ohvf03NiIA) video has a place in that section seeing as we're editing this page. Otherwise LGTM!
we could perhaps do what we did with the other VPN video and put it below that one? I did watch that video and thought it was pretty accurate.
@dngray yes, that was what I meant, because I don't think it has anything to do with breaches really. Puting it next to the Tom Scott video is were it should be.
@dngray yes, that was what I meant, because I don't think it has anything to do with breaches really. Puting it next to the Tom Scott video is were it should be.
@dngray yes, that was what I meant, because I don't think it has anything to do with breaches really. Puting it next to the Tom Scott video is were it should be.
> @dngray yes, that was what I meant, because I don't think it has anything to do with breaches really. Puting it next to the Tom Scott video is were it should be.
ah yeah I thought that's what you meant. See https://github.com/privacytools/privacytools.io/pull/2011
Mikaela
(Migrated from github.com)
approved these changes 2020-08-05 09:50:15 +00:00
I wonder if you might want to prepare for https://github.com/privacytools/privacytools.io/issues/1808 by mentioning the domains or sites where the links go to as currently there is no indication for screen reader users what happens upon clicking (while not-vision impaired people can read from bottom left which domain will be visited).
I wonder if you might want to prepare for https://github.com/privacytools/privacytools.io/issues/1808 by mentioning the domains or sites where the links go to as currently there is no indication for screen reader users what happens upon clicking (while not-vision impaired people can read from bottom left which domain will be visited).
jonah
approved these changes 2020-09-17 14:11:25 +00:00
freddy-m
(Migrated from github.com)
approved these changes 2020-09-24 11:59:22 +00:00
This repo is archived. You cannot comment on pull requests.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
jonah
I think this is worthwhile, because VPN companies love to make these sorts of things hard to find, with their expensive mass advertising campaigns to control SEO.
https://deploy-preview-2010--privacytools-io.netlify.app/providers/vpn/#info
I also feel as if The Hated One's video on Tor vs VPN video has a place in that section seeing as we're editing this page. Otherwise LGTM!
we could perhaps do what we did with the other VPN video and put it below that one? I did watch that video and thought it was pretty accurate.
@dngray yes, that was what I meant, because I don't think it has anything to do with breaches really. Puting it next to the Tom Scott video is were it should be.
ah yeah I thought that's what you meant. See https://github.com/privacytools/privacytools.io/pull/2011
I wonder if you might want to prepare for https://github.com/privacytools/privacytools.io/issues/1808 by mentioning the domains or sites where the links go to as currently there is no indication for screen reader users what happens upon clicking (while not-vision impaired people can read from bottom left which domain will be visited).