Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)E
Posts
4
Comments
1088
Joined
3 yr. ago

  • DNS?

    Jump
  • For the same reason you’re running AdGuard and not just pointing all your devices at the recursive upstream.

    You’re using AdGuard / Pihole as an ad sinkhole, not just to cache and forward DNS requests. Like if you really wanted to you could hack together something in Unbound to do that, but why would you do that when Pihole already exists? You have two things built for purpose.

  • DNS?

    Jump
  • If you want to run your own recursive DNS server, why would you run two separate DNS servers?

    I’m not sure I understand your question. A recursive DNS server and a local DNS cache/forwarder/are two different things with two different purposes. You will always need both. You yourself are using AdguardHome and that is just connecting to recursive DNS server upstream. In my scenario you’re just running both yourself instead of you running one and then letting a 3rd party run the other for you.

    Your outbound queries will still be unencrypted, so your ISP can still log them and create an advertising profile based on them.

    You can encrypt the recursive queries through your ISP if you want to. Though the effectiveness of any profiling your ISP would do to you are minimized by Qname minimization that Unbound does by default.

    If you’re just using DoH then you’re just shifting who’s making that advertising profile on you from your ISP to whoever is hosting your upstream recursive DNS server. It doesn’t matter how much encryption you do because on the other end of that encrypted connection is the entity who you’re giving all your queries to.

  • DNS?

    Jump
  • I would say Pihole is a better choice than AdGuard home because PiHole just runs on top of dnsmasq. Throw Unbound on there too as your upstream recursive resolver and you’re set. You don’t even need to worry about an encrypted session to your upstream anymore because your upstream is now your loopback.

  • If you can get a much better deal on a Belkin or Anker cable or anything you know is a decent brand then I’d say go for it. You don’t NEED an Apple cable. It’s just a fool proof way to get a cable that you know will work well.

  • Yeah, why not? A quick look at Best Buy and I can see that the Apple USB-C cable is $15.99 and the cheapest reputable third party USB-charger is $13.99. You save a whopping $2.

    So if you’re a deal-oriented shopper you’re probably not even going to buy from a reputable third party, you’ll probably go with the $6 one from the gas station of dubious quality. And you’ll probably be fine. Or maybe after 3 months it causes a short and burns your house down. Best $10 you ever saved.

    Or you can take literally all of the guesswork out of it and just go with whatever manufacturers cable, spend the extra $10 on a cable that will last you years. The point isn’t buying something Apple branded, they don’t even brand it physically. The point is to just buy something guaranteed to work.

  • I think you are right but I wasn’t sure. Like technically you’ll still see the details if you open the certificate but… who’s doing that?

  • Because you’re getting a product that you know isn’t a cheap knockoff that will burn your house down, and you know it will charge your phone at the fastest speed it’s capable of.

    You can of course get the same experience buying third party, but then you have to spend time doing research on which one to buy for your device, and the reputable third party brands can cost just as much as the Apple ones anyway.

  • The point of paid SSL at this stage in the game are the higher tiers of verification. Instead of just verifying that you own the domain, you can verify that you are who you say you are. These are called Extended Validation and Organizational Validation certificates. This has historically been desirable by businesses. It used to be that these higher tier certs would not only give you a lock icon in the address bar of a web browser, but also a little blurb confirming your organization is legit. Not sure if this is still the case though. You will see the extended validation when you check the sites certificate though for sure.

    As far as encryption and security, there’s no difference. Also side note, the Comodo brand still technically exists but it was bought by Sectigo like 7 years ago.

  • Yeah but also even when you’re paying, you’re still the product.

  • God just imagine the racism.

  • Well I just bring it up because part of RCS is encryption, but there are a lot of asterisks and one of them is that RCS with Apple will never be encrypted.

    It’s one of the main problems with RCS is that whether or not the chat is secure depends on the implementation and is dependent on sender and receiver, unlike iMessage where you know that when the chat bubbles are blue, your chat is encrypted.

    IMO inconsistent encryption is worse than no encryption at all, due to the false sense of security.

  • You do not know for absolute certain fact, which I know for absolute certain fact because the likelihood of your claim is incredibly low.

    Are your friends phones running Android 5.0 or later? (I’m sure they are) they have RCS. End of story. This is not something you can dispute, you’re just wrong.

    You can be in denial about it, but your friends have RCS.

  • You having no clue is not the same thing as being absolutely positive.

  • WhatsApp is big outside the U.S. inside the U.S., I don’t know a single person who uses it.

  • Important to note those chats won’t be encrypted.

  • It’s more than likely that every single one of your Android friends have RCS on their phones.

  • It’s perfectly reasonable there’s no shame involved.

  • I tried Firefish but at no point in time did it ever actually work well. 85% of the content just wouldn’t load.

  • Yeah let’s not repeat the mistakes of 2016 that put him in the white house the first time