
NotHereToPlayGames
MemberContent Type
Profiles
Forums
Events
Everything posted by NotHereToPlayGames
-
This link is dead. I use uBlock 1.52.2 and have a couple profiles (such as at work) that run 1.59.0. I do notice that 1.52.2 "seems to be" a little faster, but I've not technically performed any quantifiable measurements outside of "never believe gut feeling placebo effects" that suggests 1.52.2 to be a little faster.
-
Another reason to hate Windows 11 (and Microsoft)
NotHereToPlayGames replied to pcalvert's topic in Windows 11
I think that was supposed to read: <font: sarcasm;>hate is childish; if it aint newest then it sucks ...</font> -
That yellow exclamation mark was introduced in version 1.48.0. I myself tend to be "impatient" at times when it comes to computers, so I myself can not trust versions prior to 1.48.0. Not because they don't work, they do, but because I tend to start clicking bookmarks or whatnot before uBO is actually "ready". So I actually like the yellow exclamation mark as a reminder that I can wait half a second before opening a bookmark.
-
I can confirm that 0.0.0.0 "works" for breaking the Google Analytics telemetry for the extension that this was discussed. I don't really have a way to "test" if this is indeed "faster" or "better" or not. But I can confirm that it "works". Personally, I still prefer the tt -> xx method. Because I like to look at my modifications six months or a year from now and with that method, my mod stands out like a sore thumb. The 0.0.0.0 would require "notes" on the side or a re-visit to the original code to see just what I mod'd out. I'm personally not convinced that hxxp is any slower than ht tps://0.0.0.0 because the browser does not know what to "do" with hxxp so the instruction is SKIPPED. The browser DOES know what to "do" with ht tps://0.0.0.0. (edit: and it appears that an "old" browser versus a "modern" browser will react DIFFERENTLY when it encounters 0.0.0.0) It would be one thing if I replaced a real DOMAIN with a will-not-resolve-at-the-DNS-level DOMAIN as that would obviously consume clock cycles and DNS lookup time. But the browser (and OS) has no clue what to "do" with hxxp://you-are-here.com and it is irrelevant if "you-are-here.com" is a real DOMAIN or not, it doesn't even get sent to the server for a DNS lookup. It doesn't even get passed through the OS hosts file for the OS to decide if it is "redirected" or not. The REDIRECTION may indeed be FASTER, but my mod doesn't require the OS to perform any host-based redirect.
-
On second thought, the CRASH if that UNINSTALL URL is "tampered with" was discussed in this very thread and you even replied to it, so I did already tell you WHY that URL cannot be "tampered with" but that PREFIXING solves the auto-visit BS.
-
Not to be misread. I wholly and fully support the author's great extension (I've tried the alternatives and greatly disprove of them, to each their own) and he is wholly and fully "allowed" to code-in "telemetric phone-home shenanigans". I am not a supporter of "time bomb" shenanigans, but do "understand" why MANY authors employ them. I equally wholly and fully support the END USER acquiring the know-how to PREVENT said "telemetric phone-home shenanigans". I personally hate hate HATE even "auto-update" BS as that is just a cleverly veiled "phone home shenanigan".
-
You missed that part of the conversation. That was discussed "before" the topic was relocated to this thread, so it's understandable that it was missed. Tampermonkey's coding is very "tricky" in places. MANY extensions employ TRICKS in an ATTEMPT to keep people from editing out the parts they don't like. That does not stop me! I find a way to edit out the BS! In the case of the UNINSTALL auto-visit BS to the D#MN HOME PAGE, if you remove the URL entirely, or even replace parts of the URL, then the GUI will not load and CRASHES. But if you PREFIX with "disabled-" as my mod does, THEN THE UNINSTALL AUTO-VISIT BS IS BROKEN, no new tab opens! But yeah, sure, a CPU cycle or two was "wasted". Sure, there are other ways to defuse the d#mn auto-visit BS upon uninstall, but my prefix-fix is a COMMON method that works in MANY extensions that code-in "you tampered with my code, I'm going to CRASH now". Again, try your advice if you don't believe mine. THIS is what happens if you "edit it out". The Tampermonkey author WANTS YOU TO VISIT HIS HOME PAGE. Without modifying an otherwise great extension, the home page is visited immediately after install, 14 days later, upon various edits resulting in a crash where those edits would not crash other extensions, upon uninstalling, within useless portions of the GUI that I also mod-out, perhaps even other areas that my useage has not ran across (if I do, rest assured, they too will be mod'd out!), et cetera. This author really does add "countless" attempts for his HOME PAGE to be auto-visited! Not on my system! We've also seen just what that HOME PAGE does to the chrome.exe process-count in Supermium.
-
No, no, no, no, no. Again for those in the back row - No, no, no, no, no! Why? Because then the browser opens a new tab when you UNINSTALL the extension! The whole POINT of that MOD is for NO TAB TO BE LAUNCHED when the extension is UNINSTALLED! Especially no PHONE-HOME tab to the HOME PAGE. But why replace the phone-home HOME PAGE URL with a EMPTY TAB URL ??? Try your advice! It launches an empty tab (with a certificate error). Again, the entire PURPOSE of that MODIFICATION is so that I can uninstall the extension WITHOUT ANY TAB AUTO-LAUNCHING. None, naughta, zero, zilch, null, zewo, nula, nol, cero! https://en.wikipedia.org/wiki/Names_for_the_number_0 Please, please, please - listen to my raving wisdom.
-
Perhaps. But not all extensions can have telemetry removed in this "simplistic" manner. More often then not, it requires tracking down a variable (ie, the *time bomb* was particularly interesting to isolate) or removing lines (plural) of javascript code. In fact, if you remove the URL below entirely or even replace the tt with xx, then Tampermonkey's GUI will not even load! For this one, replacing http with ftp may have worked just as well as prefixing with disabled-. URL("disabled-ht tps://www.tampermonkey.net/uninstall.php?ext="+rea.runtime.short_id),_t.init(()=>{Ye.finalize()}),Object(ie.init)
-
Well yes but no... The tt -> xx has been COMMON PRACTICE since the 90s. So no, I did not learn this from 360Chrome repackers. But yes, a few CPU cycles are consumed. But so are they with 0.0.0.0 ???
-
Personally, "don't care". The sky is not falling!
-
My apologies! I make so many extension mods that I (temporarily) lost track. The Google Analytics that I had to "defuse" last week was when I was testing audio EQ extensions. Since we are embarking on this journey, I'll walk through that extension's modifications. It is the EQ extension that makes a Google Analytics connection with each and every browser launch. It is this extension - https://chromewebstore.google.com/detail/ears-bass-boost-eq-any-au/nfdfiepdkbnoanddpianalelglmfooik?hl=en In manifest.json, make this mod to defuse the Google Analytics telemetry: "content_security_policy": "script-src 'self' https://ssl.google-analytics.com; object-src 'self'" "content_security_policy": "script-src 'self' hxxps://ssl.google-analytics.com; object-src 'self'" In popup.js, make this mod to defuse the Google Analytics telemetry: e.src="https://ssl.google-analytics.com/ga.js"; e.src="hxxps://ssl.google-analytics.com/ga.js";
-
How to remove Google Analytics telemetry in Tampermonkey. Also some GUI-related items of telemetric intent. First - be warned, Tampermonkey also has a "time bomb" (contribution solicitation) and a "the version you are using has been tampered with, please uninstall and reinstall from official sources" embedded 'checks' which are reported via automated visits to the "home page". So those should also be "defused" (and are in the below mods). I cite the changes for v4.13 as that is the version that I use. In extension.js, make the following mods (before line is first line, modified line is second line): },i=$('<iframe src="ht tps://www.tampermonkey.net/contrib.php?embedded=2'+(t?"&locale="+t:"")+"&src="+(e||"e")+rea.runtime.short_id+'" class="contrib_iframe"></iframe>'),s=[$('<button [IGNORE SPACE IN HTTPS] },i=$(''),s=[$('<button l=i("div","head_container","opt","head_container"),c=i("div","tv_container_fit","opt","tv_container"),A=s("a","head_link","heads","head_link");A.href="https://www.tampermonkey.net",A.target="_blank";const l=i("div","head_container","opt","head_container"),c=i("div","tv_container_fit","opt","tv_container"),A=s("a","head_link","heads","head_link");const r=i("div","head_container","ask","head_container"),o=i("div","tv_container_fit","ask","tv_container"),a=s("a","head_link","ask","head_link");a.href="https://www.tampermonkey.net",a.target="_blank";const r=i("div","head_container","ask","head_container"),o=i("div","tv_container_fit","ask","tv_container"),a=s("a","head_link","ask","head_link");const In background.js, make the following mods (before line is first line, modified line is second line): sub_menu_item:!0,pos:"bottom",items:[]};A.items.push({name:M.I18N.getMessage("Dashboard"),image:"utilities",url:rea.extension.getURL("options.html")+"#"+ sub_menu_item:!0,pos:"bottom-disabled",items:[]};A.items.push({name:M.I18N.getMessage("Dashboard"),image:"utilities",url:rea.extension.getURL("options.html")+"#"+ e;h.length?(e={name:"scripts_new",id:"scripts_new",sub_menu_item:!0,pos:"center",items:[]},s.push(e)):e=l;const e;h.length?(e={name:"scripts_new",id:"scripts_new",sub_menu_item:!0,pos:"center-disabled",items:[]},s.push(e)):e=l;const e=[],r=M.I18N.getLocale(),n={name:"commands",id:"commands",sub_menu_item:!0,pos:"left",items:[] e=[],r=M.I18N.getLocale(),n={name:"commands",id:"commands",sub_menu_item:!0,pos:"left-disabled",items:[] e=12096e5;let (this is the "time bomb", 12096e5 milliseconds = 14 days, this and the next mod are related, there are other ways to defuse, this is just what I did as the "easiest" to defuse) e=0;let r=Date.now(),n=!t.first_run||t.first_run.ts+e<r,s=!t.hide,o=!t.contributed,a=!t.later||t.later.ts+e<r;if(!Ne.RUNTIME.SAFARI&&!Ne.RUNTIME.DOLPHIN&&n&&s&&o&&a)return r=Date.now(),n=!t.first_run||t.first_run.ts+e<e,s=!t.hide,o=!t.contributed,a=!t.later||t.later.ts+e<e;if(!Ne.RUNTIME.SAFARI&&!Ne.RUNTIME.DOLPHIN&&n&&s&&o&&a)return newV:rea.extension.manifest.version,oldV:null,first_run:!1,active:!1},r=()=>{if(!kt.late)return (disables "first run" Mickey Mouse Crap, ie, disables auto-visit to home page [which has also been seen to launch a HUNDRED chrome.exe's in Supermium!]) newV:rea.extension.manifest.version,oldV:null,first_run:!1,active:!1},r=()=>{if(!kt-disabled.late)return URL("ht tps://www.tampermonkey.net/uninstall.php?ext="+rea.runtime.short_id),_t.init(()=>{Ye.finalize()}),Object(ie.init) (disables "dumb" 'why did you uninstall me' auto-visit Mickey Mouse Crap) [IGNORE SPACE IN HTTPS] URL("disabled-ht tps://www.tampermonkey.net/uninstall.php?ext="+rea.runtime.short_id),_t.init(()=>{Ye.finalize()}),Object(ie.init) In style.css, make the following mods (I wouldn't call them telemetric, I'm only including since I am listing my mods): sup{font-size:small} sup{display:none} .noborder{border-collapse:collapse;border-spacing:0;border:0}.float{float:left} .noborder{border-collapse:collapse;border-spacing:0;border:0}.float{cursor:default;float:left} .contrib_button{padding:10px;margin:0 10px} .contrib_button{display:none} .social{font-size:.5em;display:inline;vertical-align:bottom} .social{display:none} Hmm, I think that's all of my v4.13 changes. Google Analytics does not seem to be one of my v4.13 changes. Telling me that Google Analytics was added with LATER VERSIONS. One moment, I'll do a little more digging...
-
Not sure if the two are the same. Gray area. Admins/Moderators could have shut down the 360Chrome discussions (which I did not "start", I simply expanded upon and carried over to version-specific threads) at any point. None did. So fair enough. We can let the Admins/Moderators erase the next post if we "crossed the line" (it's always been a very fine line).
-
No surprise here! I'm not a fan of anything being "internal". The browser should "render" and nothing more! I'm not sure if it is "allowed" to (publicly) discuss how to break/modify Tampermonkey's telemetry. Does doing so break MSFN Forum Rules?
-
<del>
-
I guess this isn't technically accurate. 1809 does have a better Task Manager that will display GPU usage. But that is only important if you rely solely on Window's native Task Manager as I get GPU usage from System Informer 3.1.24333.0 and use it over the native Task Manager.
-
WinReducerEX100. https://forum.winreducer.net And the "base" OS is Win10 1607 (year = 2016). I do have a tweaked version of Win10 1809 (year = 2019) but it's still at trial-and-error due to a very long blank screen during cold boot. 1809 doesn't gain me anything over 1607 and I'll likely never need 1809 but would jump to 21H2 next. Only time will tell. I used XP for twenty three years. Perhaps I'm being naive, but I have my fingers crossed that I can get at least half that (call it twelve years) and sail along just fine with 1607! "Support" from Microsoft is MEANINGLESS to me. I don't even install "updates" to 1607! If it ain't broke, don't fix it!
-
My Win10 is ALREADY TWEAKED DOWN TO ONLY 27 PROCESSES !!! (the screencap shows 28 because I had to open the Task Manager process, lol) This is technically from inside a VM but my HOST is IDENTICAL. To be perfectly fair and honest and not hide anything, the process count is 29 and 31 on two laptops but this is due to sound and graphics drivers for higher resolutions than default generic drivers. This tweaked-down version of Win10 (1607) is the result of two years of trial-and-error all while still running XP as my only OS. I could NOT bring myself to migrate away from XP until I was able to get Win10 to my liking. And as one might suspect, it was web browser and billpay access HEADACHES in XP that was the "last straw". Once I did finally end up a Win10 User, I REGRET NOT DOING IT SOONER - Win10 *is* much BETTER once you tweak out the BS!
-
<excerpt> Over time I have observed that the audio quality of the PC is related to the number of processes that run on it and to the latency. We all know that Windows Server has higher quality sound than Windows 10, and in Core mode even more, and if we also run it from RAM it increases much more. These facts corroborate the above, as they are related to the number of processes that are executed in the OS while listening and with the latency, always lower in RAM. To corroborate these statements I have checked how many processes are running on each OS (clean) mentioned above, and the results are as follows: 1. WINDOWS 10: 126 processes (104 applying Windows Debloater powereshell script and disabling Windows Defender) 2. WINDOWS SERVER 2019 GUI: 104 processes (with defender installed) (87 with defender uninstalled) 3. WINDOWS SERVER 2019 CORE *: 71 processes (54 with defender uninstalled) (*) with AppCompatibility FOD installed. 4. WINDOWS 10-11 PE: 27 processes.
-
I don't think this is the correct forum. Everything within my template was obtained from here. And a ton of trial-and-error. I intentionally break/defuse/axe things like Windows Defender and Windows Firewall and Smart Screen and Action Center for the sake of PERFORMANCE over "security". I strongly feel that if I get hit with malware/virus/trojan, then it is BECAUSE I WAS STUPID AND CLICKED ON SOMETHING I SHOULD NOT HAVE, INTALLED SOMETHING I SHOULD NOT HAVE, VISITED A WEB SITE I SHOULD NOT HAVE, et cetera. I have NO INTEREST in my computer being CRIPPLED with background bottlenecks to "protect me from me". I take FULL RESPONSIBILITY and BLAME MYSELF if I click on something I should not, install something I should not, et cetera. If a new thread is started and there is enough interest, I may reconsider. But in the meantime, there are other (better [due to membership subset]) forums for discussing these types of templates.
-
I use a stripped-down version (WinReducerEx100) of 1607 on five home computers without any issues. One is an ancient quad-core (may even only be duo, would have to look), one is an i3 laptop, one is an i5 laptop, one is a single-core desktop, and one is an i7 desktop. Three of the five are used DAILY. The fourth is used at least three times a week. The single-core is for music out in the garage so is only when working in garage or in backyard. VERY practical and NO ISSUES. I don't doubt that these will not last "forever". But I envision at least FOUR TO FIVE MORE YEARS before I have to worry about anything! That's an eternity for computers already 8-16 years old.
-
Eureka! I did not originallyhave this toggled to Enabled, but doing so definitely broke Violentmonkey's ability to inject scripts! I only tried most-recent stable (non-beta) version. It does not break Tamerpermonkey's v4.13 ability to inject scripts (only tried that version because that was already present in the 360Chrome profile). Tampermonkey's most-recent stable (non-beta) version does not work (reducing min-ver in manifest will get it to install, but the GUI will not load). That's where I stopped for now... I personally PREFER Tampermonkey over Violentmonkey but BOTH are equally GREAT and only a matter of PERSONAL PREFERENCE. If the OP wants to isolate how "old" of a Tampermonkey version he must go and still be able to use the "experimental-web-platform-features", I don't mind hunting that down. We do know that version 4.13 does work! Technically, I've never had any use for any version newer but cannot recall offhand "why" I opted for v4.13. t is VERY common for me to test tons of extension versions and hand-select the version I *keep*. Which is not always "latest and greatest" but the actual "why" will vary greatly from one extension to the next.