IPv6 badge for Mullvad #1537

Merged
dngray merged 2 commits from pr_ipv6_vpn_badge into master 2019-11-29 09:01:07 +00:00
dngray commented 2019-11-29 05:02:03 +00:00 (Migrated from github.com)
Resolves PR https://github.com/privacytoolsIO/privacytools.io/issues/1435
netlify[bot] commented 2019-11-29 05:04:38 +00:00 (Migrated from github.com)

Deploy preview for privacytools-io ready!

Built with commit 5fe23dccbd

https://deploy-preview-1537--privacytools-io.netlify.com

Deploy preview for *privacytools-io* ready! Built with commit 5fe23dccbd636bd52953db5c759471c8baebec24 https://deploy-preview-1537--privacytools-io.netlify.com
nitrohorse commented 2019-11-29 05:38:08 +00:00 (Migrated from github.com)

I’m wondering if we should add IPv6 support under our criteria: https://deploy-preview-1537--privacytools-io.netlify.com/providers/vpn/#criteria, specifically Technology > Best Case?

I’m wondering if we should add IPv6 support under our criteria: https://deploy-preview-1537--privacytools-io.netlify.com/providers/vpn/#criteria, specifically Technology > Best Case?
dngray commented 2019-11-29 05:57:09 +00:00 (Migrated from github.com)

I’m wondering if we should add IPv6 support under our criteria: https://deploy-preview-1537--privacytools-io.netlify.com/providers/vpn/#criteria, specifically Technology > Best Case?

Yes we should.

> I’m wondering if we should add IPv6 support under our criteria: https://deploy-preview-1537--privacytools-io.netlify.com/providers/vpn/#criteria, specifically Technology > Best Case? Yes we should.
nitrohorse (Migrated from github.com) approved these changes 2019-11-29 06:18:05 +00:00
Mikaela (Migrated from github.com) approved these changes 2019-11-29 08:59:53 +00:00
This repo is archived. You cannot comment on pull requests.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#1537
No description provided.