Not if the response to the AirPods losing capacity is to replace them altogether.
The world is a big place. Of course it happens. But, colloquially speaking, "getting people's attention" suggests that more than a rounding error took heed. I'm glad your CEO cares. It makes a difference and I hope you…
At best, it would come down to the details of what their marketing materials have claimed wrt to keeping contents secret. Do you have anything concrete they've promised? I don't remember anything, but maybe that's just…
What grounds would the lawsuit be based on? I can’t imagine that slurping any kind of data would be inconsistent with their EULA. The only risk would be the reputational damage. And as far as their bottom line is…
WhatsApp is E2EE, but Meta controls both ends. Instead of reading your plaintext on the server, they read it on the client. Not that tricky. I presume the hardest part would be avoiding detection via decompilation and…
Just like well-publicized data breaches over the years got people’s attention? Color me skeptical.
That’s why I think atproto is cool. It’s the only thing I’m aware of that provides for actually forking a public social network.
Same thing as if something equivalent happens to your VPN service I guess? Switch to another one. Oh yeah crap, you're right about DNS over regular TCP. I totally brainfarted on that.
These things you suggest incur significant latency. Also, can you simply pipe DNS over Tor? I don't see how, since Tor is TCP-only. I suppose DoT or DoH could potentially work, but not all authoritative servers may…
- Personal details isn't the point (and while a VPN service may have those, a big DNS resolver certainly doesn't)--the point is that correlating DNS traffic with your source/home IP address is likely easier with a big…
I don't see how that's an improvement over using a big public resolver. Probably worse privacy (you've basically just swapped your ISP for another virtual ISP), and worse performance (likely longer network paths from…
I don’t honestly see how that’s necessarily better. Now your ISP can tap your individual household to see what’s being queried. Whereas if you use Do[THU] to connect to some remote recursive resolver it practically…
I'm not advocating dual stack either. Like I said in my other reply to you, I am suggesting IPv4-as-a-service using standard translation technologies and architectures.
I'm not suggesting dropping v4 connectivity altogether. I'm suggesting migration to a v6-only core by providing IPv4 as a service via 464XLAT, IPv6-Mostly, or only offering IPv4 to select network segments using…
> So I don't bother with ipv6 - it's a toy. Since I can't edit my other comment: I don't agree with this. I agree with the challenges of v6 that wouldn't be there if translation had been prioritized from the start, and…
Well performance really isn't something I would point to at all. While I believe it can become problematic with great scale (e.g. those expensive CGNAT boxes), it's more the architectural and connectivity aspects that…
Yep, agreed on pretty much all counts. The end goal is obviously the same for both dual-stack and translation technologies. But the latter makes things so much lower risk and gives you (the network operator) actual…
> If ISP would have deployed IPv6 early enough in time, like deutsche Telekom had a properly IPv6 network ready in 2012 or even before. I think you forgot half a sentence here. What was your point? > And dual stack is…
Very much agreed with you that IPv6 is indeed fine. I think it’s even good, even beyond the necessary feature of providing an appropriate number of prefixes. But I do narrowly agree with GP that CLAT should’ve been a…
Ah great, thanks for the link! A very clearly-written RFC.
Adding on to what others say about printenv, various diagnostic tools (e.g. crash reporting stuff) will capture the environment. Env vars are just categorically so easy to accidentally leak that it can’t even be classed…
I’ve never even heard of the DHCP option for this. How widely adopted is it? It’s surprising to hear it called “the right way” when it wouldn’t work for a single-stack IPv6 (or IPv6-mostly, probably) network.
I’ve seen website.com/z/{initiative} before, and it worked quite well.
Could put pressure on data center margins, but not revenue, and not necessarily gross profit.
This point applied to normal NAT as well as CGNAT specifically. And hole punching gets a lot simpler when you’re behind NAT since you don’t need any kind of rendezvous server to determine port mappings. In other words,…
Not if the response to the AirPods losing capacity is to replace them altogether.
The world is a big place. Of course it happens. But, colloquially speaking, "getting people's attention" suggests that more than a rounding error took heed. I'm glad your CEO cares. It makes a difference and I hope you…
At best, it would come down to the details of what their marketing materials have claimed wrt to keeping contents secret. Do you have anything concrete they've promised? I don't remember anything, but maybe that's just…
What grounds would the lawsuit be based on? I can’t imagine that slurping any kind of data would be inconsistent with their EULA. The only risk would be the reputational damage. And as far as their bottom line is…
WhatsApp is E2EE, but Meta controls both ends. Instead of reading your plaintext on the server, they read it on the client. Not that tricky. I presume the hardest part would be avoiding detection via decompilation and…
Just like well-publicized data breaches over the years got people’s attention? Color me skeptical.
That’s why I think atproto is cool. It’s the only thing I’m aware of that provides for actually forking a public social network.
Same thing as if something equivalent happens to your VPN service I guess? Switch to another one. Oh yeah crap, you're right about DNS over regular TCP. I totally brainfarted on that.
These things you suggest incur significant latency. Also, can you simply pipe DNS over Tor? I don't see how, since Tor is TCP-only. I suppose DoT or DoH could potentially work, but not all authoritative servers may…
- Personal details isn't the point (and while a VPN service may have those, a big DNS resolver certainly doesn't)--the point is that correlating DNS traffic with your source/home IP address is likely easier with a big…
I don't see how that's an improvement over using a big public resolver. Probably worse privacy (you've basically just swapped your ISP for another virtual ISP), and worse performance (likely longer network paths from…
I don’t honestly see how that’s necessarily better. Now your ISP can tap your individual household to see what’s being queried. Whereas if you use Do[THU] to connect to some remote recursive resolver it practically…
I'm not advocating dual stack either. Like I said in my other reply to you, I am suggesting IPv4-as-a-service using standard translation technologies and architectures.
I'm not suggesting dropping v4 connectivity altogether. I'm suggesting migration to a v6-only core by providing IPv4 as a service via 464XLAT, IPv6-Mostly, or only offering IPv4 to select network segments using…
> So I don't bother with ipv6 - it's a toy. Since I can't edit my other comment: I don't agree with this. I agree with the challenges of v6 that wouldn't be there if translation had been prioritized from the start, and…
Well performance really isn't something I would point to at all. While I believe it can become problematic with great scale (e.g. those expensive CGNAT boxes), it's more the architectural and connectivity aspects that…
Yep, agreed on pretty much all counts. The end goal is obviously the same for both dual-stack and translation technologies. But the latter makes things so much lower risk and gives you (the network operator) actual…
> If ISP would have deployed IPv6 early enough in time, like deutsche Telekom had a properly IPv6 network ready in 2012 or even before. I think you forgot half a sentence here. What was your point? > And dual stack is…
Very much agreed with you that IPv6 is indeed fine. I think it’s even good, even beyond the necessary feature of providing an appropriate number of prefixes. But I do narrowly agree with GP that CLAT should’ve been a…
Ah great, thanks for the link! A very clearly-written RFC.
Adding on to what others say about printenv, various diagnostic tools (e.g. crash reporting stuff) will capture the environment. Env vars are just categorically so easy to accidentally leak that it can’t even be classed…
I’ve never even heard of the DHCP option for this. How widely adopted is it? It’s surprising to hear it called “the right way” when it wouldn’t work for a single-stack IPv6 (or IPv6-mostly, probably) network.
I’ve seen website.com/z/{initiative} before, and it worked quite well.
Could put pressure on data center margins, but not revenue, and not necessarily gross profit.
This point applied to normal NAT as well as CGNAT specifically. And hole punching gets a lot simpler when you’re behind NAT since you don’t need any kind of rendezvous server to determine port mappings. In other words,…