NotHereToPlayGames

Minor updates reserved for next update - proxcss-menu.css >> added --->>> form input[type="checkbox"] proxcss-menu.css >> added --->>> form input[type="radio"] proxcss-menu.css >> added --->>> form input[type="radio"]:checked:before Minor-major update reserved for next update - Reverted to previous Header Top Add: Initial JS Code 19.02.23 (ccw!) [...] (d.r) ---->>>> Header Top Add: Initial JS Code w/o nonce 20.02.09 (ccw!) [...] (d.r) [add++] proxjs-full.js >> modified own modification --->>> cd = " style=\"text-decoration: line-through !important; display: inline-table;\""; proxcss-general.css >> added >> a.Pr0xCookie, span.Pr0xCookie --->>> display: inline-table;

Unsure if this practice is still prevalent or not (companies were sued over it circa 2011 (hulu?)), basically there were web sites that could "recreate" / "respawn" a DELETED cookie by using the Etag http header. This is the Proxomitron filter that us Proxomitron users were using to prevent that "respawning". I still keep this in my config but I do not have any in-the-wild examples where "respawning" is known to still be employed or not - I keep it more as an err-on-the-safe-side approach. In = TRUE Out = FALSE Key = "ETag: Always Remove 11.08.16 [jjoe] (o.0) (In) [add++]" Match = "\1&$LOG(CGET $DTM(c) : ETag removed: \1)"

Forgot to mention, and again I kinda rely on the neighbor for most of this info, not the news, but somebody that works IN THE FIELD - she claims that a large number of deaths that are reported as covid deaths were not in fact covid deaths. A gunshot victim or car crash victim would be counted among the covid numbers even if that gunshot or car crash was the "real" cause of death, but since "covid" was found in the lungs (my assumption here), then they were "counted" as a covid death. At any rate, I'm just tired of all of the BS and still have my fingers crossed that we return to "normal". I have no intention of wearing a USELESS mask for the next TWENTY YEARS all because "politicians" don't want to give up their "control" over rules we must follow but they don't think apply to them. Any whoo...

I'm no doctor, but my neighbor is. She threatened to quit her job three/four weeks ago due to a vaccine mandate that would have required she be vaccinated (she still to this day is NOT vaccinated). She's a consultation physician and to me at least it sounds like when I do jobs as a "consultant". I am exempt from "union rules" at most of the companies that I do consultant work for. The way she tells it, the only reason she was allowed to keep her job and remain UNVACCINATED is because of a Supreme Court ruling (which I have not been following). At any rate, that aside, me and my neighbor are both of the "opinion" (we acknowledge that is is "opinion" but there is "some" studies that back it up, but just as many studies that refute it, but I cannot claim to be following these studies personally, the neighbor is however and I kinda take her word for it), where was I, oh, it is my "opinion" that the folks that have died from covid were in such a state of health that they were going to die anyway, not from covid but something much less "deadly" than covid. So in my view, all of this "crap" that the US and other countries have been doing in the "guise" of 'safety' is all just BS. Opinions vary, of course. But that's mine True.

