Jump to content

NotHereToPlayGames

Member
  • Posts

    7,484
  • Joined

  • Last visited

  • Days Won

    98
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by NotHereToPlayGames

  1. But I'm sure the biggest part of my slowdown is that I funnel through Proxomitron.
  2. The page load times are not a good comparison between "my" computer and "somebody else's" computer. BUT the page load times do give a scientific method quantitative measurement - change ONE variable (chrome.dll) and time the result of that ONE variable.
  3. YouTube loads much quicker if I actually allow the ads. Just not a very pleasant listening experience.
  4. This is the network entry that was used for all page load times.
  5. Yes. But my YouTube experience will be much different from others. A lot of delay for ad-blocking and what-not so I can listen to music ad-free while at work. The work network blocks the ad servers but YouTube will play the length of the ad anyway. So I have music, 20 seconds of silence or however long the ad was supposed to be, more music, another long delay of silence, more music. So I've had to use some ad-blocking YouTube extensions for uninterupted music throughout the day.
  6. YouTube has always been molasses-slow for me. But it also runs through two extensions to block ads, annotations, info cards, end scenes, comments, and chats. Wasn't patient enough to clear the cache and reload ten times. Player css and polymer js files take "forever" to load on my setup. Before=rebuild_2 and after=rebuild_3 ( www.youtube.com ) --
  7. After ( https://msfn.org/board/forum/201-browsers-working-on-older-nt-family-oses/ ) --
  8. Before ( https://msfn.org/board/forum/201-browsers-working-on-older-nt-family-oses/ ) --
  9. Cool! Thanks! There shouldn't be a high "frequency" of updates.
  10. I'll run these for a full week before uploading a rebuild_3.
  11. Awesome! I did get as far as removing the Translate entries. Didn't think to compare page load speeds before-and-after.
  12. The Translate feature will be broken in both the ungoogled and the regular.
  13. The "ungoogled" version does intentionally prevent that network connection unless you perform the chrome.dll modification posted here - https://msfn.org/board/topic/184135-arcticfoxienotheretoplaygames-360chrome-v135-build-2022/?do=findComment&comment=1230537
  14. Good deal. I'm "on the fence" as to whether to keep the translate feature intact or not. I myself "never" (never say never?) visit sites that need translated. And when I do, there are web-based translation sites as opposed to being "built in" to the browser. On one hand, Official Ungoogled Chromium does not have it and my goal with 360Chrome was to immitate Official Ungoogled for the most part. On the other hand, it's buried away in a context menu and makes no "connections" to Google until the user intentionally selects that context menu item.
  15. Plus, I also think that v13.5 is basically "end of the line" for 360Chrome on XP. I hear rumors of another Chrome Fork in the works that would dethrone 360Chrome if the rumors are true. Waiting to see. https://msfn.org/board/topic/184127-xp-and-future-of-web-browsing/?do=findComment&comment=1230273 edit - truth be told, 360Chrome could come out with twenty "newer builds" for v13.5, but if a web site that does NOT work in build 2022 isn't PROVEN to work on the "newer build", then I will not upgrade from build 2022. I'm not looking to be the dog chasing its tail with constant "updates".
  16. Agreed. Small "patch" .exe's (7z executables with self-contained portable HxD coupled with AutoIt) would be fairly easy but then all of the anti-virus folks would crawl out of the woodwork and cast aspersions.
  17. Instructions on how to convert the "ungoogled" to "regular" and how to restore "Translate to Engish" provided in 2nd and 3rd posts. Please note that going forward, I intend to maintain ONLY the "ungoogled". Instructions will be provided on how to "convert" the "ungoogled" for different 'flavors' but I will not be "maintaining" anything outside of "ungoogled". MSFN Members are free to assist/host/share any files they wish to assist other 360Chrome users.
  18. The font-thing is one of those things that constantly keeps coming around. Chrome/Chromium/forks do fonts WAY different than Mozilla/Firefox/forks. Took some getting used to when I finally abandoned Mozilla/Firefox/forks.
  19. Not as easy, but I used this before setting up Proxomitron to perform all of my font-based tasks. https://greasyfork.org/en/scripts/419363-%E5%85%A8%E5%B1%80%E5%BE%AE%E8%BD%AF%E9%9B%85%E9%BB%91
  20. There are 42 "gstatic" entries and I did not have to restore any of them to restore "Translate to English". I personally prefer the "err on the side of caution" approach and would keep all 42 "gstatic" and all 47 "googleapis" entries disabled. We can always isolate and "selectively restore" if some unknown feature that nobody has found in close to two years is somehow suddenly found.
  21. Confirmed. Only two of the 49 "googleapis" entries need restored in order to restore the "Translate to English" feature. Therefore, you do not need to restore Google's email service, update service, userinfo profile tracker, firebase messaging, firebase user topics, tachyon tracker, Google account manager, geolocation, Google password service, Chrome upboarding, Google nearby sharing, Google pixel langs server, Google client services, Google data saver, Google content suggestions, Google optimization guide tracker, Chrome wallet, Google fcm notifications tracker, Big Cache beacon, networktraversal, Google Alumni, Chrome Reporting, among others. You also do not need to enable the Chrome Web Store portion of the "ungoogling" (ie, the persistent Google cookie that never deletes and spans all browsing sessions).
  22. Follow-up: "Translate to English" is intentionally broken when 49 "googleapis" (without the quotes) entries are batch-replaced with 10 dots inside chrome.dll. These "can" be restored by batch-replacing any series of 10 dots with "googleapis". Technically what this also does is replace 11 dots with googleapis followed by 1 dot, replace 12 dots with googleapis followed by 2 dots, et cetera. There appears to only be TWO "googleapis" entries that pertain to "Translate to English". We should be much better off (for those that want this feature) in restoring only these TWO and not the other 47 that do not pertain to this feature. Will need to do some testing, more to follow within the next couple of days or so.
×
×
  • Create New...