News for hackers. Stuff that matters.
Re:Cloudflare Ohttp Gateway by 0x073 on Saturday October 03, 2026 @05:56AM (#49942803)
As cloudflare is the gateway for half the Internet and the other half is meta Google and Microsoft, I would prefer to share my IP with the website I visit instead some big tech companies.

But maybe I get privacy wrong.

Re:Cloudflare Ohttp Gateway by someonebaggy on Saturday October 03, 2026 @08:49AM (#49943810)
Why not both? When browsing Microsoft, give your IP to Cloudflare. When browsing Pouet, give your IP to Pouet.
Re:Cloudflare Ohttp Gateway by ThatMedicIsASpy on Saturday October 03, 2026 @10:38AM (#49944684)
What if the solution is garbage? There are ad blockers that click every ad. Random google searches, random chatbot searches, random clicks.

I have a feeling that privacy is easier to protect if you just mix what you want to hide with a lot of garbage.

Re:Cloudflare Ohttp Gateway by stubish on Saturday October 03, 2026 @08:27PM (#49949282)
If a human was manually reviewing your logs, maybe. But that isn't the problem. Your stream is already a pile of garbage amongst billions of other piles of garbage. Programs will find the keywords they are looking for no matter if they are looking in a big pile of garbage or small.
Re:Cloudflare Ohttp Gateway by krzyk on Saturday October 03, 2026 @11:33AM (#49945164)
There are other CNDs, and Cloudflare isn't event the largest one, it has best marketing and free solutions.
Re:Cloudflare Ohttp Gateway by jbverschoor on Saturday October 03, 2026 @12:05PM (#49945431)
Cloudflare provides so much more than just CDN, and in a very nice package
Re:Cloudflare Ohttp Gateway by krzyk on Sunday October 04, 2026 @12:07PM (#49955126)
As do others, they had to because CDN is not that good source of income nowadays, so most went into other offerings that are more profitable.

As I wrote, Cloudflare excel at marketing. And offers to consumers (as opposed to B2B).

Re:Cloudflare Ohttp Gateway by johnhess on Saturday October 03, 2026 @12:25PM (#49945607)
This separates who sees what. Cloudflare (or any OHTTP gateway) sees who talks to who, but can't see the content. The service sees the content but not who you are/your IP.

You can imagine a lot of threat models where who you talk to isn't sensitive, nor is "someone talked to them about X" but knowing both facts is a risk.

Re:Cloudflare Ohttp Gateway by thayne on Saturday October 03, 2026 @01:58PM (#49946331)
For a single transaction that's great. The problem is whene a large fraction of the internet is served by a single entity (say cloudflare), then that entity has information about what sites/customers were visited by a specific ip address, and which ip addresses visited a certain site/customer.

Although, that is still better than them having the source ip and the content.

Re:Cloudflare Ohttp Gateway by juros on Thursday October 08, 2026 @04:43AM (#50003355)
that's a big misunderstanding. Cloudflare DOES see the contents because they terminate TLS. All requests and responses, with bodies, credentials and cookies in plaintext.

The NSA's dream made true.

Re:Cloudflare Ohttp Gateway by charcircuit on Saturday October 03, 2026 @03:42PM (#49947133)
Many of those websites are hosted by big tech companies via their cloud offerings. These clouds have even developed software for reading files within the VMs they are hosting.