Straight from the horse's mouth - China's own Global Times: Chinese schools monitor students activities, targeting truancy with 'intelligent uniforms'

A different view - the Australian Broadcasting Commission: Chinese schools enforce 'smart uniforms' with GPS tracking system to monitor students

There's a lot of anime and, from what I've experienced, people who are fans watch a lot of it. It's a daunting task to keep track of what you've seen, what you've thought of it, what to anticipate coming up, and discovering more that you might like.

What site, app, home-grown system are you using to organize your anime life?

One of the unfortunate realities of open source efforts is that these efforts are often fragmented and scattered all over the place, making things difficult to find. With that in mind, I've started a new GitLab project here consisting of a simple README file that we can use to start tracking the client-side themes and extensions that the community here has been hard at work developing.

The list, at the time of posting this, is empty. The README is sparse and the entire thing is subject to change by the community itself. I will only be reviewing changes to ensure that changes are acceptable before a merge is allowed through (we don't want e.g. malicious links thrown in or perfectly good projects removed by someone acting in bad faith). You can change contribution notes/guidelines, existing language, layout, categories, and whatever else you can think of. If there's something else that you think the repository could use aside from the README, then you're free to issue a merge request to have it reviewed as well.

I'm hoping that this will help us keep track of everything and aid future users in discovering the various tools and themes provided by the community.

Please feel free to discuss guidelines here. Is there anything that shouldn't be allowed on the list? Is there anything that should be taken care of immediately? Are there any immediate concerns? Is there anything else on your mind?

Let's take Google, for example. Google tracks where you physically are - why are some people so much against it? It doesn't hurt me, google just uses it to serve me personalized ads. Why are people so concerned about it?

Google even tracks, which websites do I visit - again, why should I care? When I want to browse anonymously, I use VPN. If I wanted to do something illegal, I guess I won't use google at all and install tor? I'm not sure what should I do in that case, but I'm sure, there are ways to get away from google's sight when people need to.

I don't understand, why some people fight for internet privacy so much. Could someone help me to understand it? What's your opinion on privacy and internet tracking?

Firefox recently introduced DNS over HTTPS (DoH) and Trusted Recursive Resolver (TRR) in nightly builds for Firefox 62.

DoH and TRR are intended to help mitigate these potential privacy and security concerns:

1. Untrustworthy DNS resolvers tracking your requests, or tampering with responses from DNS servers.
2. On-path routers tracking or tampering in the same way.
3. DNS servers tracking your DNS requests.

DNS over HTTPs (DoH) encrypts DNS requests and responses, protecting against on-path eavesdropping, tracking, and response tampering.

Trusted Recursive Resolver (TRR) allows Firefox to use a DNS resolver that's different from your machines network settings. You can use any recursive resolver that is compatible with DoH, but it should be a trusted resolver (one that won't sell users’ data or trick users with spoofed DNS). Mozilla is partnering with Cloudflare (but not using the 1.1.1.1 address) as the initial default TRR, however it's possible to use another 3rd party TRR or run your own.

Cloudflare is providing a recursive resolution service with a pro-user privacy policy. They have committed to throwing away all personally identifiable data after 24 hours, and to never pass that data along to third-parties. And there will be regular audits to ensure that data is being cleared as expected.

Additionally, Cloudflare will be doing QNAME minimization where the DNS resolver no longer sends the full original QNAME (foo.bar.baz.example.com) to the upstream name server. Instead it will only include the label for the zone it's trying to resolve.

For example, let's assume the DNS resolver is trying to find foo.bar.baz.example.com, and already knows that ns1.nic.example.com is authoritative for .example.com, but does not know a more specific authoritative name server.

1. It will send the query for just baz.example.com to ns1.nic.example.com which returns the authoritative name server for baz.example.com.
2. The resolver then sends a query for bar.baz.example.com to the nameserver for baz.example.com, and gets a response with the authoritative nameserver for bar.baz.example.com
3. Finally the resolver sends the query for foo.bar.baz.example.com to bar.baz.example.com's nameserver.
   In doing this the full queried name (foo.bar.baz.example.com) is not exposed to intermediate name servers (bar.baz.example.com, baz.example.com, example.com, or even the .com root nameservers)

Collectively DNS over HTTPs (DoH), Trusted Recursive Resolver (TRR), and QNAME Minimization are a step in the right direction, this does not fix DNS related data leaks entirely:

After you do the DNS lookup to find the IP address, you still need to connect to the web server at that address. To do this, you send an initial request. This request includes a server name indication, which says which site on the server you want to connect to. And this request is unencrypted.
That means that your ISP can still figure out which sites you’re visiting, because it’s right there in the server name indication. Plus, the routers that pass that initial request from your browser to the web server can see that info too.

So How do I enable it?
DoH and TRR can be enabled in Firefox 62 or newer by going to about:config:

• Set network.trr.mode to 2
  • Here's the possible network.trr.mode settings:
    • 0 - Off (default): Use standard native resolving only (don't use TRR at all)
    • 1 - Race: Native vs. TRR. Do them both in parallel and go with the one that returns a result first.
    • 2 - First: Use TRR first, and only if the name resolve fails use the native resolver as a fallback.
    • 3 - Only: Only use TRR. Never use the native (after the initial setup).
    • 4 - Shadow: Runs the TRR resolves in parallel with the native for timing and measurements but uses only the native resolver results.
    • 5 - Off by choice: This is the same as 0 but marks it as done by choice and not done by default.
• Set network.trr.uri to your DoH Server:
  • Cloudflare’s is https://mozilla.cloudflare-dns.com/dns-query
    (but you can use any DoH compliant endpoint)
• The DNS Tab on about:networking will show which names were resolved using TRR via DoH.

Links:
A cartoon intro to DNS over HTTPS
Improving DNS Privacy in Firefox
DNS Query Name Minimization to Improve Privacy
TRR Preferences

I'm not affiliated with Mozilla or Firefox, I just thought ~ would find this interesting.