That’s not as effective, since it can’t block anything that’s hosted from a hostname that also serves regular content without also blocking the regular content. It also can’t trick websites into thinking that nothing is blocked and it can’t apply cosmetic rules. I use it for my devices, but in browsers I supplement it with uBlock Origin (or whatever is available in that browser).
That’s because Bitwarden used various methods to enable auto-fill in places where the native auto-fill capability of Android doesn’t work. See https://bitwarden.com/help/auto-fill-android/ for an explanation.
I’m not going to defend Apple’s profit maximization strategy here, but I disagree. Most people won’t end up buying a cable and adaptare because they already have one, and in contrast to those pieces made of plastic and metal, the packaging is mostly made of paper. I’m pretty confident that the reduction in plastic and metal makes up for the extra packaging that’s produced for the minority that does buy a cable and/or adapter.
Telegram’s “privacy” is fully based on people trusting them not to share their data - to which Telegram has full access - with anyone. Well, apart from the optional E2EE “secret chat” option with non-standard encryption methods that can only be used for one on one conversations. If it were an actual privacy app, like Signal, they could’ve cooperated with authorities without giving away chat contents and nobody would’ve been arrested. I’m a Telegram user myself and I from a usability standpoint I really like it, but let’s be realistic here: for data safety I would pick another option.
I would look into how Matrix handles this, for example. It involves unique device keys, device verification from a trusted device, and cross-signing. It’s not just some private key that’s spread around to random new devices where you lose track of.
They’ve implemented it in such a way that you only have access to an encrypted chat on a single device, so no syncing between devices. Syncing E2EE chats across devices is more difficult to pull off, but it’s definitely possible and other services do that by default.
“Uncensored”: https://x.com/KarlMaxxer/status/1823753493783699901. I don’t know if this is really true, but if it is, it’s something that they should’ve called out in their article.
Right, I see what you mean now. I misread your comment as explaining something that was already clear.
A false positive is when it incorrectly determines that a human written text is written by AI. While a detection rate of 99.9% sounds impressive, it’s not very reliable if it comes with a false positive rate of 20%.
In my opinion it’s more useful to look at grams of protein per kcal. You can only eat so many calories in a day, so that dictates your protein intake for a large part. If you eat 2000 kcal worth of peanuts, you’d ingest 80 grams of protein. With chickpeas that would be 110 grams and with chicken breast 425 grams. You don’t eat just protein rich things, so the higher the value, the higher your chances of ingesting enough protein when combined with (other) vegetables, grains, rice, oil, etc.
I know that some people will read this comment as if I’m promoting meat consumption, so let me add that I firmly believe that the world would be a better place if we ate a lot less meat. I’m just using these examples for demonstration purposes, as they’re all at the right side of the graph. It’s always an option to supplement with a plant based protein powder.
I might be wrong, but I think they will probably let the OS handle the biometrics offline, which means that they won’t have access to your biometrics, they just work with cryptographic keys. Otherwise it doesn’t make sense, as apps usually don’t have direct access to the fingerprint reader. It will probably be similar to how a passkey works.
“Our analysis shows that the two voices are similar but likely not identical,” Berisha said.
They also point out the main differences between the two voices in the paragraphs below this quote. I do believe that they hired a voice actress and that they didn’t train on SJ’s voice, or at least not entirely. However, I wouldn’t be surprised if there was big push for finding a voice similar to SJ’s voice in Her, no matter how much they deny this.
For me they only work in relatively quiet environments, or with earplugs. As soon as a car drives by it completely drowns out the sound. With music that might not be an issue, but with podcasts or calls it’s very annoying. I’ve bought earplugs especially for this, as my other earbuds have issues with wind while running, but it does feel like it’s defeating the purpose a bit. I guess turning them all the way up would also work, but that doesn’t feel healthy. Other than that I like them and the mic quality is also good according to people I’ve spoken with over the phone.
I’m not sure, it depends on your configuration and blocking list. I don’t use native tracking protection, and my blocklist (oisd) prioritizes functionality over blocking, so in my case everything just works and I don’t have anything special added to my whitelist. I don’t like DNS blocking to be in the way and I also share my configuration with some family members, so that’s why I’ve made this choice, but if you prefer a stricter approach you might have to do some whitelisting.
If the iCloud Private Relay ODoH DNS server is used it will show up as a DNS leak, even if the IP address from its response isn’t used for browsing. For privacy it doesn’t matter, as with ODoH the DNS resolver doesn’t know your IP or identity, the most important thing is whether it will bypass the NextDNS blocklist. In my testing I couldn’t visit any website that was blocked by NextDNS, meaning that the iCloud DNS resolver wasn’t used as the primary DNS resolver, which matches with their documentation (that page 10 that I linked to earlier). Note that Apple will only use a custom DNS resolver if you’re using the native DoH option, so for example the configuration that you can get from https://apple.nextdns.io/.
You can easily test it yourself: block a hostname in NextDNS that you haven’t visited recently (due to cache) and try to visit it in Safari.
I don’t know why Apple still uses the Cloudflare DNS resolver even if it seems to be ignoring its responses. Maybe they use it for some custom metadata that’s sent along with the request which somehow is important for the relay. All I know is that I’ve never seen it bypassing the NextDNS blocklist, which again is exactly how it’s documented by Apple.
So for some reason Apple keeps using their DNS resolver even with a custom DoH resolver configured, but in my testing it didn’t affect the blocking capabilities of NextDNS at all, meaning that the answers from their resolver are just ignored (or used for some other purpose). The way NextDNS knows that you’re using another resolver is by letting the browser resolve some unique hostnames, so that way it will show up even if the answers from that resolver aren’t used. As to why Apple does this I don’t know. In theory it could be the case that Apple just used whichever answer arrives first and that NextDNS just happened to be faster in my testing, but that doesn’t match with how it’s documented in their PDF.
Which one to pick (if you don’t just want to use them at the same time) depends on what your goal is. I use iCloud Private Relay + NextDNS + AdGuard, but nowadays I mainly use another browser with a built-in adblocker, so iCloud Private Relay and AdGuard aren’t used in that case.
I use NextDNS everywhere I can and use a list that prioritizes not breaking anything. It’s a nice backstop. It’s not a replacement for an in-browser adblocker in my opinion, unless you don’t care that it’s less effective.
Contrary to common believe, iCloud Private Relay and NextDNS are compatible and can both be enabled at the same time, see page 10 of https://www.apple.com/icloud/docs/iCloud_Private_Relay_Overview_Dec2021.pdf. When you try to visit a blocked hostname in Safari, you’ll see that it won’t work. This is something that I’ve personally confirmed.
What NextDNS solves and iCloud Private Relay doesn’t, is blocking hostnames system wide, thereby completely blocking some ads and tracking. What iCloud Private Relay solves is hiding your browsing traffic a bit better within your local network and from your ISP, as well as hiding your IP from trackers and hiding your identity from their DNS resolver (not from NextDNS, though).
Some background information why using HTTPS together with encrypted DNS doesn’t fully hide which websites you visit (yet): https://blog.cloudflare.com/announcing-encrypted-client-hello.
If I had to choose, I’d go with NextDNS for system wide blocking and I’d add an adblocker browser extension to block trackers and ads that can’t be blocked with DNS based blocking. But you don’t have to choose and can use both at the same time.
For me it works fine, but I guess that might be because I use the flatpak version of Firefox.
deleted by creator
It’s off by default, but activated when you end your search query with a question mark. That option can be turned off.