All of my BNav extenstions have an install.rdf with the following addition (please do not call it Borealis) [that is, if you are referring to Roytam's release, if you are indeed referring to the official Borealis, then yes, call it Borealis] - <!-- Borealis Navigator --> <em:targetApplication> <Description> <em:id>{a3210b97-8e8a-4737-9aa0-aa0e607640b9}</em:id> <em:minVersion>0.9.0a1</em:minVersion> <em:maxVersion>2.*</em:maxVersion> </Description> </em:targetApplication>

Minor updates reserved for next update - proxcss-menu.css >> added >> input.Pr0xMLink --->>> opacity: 1.0 !important; proxcss-menu.css >> modified >> input.Pr0xMLink --->>> margin: 0 !important; ---->>>> margin: 0 4px 0 0 !important; proxcss-menu.css >> added >> input.Pr0xM-Input --->>> border-radius: 0 !important; proxcss-general.css >> modified >> input.Pr0xBtn-Input --->>> border-color: #FFD600; ---->>>> border-color: #FFD600 !important; proxcss-general.css >> added >> input.Pr0xBtn-Input --->>> border-radius: 0 !important; proxcss-general.css >> modified >> input.Pr0xBtn-Input --->>> border-width: 1px; ---->>>> border-width: 1px !important;

In the US, there has been 73,100,000 cases and 876,000 deaths. Divide that out and that's 0.01198. So is the mortality rate 0.01198? Or 1.198? At any rate, it's not the "90%" that our media would have had you believe a year and a half ago.

Forgive me for being a bit unorthodox. But I feel that if we all went around licking each others hands and faces a year and a half ago, we would have achieved natural immunity in less than a MONTH and this thing would be over already.

No it isn't. But yeah, it's "peanuts" and not worth arguing over. While my recollection of "exact" details may be fuzzy (because it's an "issue" that only ranks right around a 4 on a 10-point scale), but it *is* an "issue" that should not just be shoved under the rug and "ignored". Google for "history of post office bailouts". But again, yeah, "peanuts" so not worth arguing.

The Post Office is a much larger waste of money, in my humble view. Between 2007 and 2020, the US Government has had to bail out (ie, taxpayer money) the Post Office pretty much each and every year to the total of $78 billion spanning those years. The Post Office is *NOT* supposed to be funded by TAXPAYER FUNDS. Let alone each and every year!

This includes incognito mode! Which to me is a gigantic PLUS

re: Just add $SET(0=a_track.i_script:0.) to the ublock filters. Please do not do it that way. That would basically break our entire reason for adding Proxomitron. All internet traffic is seen by Proxomitron before any extension sees the internet traffic. If we start creating extension rules to strip away at Proxomitron functions, then Proxomitron will not be for that user. It is fair to set up Proxomitron as a "small net to catch a few fish" or as a "wide net to catch too many fish". The i_script:0 in particular violates the very essence of intentionally using Proxomitron as a "wide net" then employing its "lists" to whitelist per user needs. If the user prefers the "small net" then i_script:0 would never be needed because that user would not be using the 7.1 Block all Scripts option.

Here I'll highlight another usage for Proxomitron. Here's an example web site to demonstrate -- https://off-guardian.org/2021/09/22/30-facts-you-need-to-know-your-covid-cribsheet/ When you open that page, there are FIFTY ONE same-domain images and SEVENTY FIVE third-party images as pointed out by uMatrix - My internet speed is pretty fast, but that's still a ton of unneeded internet traffic. Especially considering those SEVENTY FIVE gravatar images are nothing but avatar images way down at the bottom in the "comments section". Here are my three added filters to prevent these gravatar images from loading by default - but I can toggle them on by clicking the "F" (fetch) or open in a new tab/window using the "I" (image). Disregard, will post again after further testing.

I apologize if I sound a bit blunt, but I am the wrong person to ask. Browser "certificates" have been flawed ever since the "web" decided to use httpS "everywhere" instead of only on banking web sites (circa May 2000). Chrome did not start "nagging" its users that http pages are not "secure" until version 68 [July 2018]. Mozilla followed Chrome's footsteps with the "nagging" with the release of Firefox version 70 [October 2019]. Firefox did flag password fields on forms with version 46 but was not enabled by default until version 51 [January 2017, at which time Chrome also flagged password fields that where not https). But as far as blocking access based on a "padlock", that started in 2018 with Chrome and in 2019 with Firefox. I have personally always disabled these "nags" and I find the "padlock" in a web browser's address bar to be a complete and utter waste of time - so again, I apologize, but I am not the person to ask. That's not to be "misread" or "misinterpreted". I do have "blocking" means employed for "security", but that "d@mn" 'padlock' is NOT one of them. Malware web sites have GREEN PADLOCKS! [also the very reason I started telling Proxomitron users to filter HTTPS way back in 2004!]) https://www.pcmag.com/news/google-chrome-begins-flagging-all-http-pages-as-not-secure https://www.zdnet.com/article/firefox-follows-in-chromes-footsteps-and-will-mark-all-http-pages-as-not-secure/ https://nakedsecurity.sophos.com/2020/02/18/malware-and-https-a-growing-love-affair/

I can only confirm that I tried it both ways and I had to use the proxcert-MakeCert.bat step in order for the new .pem files to "work". It appears redundant, but I did try it both ways and was unsuccessful without this step. However, I may have not noticed that an exit-and-relaunch is required so I will double-check and report my findings. Update - I can confirm that the proxcert-MakeCert.bat step is required. I cannot get Mypal to accept the certificate if I skip this step. There are "cryptography" settings available but they are "over my head" and I am unsure if they would elliminate this step or not. That is correct. You may have missed one of my steps because in the uploaded files you should find that the certs.pem file was renamed to certs.pem-disabled (essentially deleting the file because Proxomitron hunts for it by name). The confusion here is that 8443 is an "internal" port (at least that seems to be the best way to explain it). The port connections for http and for https are both to be set at 8080 (just like the original Proxomitron that we all used before Proxomitron Reborn). And this 8080 should be used in your operating system or browsers proxy settings and in Proxomitron's Config Settings "http" TAB. It is only the "https" TAB in Proxomitron's Config Settings that uses 8443.

Here's another one of my favorite functions (default settings for Advanced Mode, did not verify in Standard Mode). A lot of users like to "embed" YouTube videos, especially in the What Are You Listening To? thread. Since these are contained in an "iFrame" (my default uMatrix blocks), we can now toggle them into view. Or click to open in current tab or right-click to open in new tab, window, or incongito window (my default extensions block YouTube unless I am actually on YouTube).

Here's another cool function of Proxomitron. Credit to @XPerceniol for the image. Animated gif's by default animate in an endless loop. With Proxomitron you can freeze them completely or limit their number of loops. Refresh this page and watch the below animated gif with different Proxomitron settings (do not check the Freeze when you check the Header filter for Filter GIFs [requires Web Page filter for Limit Animated GIFs]).

For a more permanent solution, add this to your Exceptions-U.txt file then have Proxomitron reload the config so that it takes effect (the keylogger remains deactivated unless you manually activate using the "timer" button) - # MSFN msfn.org/ $SET(0=a_track.i_script:0.)

ps - maybe I should add some context. I live next door (two doors down, actually) from a house that was "inherited" by three brothers/sisters TWELVE YEARS AGO and they no longer live in this state. The three kids rotate on who will take their two-week vacation and spend it at the "inheritance" sorting through JUNK. They have cleared out TWO BEDROOMS of JUNK. But the garage STILL has boxes and boxes of JUNK that they "inherited". They cannot sell the house because of all of the JUNK. And they "live in fear" of throwing away something "valuable" if they don't sort through each and every box. I see THAT and there is no way in Hades I plan on putting my own kids through that TORTURE.

But my BOTTOM LINE remains the same! Don't let your KIDS inherit a garage full of "reusable junk" that you yourself haven't touched in FORTY YEARS. That's NOT "thankless" or "cold hearted", it's just "reality". If you want YOUR stuff "reused", then do NOT hand it over to the next generation and have them sift through junk that even antique shops cannot unload!

Too funny! I literally edited my post to say "reuse" and we posted at the same time. We're on the same page, lol.

Sorry. I'm from a family of six kids. So I mispoke. "Recycle" to me is when my older brother doesn't use his bicycle anymore so I claim it as my own. How many people would have known what I was talking about if I said to "garage sale it" ? I did mean "reuse" versus "recycle".

I agree also. I did not say to put it in the dumpster. I said to recyle it Guess my point is that if it took our parents EIGHTY YEARS to collect "stuff", why put our kids in the position of having to spend MONTHS upon MONTHS of sorting through two spare bedrooms, a two-car garage with no room for a car and barely enough room for a lawnmower, and an attic of "junk" ??? I have no intention of spending TWENTY YEARS of retirement years sorting though my PARENT'S junk! Because a MONTH or so in, I'll rent a DUMPSTER because I'm not spending that "time" to sift through "collectibles" that nobody in my generation "wants". My generation is more "mobile", we tend to me "minimalists". We have our own share of "junk", don't get me wrong. But not two spare bedrooms, a two-car garage, and an attic of "stuff" that hasn't been touched for FORTY YEARS. Just calling it like I see it.

Findings like this are to be expected (we are "filtering" the web page). It's why we have bypass lists. For MSFN, I don't use any bypass lists but do use the Proxomitron Menu (click on a web page and you access it from the lower right corner). For the MSFN reply box, you can enable it this way --

Sometimes it's just "time to". I don't believe in a "throwaway society", my everyday belt is the same belt I wore in the 90s. But us Americans especially, we tend to collect a lot of "junk". I support "recycling" so most of my stuff doesn't land in a "dumpster", but sometimes "junk is junk". "Baby Boomers" are particulary bad. They are the offspring of parents that lived through the Great Depression (I knew one that put WATER on her breakfast cereal instead of MILK). Gen X'ers, Y's, Millenials - we don't want your "junk". I know far too many in my generation "saddled" with inheriting 3 bedroom houses where two of the bedrooms, the garage, and the attic is nothing but miles upon miles of JUNK. I'm not trying to sound insensitive or heartless - but do us a favor and unload your own junk and don't make us recycle it for you. Speaking colloquially, of course. You/your is not a "person", but a collective-whole. But anywhoo...