Re:UnGoogled Chromium: Chromium with enhanced privacy, contr...
by eloston on Sunday September 25, 2016 @08:52PM
(#12578404)
Yes, it is a lazy way of stopping requests. I also modified Iridium's "trk" scheme code to pick up domains ending in qjz9zk so I can notify the user.
Re:UnGoogled Chromium: Chromium with enhanced privacy, contr...
by RubyPinch on Monday September 26, 2016 @01:02AM
(#12579348)
Could probably make use of the .invalid TLD for this. Should definitely result in less confusion, and it provides something a bit more searchable if people are concerned
- doubleclick([A-Za-z\-]*)\.net#60u613cl1c4\1.qjz9zk
+ doubleclick([A-Za-z\-]*)\.net#doubleclick\1.g.invalid
https://en.wikipedia.org/wiki/.invalid
Re:UnGoogled Chromium: Chromium with enhanced privacy, contr...
by comex on Sunday September 25, 2016 @09:30PM
(#12578586)
Does qjz9zk have any significance? It seems a little elaborate for a fake domain :)
Re:UnGoogled Chromium: Chromium with enhanced privacy, contr...
by RandomlyGen on Monday September 26, 2016 @09:25AM
(#12581570)
It seems like the developer mashed the keyboard.
Edit: see https://github.com/Eloston/ungoogled-chromium/blob/8dd86477d...