DNS: add Nebulo as worth mentioning & warn about DoH metadata & sort worth mentioning/additional information into sublists #1200
No reviewers
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1200
Loading…
Reference in New Issue
No description provided.
Delete Branch "nebulo"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Resolves: #1187
Check List
I have read and understand the contributing guidelines.
I have listed the source code.
This project is free/libre software.
This project has an associated discussion.
Netlify preview for the mainly edited page: https://deploy-preview-1200--privacytools-io.netlify.com/providers/dns/#icanndns
Code Repository (if applicable): https://git.frostnerd.com/PublicAndroidApps/smokescreen/
Deploy preview for privacytools-io ready!
Built with commit
6a91bff702
https://deploy-preview-1200--privacytools-io.netlify.com
TODO: find a more authoritative source than someone on our issue tracker? :)
Show me a more authoritative source than the RFC!
English: Do things contain or include metadata?
I think "contains" is fine. I think we could also make this a tad more readable by:
@ -300,0 +293,4 @@
<li><em>Firefox</em> comes with built-in DoH support with Cloudflare set as the default resolver, but can be configured to use any DoH resolver. <span class="badge badge-warning" data-toggle="tooltip" data-placement="bottom" data-original-title='"Cloudflare has agreed to collect only a limited amount of data about the DNS requests that are sent to the Cloudflare Resolver for Firefox via the Firefox browser."'><a href="https://developers.cloudflare.com/1.1.1.1/commitment-to-privacy/privacy-policy/firefox/"><i class="fas fa-exclamation-triangle"></i></a></span> Currently Mozilla is <a href="https://blog.mozilla.org/futurereleases/2019/07/31/dns-over-https-doh-update-detecting-managed-networks-and-user-choice/">conducting studies</a> before enabling DoH by default for all US-based Firefox users.</li>
</ul>
</li>
<li><strong>Encrypted DNS clients for mobile:</strong>
Could we move this directly above or below DNSCloak just to group similar apps together?
Small suggestions, otherwise LGTM
Sure, will do
@ -300,0 +293,4 @@
<li><em>Firefox</em> comes with built-in DoH support with Cloudflare set as the default resolver, but can be configured to use any DoH resolver. <span class="badge badge-warning" data-toggle="tooltip" data-placement="bottom" data-original-title='"Cloudflare has agreed to collect only a limited amount of data about the DNS requests that are sent to the Cloudflare Resolver for Firefox via the Firefox browser."'><a href="https://developers.cloudflare.com/1.1.1.1/commitment-to-privacy/privacy-policy/firefox/"><i class="fas fa-exclamation-triangle"></i></a></span> Currently Mozilla is <a href="https://blog.mozilla.org/futurereleases/2019/07/31/dns-over-https-doh-update-detecting-managed-networks-and-user-choice/">conducting studies</a> before enabling DoH by default for all US-based Firefox users.</li>
</ul>
</li>
<li><strong>Encrypted DNS clients for mobile:</strong>
How about copying the XMPP syntax from https://www.privacytools.io/software/real-time-communication/#im to do it?
I didn't see the logic before, so I just put it in order of addition. I will try to commit it so we will see how it looks like.
@ -300,0 +293,4 @@
<li><em>Firefox</em> comes with built-in DoH support with Cloudflare set as the default resolver, but can be configured to use any DoH resolver. <span class="badge badge-warning" data-toggle="tooltip" data-placement="bottom" data-original-title='"Cloudflare has agreed to collect only a limited amount of data about the DNS requests that are sent to the Cloudflare Resolver for Firefox via the Firefox browser."'><a href="https://developers.cloudflare.com/1.1.1.1/commitment-to-privacy/privacy-policy/firefox/"><i class="fas fa-exclamation-triangle"></i></a></span> Currently Mozilla is <a href="https://blog.mozilla.org/futurereleases/2019/07/31/dns-over-https-doh-update-detecting-managed-networks-and-user-choice/">conducting studies</a> before enabling DoH by default for all US-based Firefox users.</li>
</ul>
</li>
<li><strong>Encrypted DNS clients for mobile:</strong>
I think it looks better, but now I have to sort everything else too, not that it's a bad thing:
I fear we may be causing merge conflicts for each other depending on which PRs are merged, but if that happens, we can resolve them.
So currently it looks like this:
What's up with the excess spaces? I tried to make it readable while I worked on it in mousepad.
Open question: should I keep the
:
s or not, before bolding I thought that it definitely needs something, but now I am not sure whether to move them outside of the<strong>
s or drop them entirely.I understand that we don't have a mobile-first attitude, so desktop software is what a visitor is most likely looking for and for now it's not so long, so I think it makes the most sense being on top.
I think it's the second most likely thing someone is looking for
Anyone can run them, so I think it's a good third thing to list
I think it's the most technical thing we list and requires the most, so it's good to be on the bottom of recommendations.
I first thought about putting it on top, but as the heading says "Worth mentioning and additional information" I thought it should be on bottom and I cannot think of anything better here. Isn't "further reading" generally something that one doesn't have to read, but which can be of interest to someone who is especially interested in the topic?
I didn't start touching this file as there hasn't been feedback (and I forgot it), but should I start sorting the recommendations there? I hope not.
Yeah, makes sense to me 👍
I wonder if these titles are as clear and a bit less wordy?
Encrypted DNS clients for desktop:
Encrypted DNS clients for mobile:
Yeah, makes sense to me!
Ideally I think each section would have the same order as what's on the section but I think as long as the source code is listed in the right section that's fine.
I think just to keep the HTML tidy, we should move the
</li>
tags to the bottom of their corresponding</ul>
tag, wrapping the list. Ex:Some further suggestions but LGTM otherwise; glad to see this further organized! 😄
I tried to change the order to that
Looks great!