Jump to content

NotHereToPlayGames

Member
  • Posts

    5,011
  • Joined

  • Last visited

  • Days Won

    83
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by NotHereToPlayGames

  1. No offense, but not interested. I have other hobbies to attend to and have never found any significance in these types of "scans".
  2. Ah. ZERO concern here. FALSE POSITIVES with these types of scanners are a DIME A DOZEN. Go ahead and scan winPenPack or PortableApps browsers and see if they are "flagged". But like I say, ZERO concern here.
  3. Ah, here it is. The six security vendors are referring to the "Chrome 115" chrome.exe file. Still NO CLUE why MY NAME was introduced in this thread or why the Russian Repack loader was specifically being targeted. But don't care either, not interested in getting caught up in this thread.
  4. No clue what that file is in reference to. It is certainly NOT any of my distributions and definitely not the "loader" so why did my name get introduced into this ???
  5. Please share links or whatnot to these six security vendors. I will run the same scans on winPenPack and the Dixel 1030 loader and the PortableApps loader I use for Serpent 52. May prove quite interesting.
  6. The loader used for winPenPack browsers also works for 360Chrome. An example is here -- http://www.winpenpack.com/en/download.php?view.1082 We could redistribute the winPenPack loader instead of the one that we have been using. Actual users of my builds should discuss that in my own threads if they wish the project to go this route. As is, we (the actual users of my builds as opposed to people that naysay and do not use my builds) test for malware and telemetry and as @Milkinis noted, if we see signs of malware then we address it.
  7. Correct, 1030 Redux is the latest-and-greatest. Yes, there will be updates to 1030 Redux. All releases thus far (including the first 1030 Redux) use what upstream internally labels as "v9" menus. All of these are being updated to "v13" menus.
  8. Maybe more of a personal preference then a "never". Yeah, yeah, "never say never". Installing via Developer Mode breaks auto-update for those that think their extensions should auto-update (this is a pro to me, not a con, but I disable auto-update via other methods). Some (not all) extension's "internals" reference their own "ID String" (the random sequence of 32 letters) and installing them in Dev Mode changes that "ID String" so features relying on that ID are now broken and the user isn't even aware that they are broken. Though you will see the 32-letter ID String referenced in your error console. Installing via Dev Mode I guess is one thing, but running the browser with the Extensions page *always* in Dev Mode enables the browser to throw nag screens and enables built-in "triggers" coded into the browser (especially Chrome Forks, unsure on Mozilla Forks). I've also seen reports (though have not personally witnessed) that installing via Dev Mode can result in your browser DELETING YOUR EXTENSION without asking if you want it deleted - I think this occurs when you toggle out and then back into Dev Mode.
  9. 2. It appears that crx4chrome is updating all of their MV2 downloads to default to MV3. You will need to extact the .crx, delete manifest.json (which is a direct copy of manifest_v3.json), rename manifest_v2.json to manifest.json, then go into Developer Mode on the Extensions page to pack the extension. DO NOT "install" the re-packed .crx via Developer Mode. Exit Developer Mode after you repack then install via drag-and-drop. Developer Mode should only ever be used to "develop" extension, NEVER TO INSTALL THEM.
  10. The loader is "generic" and not tied to any specific build, so no worries here, lol I actually use the same "loader" on ALL of my Chromium Forks. I also have one "loader" that is used on ALL of my Mozilla Forks.
  11. Interesting. Technically, I modify ALL of my extensions (disable any phone-home shenanigans, disable any auto-update, defuse any timebombs, customize GUI, modify descriptions, remove any "donate for beer fund" frat-mentality nags, et cetera). But I don't recall any 'declarativeNetRequest' permission issue with "I Still Don't Care About Cookies". My work-version manifest.json has the below, unsure if my home-version is identical or not. <excerpt> "permissions": [ "tabs", "storage", "http://*/*", "https://*/*", "notifications", "webRequest", "webRequestBlocking", "webNavigation" ], </excerpt>
  12. I'm fairly certain that I've seen that tidbit of telemetry in Mypal 27, New Moon 27, and New Moon 28 over the years. If I recall, it also creates a file or folder in your profile with the name "telemetry" right in the name.
  13. I already know how to de-timebomb without visiting GitHub. I would advise against sharing or "teaching" how to de-timebomb here at MSFN. That would fall under the same classification as violating an Operating System's activation and MSFN is not here to violate PAID-FOR software licenses. To the best of my knowledge (I don't follow the project), but the discussed browser is planned to be pay-ware (I think that's a word). There is a market for pay-ware modern browsers on XP, so I wish the best of success to the creator. Though I add that I wish the best of success to Supermium also. And to Mypal 68. And everything else out there, lol.
  14. I thought it was Aug 1, 2024... Wait a few months and it works again... Timebomb again Aug 1, 2025... Wait a few months and it works again... Timebomb again Aug 1, 2026... "Rinse and Repeat"...
  15. Agreed, ridiculous. Though I would not classify that as "one month old" -- Firefox 52.9 was released June of 2018. 52.0 was March 2017. To a "user agent sniff", they see something FIVE AND A HALF YEARS OLD, not "one month old".
  16. I have "learned" how to politely be "passive aggressive" with people on their mobile phones. Just yesterday during my lunch break, there was a line of 6 or 7 or so folks in front of me. The two directly in front of me were two young ladies in their early 20s or so. One of the two kept lifing her mobile phone every FORTY TO FIFTY SECONDS. And yes, I timed it !!! Just to tap the screen, scroll up on her app, see NO NEW POSTS, then flick the screen off and drop it to her waist. Only to REPEAT another FORTY TO FIFTY SECONDS later. See NO NEW POSTS. Then flick the screen off again. She repeated that BS for SIX MINUTES. And yes, I timed it !!! I laughed at her and she smiled and grinned and asked what was so funny. I politely chimed, "Do you see that thing as an ADDICTION, like any DRUG that RUINS people's lives?" She chuckled and nodded agreeingly and she never looked at the screen again for at least FOUR more minutes as we hit the front of the line. I could all but SEE the sweat rolling from her forehead, WANTING to lift that d#mn thing every FORTY TO FIFTY SECONDS but AFRAID to because the person standing in line behind her just told her she is no different than a DRUG ADDICT.
  17. Agreed! I've been of the same thought for the past couple of years. I heavily modify my Serpent 52 and the ability to modify-to-liking 360Chrome is why I don't see myself ditching either it or Serpent 52 for a very long time. I have dipped my toe into Mypal 68 also, but I haven't fully vetted it yet in comparison to Serpent 52.
  18. You need to polyfill the Object.hasOwn function. // ==UserScript== // @name Inject Object.hasOwn() Polyfill [93] // @version 0.0.1 // @match *://*/* // @run-at document-start // @grant none // ==/UserScript== if (!Object.hasOwn) { Object.defineProperty(Object, "hasOwn", { value: function (object, property) { if (object == null) { throw new TypeError("Cannot convert undefined or null to object") } return Object.prototype.hasOwnProperty.call(Object(object), property) }, configurable: true, enumerable: false, writable: true }) }
  19. I'd suspect nullish coalescing operators at equally.ai also. This is actually quite clever, if you ask me. Use nullish coalescing operators in your "cookie consent" javascript so that people using browsers that do not support nullish coalescing operators "think" they are setting a cookie-consent setting but in fact are not.
  20. Ah, your original post sited equalli.ai and so I only hunted for that within the trendmicro scripts and of course did not find equalli.ai with an "i" versus with a "y". Already at work now so don't have my "utilities" at hand.
  21. That's what it is, the trendmicro site is using "hundreds" of nullish coalescing operators (??) that Firefox 52.9 does not support! Which is also to me the PERFECT EXAMPLE of WHY some of us INTENTIONALLY like to use OLDER BROWSERS and dislike the constant thumping of "why are you using Browser X, it's already 3 months old"
×
×
  • Create New...