@mouse@midwest.social, @ferric_carcinization@lemmy.ml, thank you for the help and the links — things are a bit clearer now.
As I understand it, SNI slicing helps obscure the presence of the SNI field in the TLS ClientHello by splitting it into two chunks. The idea, it seems, is to make it more difficult for third-party network filters or DPI systems to detect or extract the SNI reliably.
I was thinking along the same lines. At this point, I have:
Removed all URLs in about:config
Disabled browser updates
Disabled all telemetry settings I could find
Despite all these actions, the browser still sends this request on startup. I'm starting to think it might be a setting that can't be changed via about:config.
In 2025 it sounds funny...
Aux armes, citoyens,
Formez vos bataillons,
Marchez, marchez !
Qu'un sang impur
Abreuve nos sillons !
I see a familiar pattern. First block internet resources, then block VPN, then build your own isolated internet...
Great app for tracking users and funneling EU citizens' data straight to tech giants — love it! 😅
@mouse@midwest.social, @ferric_carcinization@lemmy.ml, thank you for the help and the links — things are a bit clearer now.
As I understand it, SNI slicing helps obscure the presence of the SNI field in the TLS ClientHello by splitting it into two chunks. The idea, it seems, is to make it more difficult for third-party network filters or DPI systems to detect or extract the SNI reliably.
I was thinking along the same lines. At this point, I have:
about:configDespite all these actions, the browser still sends this request on startup. I'm starting to think it might be a setting that can't be changed via
about:config.