Updatating the DNS examples to non tracking #122
Conversation
As the DNS servers added in this document refers to well known tracking servers, I've taken the libaty to replace them to some DNS servers that should not be tracking servers. In this case quad9's and yours ------- Known non-tracking DNS servers that at the same time offers protection from tracking, spyware, adware, phishing etc.: These are using Ultimate.Hosts.Blacklist lists for blacklisting <Ultimate-Hosts-Blacklist/Ultimate.Hosts.Blacklist#590> - 88.198.70.38 - 2a01:4f8:140:5021::38 - 88.198.70.39 - 2a01:4f8:140:5021::39 ------- These are using <https://www.mypdns.org/> RPZ zones <https://www.mypdns.org/source/Matrix/repository/master/> - 95.216.209.53 - 2a01:4f8:1c0c:5f61::53 - 116.203.32.67 - 2a01:4f9:c010:410e::53 -------
There are still room for improvement as I currently don't know the full intention behind all the tables 😒 @funilrys Please enlighten me, so we can get the docs up-to-date
As I'm less trilled of GH than many of you, I challenge this uri to be using my own profile at mypdns.org vs GH Secundly change the line length to match 80 char console best practice.
Again, switching to my own profile url, as I'm less trilled with GH (tracking) vs own project (domain) profile Also added sqlalchemy to the list
As @PyFunceble is getting more and more popular, it's time to update the list of projects using this software.
Related to <#86>
|
Awaiting the review and comments on https://github.com/spirillen/PyFunceble/pull/9 |
| @@ -6,6 +6,7 @@ Why do we use "databases"? | |||
|
|
|||
| We use databases to store data while we run the tests. When globally talking | |||
| about databases, we are indirectly talking about the following subsystems. | |||
| (JSON) | |||
There was a problem hiding this comment.
Line break. (The 80 chars for consoles support)
I added it as this part is about JSON and does have nothing to do with the SQL layout
| If the environment variables are not found, you will be asked to | ||
| prompt the information. | ||
|
|
||
| SQL Layout: |
There was a problem hiding this comment.
As of a possible merge of https://github.com/funilrys/PyFunceble/tree/issue-118 in the coming days, All INT (except for http_status_code) will be converted to BIGINT.
There was a problem hiding this comment.
I'll take note of that. Why I've left it with a "open" wildcard (*INT???), as you notice they are followed by a note that I would have expected a BOOL in those cases.
What about my question marks in the SQL Layout: L118-L177 ?
Another thing I just noticed, it the lines L73-L108 even relevant anymore after changing to sqlachemy?
|
Let's get this one merged Then we polish it on the dev branch |
I've Added the second level title of `SQL Layout` to draft. This is done for the time of developing the SQL as I'll foresees several changes in the near future.
Added Ubuntu 20.04 Focal Fossa test environment as Bionic it starting to leave the room Also replaced MariaDB 10.4 (old stable) with MariaDB 10.5 (new stable)
|
Closing. Please resubmit to the |
|
Seem right, as the table have been under a heavy transformation as well |
As the DNS servers added in this document refers to well known tracking servers, I've taken the libaty to replace them to some DNS servers that should not be tracking servers.
In this case quad9's and yours
Known non-tracking DNS servers that at the same time offers protection from tracking, spyware, adware, phishing etc.:
These are using Ultimate.Hosts.Blacklist lists for blacklisting Ultimate-Hosts-Blacklist/Ultimate.Hosts.Blacklist#590
88.198.70.38
2a01:4f8:140:5021::38
88.198.70.39
2a01:4f8:140:5021::39
These are using https://www.mypdns.org/ RPZ zones https://www.mypdns.org/source/Matrix/repository/master/
95.216.209.53
2a01:4f8:1c0c:5f61::53
116.203.32.67
2a01:4f9:c010:410e::53