NotHereToPlayGames

That's the original author's default config from 2003. Nobody really uses that one anymore. However, I am having a higher success rate with the 2003 default config than I am with anything dated 2008 and newer. So the newer (and more complicated than needed when using in conjuction with NoScript, uMatrix, Stylus, etc) config files are going to be too bloated. So good call, reverting to the 2003 and adding to it as opposed to running something from 2008 and newer and stripping it down.

I admit that I was a bit skeptic on BFilter at first (it has not been updated since 2008). All I kept seeing it block is Google adservers and analytics that I block with other methods. It did block 1x1 pixel ads on https://www.quora.com/Which-website-has-the-most-ads (that Proxomitron also blocks). Although the 1x1 pixel ads on quora were the ONLY blocks (outside of Googlisms) in its log after bouncing around and hunting for ads for over an hour - but it DID block "something" (with all of my other methods disabled), so I cannot discredit it. If you open your config file in a text editor, I'll be able to know what config you are using if you can show us what your "Blocklists" section looks like.

I've added BFilter to my chain. Monitoring...

Are you using the 2019-01-26b1 that JJoe submitted as an update to an older sidki3003 config? I'm starting to think that for "modern usage", I may build up a config completely from scratch. "Modern usage" doesn't really need it to be the Swiss Army Knife that it is (I don't intend to "replace" Stylus, NoScript, uMatrix, and Tampermonkey but rather use in conjunction with).

I don't have a specific header-dependent redirect. I assumed that since www.google.com (and msfn.org) were being filtered that I didn't need the header-dependent redirect.

I haven't been able to get consistent results as of yet I haven't been able to get ProxHTTPSProxyMII to link to Proxomitron. I can get the older ProxHTTPSProxy (no MII at the end), but not the newer ProxHTTPSProxyMII. So I'm not sure if my inconsistency has been due to MII versus non-MII. Everything will filter on www.google.com but as soon as I perform an actual search, 360Chrome seems to be making a parallel connection because the Proxomitron log shows traffic but the page is not being filtered.

I love Stylus.

This "feature" doesn't really concern me. There is no such thing as "privacy". You can not hide. And just "trying" to hide actually fingerprints you like a sore thumb. You either connect to the internet or you live in "the hills" with no electricity and no running water. There is no inbetween. I miss using Proxomitron as a web filter so I am attempting to incorporate the "reborn" version of Proxomitron with Chrome-based browsers. There really is a "crapload" that Proxomitron can do - it is NoScript, uMatrix, UBO, AdBlock Plus, Stylus, Privacy Badger, Tampermonkey, User-Agent Switcher, LastPass, RoboForm, KeePass, EditThisCookie, Awesome Cookie Manager, Popup Blocker, HTTPS Everywhere ALL literally rolled into ONE program.

I was going to screencap where Mypal 27.9.4 logs the MSFN reply box but the reply box no longer even works in Mypal 27.9.4. Did not try NM27, Mypal 28, or NM28. I've basically abandoned them due to finding waayyy tooo many web sites where they simply do not work.

In my humble view, a shout-from-the-rooftops NO, this test can NOT be trusted. I say that because I can get THREE DIFFERENT RESULTS all in the same exact web browser from the same exact computer on the same exact wi-fi network. Change a NoScript or uMatrix setting and the test "result" CHANGES. So that is NOT a "unique fingerprint", plain and simple. HOWEVER, just narrowing a "fingerprint" from thousands down to THREE does still basically have you "identified". So I guess the answer is "yes and no".

ALL browsers are KEYLOGGING your replies in this MSFN reply box. I'll demonstrate using 360Chrome but again, ALL browsers have a KEYLOGGER for this MSFN reply box. Most likely in other forums also, especially if using the same "forum software". For my 360Chrome profile, that KEYLOGGER is being saved here -- <root folder>\360ChromePortable\Chrome\User Data\Default\Local Storage\leveldb\000022.log My 360Chrome loader deletes this file each and every time that I exit, otherwise this 000022.log file would have text from "years ago". Please note that username and password input fields are NOT being keylogged, only this MSFN reply box. I don't see this as "nefarious", you have to be a member here and you have to be logged in, but it is still a "feature" that is "concerning" to some.

Spectre was public knowledge in January 2018 and even "grandma" knew what it was by May through July of 2018. Chrome v69 was released in September 2018. Chrome addressed Spectre and Meltdown vulnerabilities with the release of Chrome v64 in January 2018 -- https://www.express.co.uk/life-style/science-technology/900606/Google-Chrome-update-patch-Meltdown-Spectre-Intel-fix-version-64 Firefox releases also addressed Spectre and Meltdown in January 2018 -- https://support.mozilla.org/bm/questions/1198249 I would keep the 360Chrome v11 (Chrome v69) flag at DEFAULT and not change it at all.

Does this help -- https://developers.google.com/search/blog/2021/03/sharedarraybuffer-notes ?

lol, too funny. You could always use Stylus to move the "mole". Or use Stylus to not even display the "mole". I actually use Stylus to not only not display the "mole", but to not even display that profile "face" AT ALL. No face for Dave-H. No face for D.Draker. No face for Dixel. No blobfish for whoever used to use a blobfish. etc...

Good News (for those that have expressed concerns). Proxomitron blocks MSFN's "keylogger" without any added filters. The "base config" (2019-01-26b1) already blocks the "keylogger" by default (I've only tested in Advanced Mode and not in Standard, Light, or Minimal Mode). Disregard. We will need to add a filter to break the "keylogger". The "base config" (2019-01-26b1) affects the "timer" but where the keylogger is in the duration of that timer may cause the keylogger to still work. My goal is to break it "completely". I don't see anything "nefarious" with that keylogger, but I do see it as a good example to demonstrate why I've used Proxomitron for 18 years and why I'm returning it to my web browser after ~2yrs away from it.

But the Dev Tools will display as present even when I block the font from being fetched -

Here is where uMatrix logs the incoming FontAwesome -

When NoScript, HOSTS file, uMatrix, UBO, you name it, blocks a font, it is still displayed in the .css element. So I still think you have something blocking FontAwesome from being "fetched". What extensions are you using?

Looks like I found something. I found three different Instagram "click here to follow" web pages that only contain a description but all three of those web pages are displaying "squares". I don't have an account so that's all the futher I can get. But all three use a font for emojis called Twemoji Mozilla. Which to me wreaks of a web master that only cares how Firefox renders the emojis, but I digress. Here's a github if interested in compiling Twemoji - https://github.com/twitter/twemoji Other than that, I'm not finding a way to "install" Twemoji on XP.

Sorry, I don't have an Instagram account. So hopefully somebody else may be able to offer assistance.

But I really really really prefer my Stylus view. No "face icons". Sorry, just a "pet peeve" of mine.

As far as that "shield" font, it's a font called "FontAwesome".

For the "sheild" in the corner of Dave-H's profile pic, you have to allow external fonts from msfn.org which I block by default in NoScript. But I also block any-and-all profile pics via Stylus so I was never aware of that "square".

We kind of need a test URL to see what's going on. I don't do Instagram so have zero reference on what it is "supposed" to look like.