Nougat

I want a comfy squishy chair.

deleted by creator

Some users might even be tempted to turn to the dark web to escape this wave of state overreach — though we certainly don’t recommend it.

If you’re going to the dark web for porn, you’re gonna have a bad time.

This is what I used before work took away my nice phone and replaced it with a bullshit iPhone. Switched to Overcast since PA is not available for iOS.

Just because “some people” can’t words, that doesn’t mean that you should change the words to suit the people who can’t them.

That’s not what I was talking about.

Technitium does not (necessarily) use a third-party service, but sends all queries directly to the root nodes.

By default, any DNS server will look to the root servers for any query. The root servers only know what DNS servers are authoritative for top level domains (TLDs), and tell the client querying “Hey, go ask the “.com” (for example) server.”

That server knows what DNS servers are authoritative for the zones under .com, and says “Hey, go ask the “querieddomain” server.”

Then your machine asks that server for the “www” (for example) host, and that DNS server says “Here’s the IP.”

Unless the DNS server your machine is pointing at is configured to use a forwarder, wherein queries for any records that it isn’t authoritative for or aren’t in its local cache are resent to whatever DNS server is configured as the forwarder. The recursion like above is done between your DNS server and its forwarder, finally returning you an IP address when one is identified.

There’s a bit more to it than that, but that’s what I was talking about. Out of the box, a DNS server uses root hints, which are IP addresses of the root DNS servers. You would need to configure forwarder(s) in your DNS server if you desire them.

If that was the case, there would be a market for exactly 0 DNS servers.

I’m not sure what you mean by that, but it’s definitely the case.

For the record, any DNS server you choose to employ should default to only using the root servers. You would need to configure your own forwarder IP(s) to point to a general purpose resolver.

… censorship-free …

You should also be aware that even if you use root servers, a DNS server which is authoritative for the domain you are querying may well return different results depending on where in the world you are. This can be in order to direct you to an IP that is closer to you, or because “different global locations get different content” for any reason, including censorship and malicious goals. The latter is definitely less likely than the former, but it’s just as possible.

I didn’t say to use profit to calculate the fine.

There is a comparison here, between the amount of the fine and revenue. I’m saying that a more appropriate comparison would be between the fine and profit.

Not saying the fine is fine, but revenue doesn’t matter here. Profit does.

tl;dr: “Strike that, reverse it.”

They can bid all they want to put ads in front of me, I ain’t gonna see them. Of course, they probably know that, too.

deleted by creator

https://en.wikipedia.org/wiki/Brittany

ICANN controls TLDs. Nobody can “register it.”

The article is literally about how there is precedent for eliminating a country’s TLD when that country no longer exists, in the .su and .yu domains (for USSR and Yugoslavia respectively).

It won’t happen overnight, but it’ll happen.

Bad actors can afford $50 the same as good ones.

The difference between $0 and $50 isn’t really relevant.

LetsEncrypt is legit. A downside is that the certs expire after 90 days. However, that also carries an upside in that it limits the damage in case a certificate is compromised. There are procedures by which you can automatically renew/request (I forget whether they allow renewing an existing cert or require a brand new one) LE certs and apply them to your application, but that can be fiddly to configure.

If you’re not comfortable with configuring automatic certificate cycling, a long-term paid cert would be more appropriate.

While “Cisco Duo” is not listed here:

The following is a list of Cisco’s trademarks and registered trademarks in the United States and certain other countries. Please note, however, that this listing is not all-inclusive and the absence of any mark from this list does not mean that it is not a Cisco trademark.

Trademarks are exactly how rules for naming things works.

Expect this name to change when Cisco comes at them for being too close to Cisco Duo.