Leaderboard

The best way to manage your user agent is the extension UserAgent-Switcher and Manager which I recommend and use myself. You can get it here: https://chromewebstore.google.com/detail/user-agent-switcher-and-m/bhchdcejhohfmigjafbampogmaanbfkg You can use this extension in different modes. One is the Black-List Mode: Apply the custom user-agent string to all tabs except the tabs with the following top-level hostnames (comma-separated list of hostnames). Note that even if a window-based user-agent string is set from the toolbar popup, your browser's default user-agent string is used. Another is the White-List Mode: Only apply the custom user-agent string to the tabs with following top-level hostnames. Note that if a window-based user-agent string is set from the toolbar popup, this user-agent will overwrite the global one. The mode that corresponds to your desires is the White-List Mode. Just enter there the domain of Google Drive. Here is a screenshot: And here is the toolbar pop-up window where you enter the mobile user agent string: Greetings from Germany, AstroSkipper

TLS 1.3 update for my older browsers: NewMoon 26 for Win2000: http://o.rthost.win/gpc/files1.rt/palemoon-26.5.0-20240601.win2000.7z K-Meleon 74 Goanna 2.2: http://o.rthost.win/gpc/files1.rt/KM74-g22-20240601.win2000.7z Retrozilla (suite): http://o.rthost.win/gpc/files1.rt/retrozilla-suite-tls13-20240526.7z Retrozilla browser (rzbrowser): http://o.rthost.win/gpc/files1.rt/rzbrowser-tls13-20240526.7z K-Meleon 1.5.4: http://o.rthost.win/gpc/files1.rt/K-Meleon1.5.4en-US.tls13.7z TLS 1.3 update files for Netscape 9: http://o.rthost.win/gpc/files1.rt/ns9-nss-update-tls13.7z TLS 1.3 update files for Firefox 1.0 - 1.5 and K-Meleon 0.8 - 1.1.6: http://o.rthost.win/gpc/files1.rt/VC6-nss-update-tls13.7z Classilla 9.3.3/9.3.4b suite: ^ http://o.rthost.win/gpc/files1.rt/classilla-9.3.3-win32-tls13.7z Phoenix 0.5 with Classilla 9.3.3/9.3.4b changes: ^ http://o.rthost.win/gpc/files1.rt/phoenix-0.5-cl933-tls13.7z ^ also comes with fixes for running under Win9x/FAT, also fixed some crashes in updated archive.

At the moment, I am testing again, but now deeply, the hardware acceleration in Thorium on my old machine equipped with the NVIDIA GeForce 6200 graphic card. And I was indeed able to enable the hardware acceleration in Thorium using both flags --use-angle=d3d9 and --ignore-gpu-blocklist. Incredibly, this mode actually still runs with my old card, and the pages load umpteen times faster than before. However, I can't run hardware accelerated canvas and rasterization together, because then undesirable side effects occur, and everything loads extremely slowly. It's a rather complicated matter of setting up and involves a lot of tests.

I have not tested that one in ages. I do know that not all User Agent extensions really work. There are SEVERAL ways that web sites can detect your User Agent. JavaScript, HTML Header, ClientHint, et cetera. Some extensions can spoof the HTML Header but do NOTHING for ClientHint. Et cetera.

... Would you be so kind as to enlighten me/us towards that very goal? I have a vested interest myself into making this work in latest Th/Sm (Chromium-122 based), but: Google have long ago removed any CH-related flags from within "chrome://flags/"; I am aware of the "--disable-features=UserAgentClientHint" command line argument, but it appears it no longer works for Chrome 122 ... That same flag currently works as expected with KafanMiniBrowser (Chromium 87 based), which had a "draft" CH implementation; I used the test site: https://user-agent-client-hints.glitch.me/ and KMB indeed leaks its Chromium version (87) through CH: But launched with "--disable-features=UserAgentClientHint" it doesn't: OTOH, latest Thorium 122 (.169) 32-bit SSE3 with the same cmdline argument continues to leak its Chromium version (122): This is rather unfortunate because at least one of my UA-spoofing extensions (Custom UserAgent String v0.2.3) in Th122 fails to work properly on some sites (which take into account the Chrome version sent via CH and not the one via the "classic" UA-string spoofed by the extension) ... I'm not entirely sure, but I think the "flag" used to work with Supermium 121, but now it doesn't with either Th/Sm 122 ... If anyone can come up with a tested/working solution for these, please chime in (FWIW, a cursory web search on Google did not produce a way to fully disable ClientHint in recent Google Chrome versions ) ...

Good! Just don't forget to disable client hints and their persistent storage in flags. Modern sites are smart enough to see through your spoofed UA.

I had written about user agent hacks ages ago' all can be found at my account, people just don't listen, hopefully they will listen to @AstroSkipper. Another important hack is OS bitness in user agent, always choose 32 bit OS. esp. if you're on XP 32 bit! Youtube (and the such) will serve less scripts for 32 bit OS.

So, after some deeper tests, I found the reason why Google Drive didn't crash for me in my fully configured profile. In this profile, I use by default a mobile user agent. The mobile view of Google Drive runs without any crashes and very fast. Therefore, I didn't observe any problems there. Here is my mobile user agent string: Mozilla/5.0 (Linux; Android 9; Tablet) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.6261.168 Mobile Safari/537.36. It can be used as a temporary or general (as Google Drive is much smoother then ) solution until the bug is fixed in the legacy build, too.

Ok. The next time when I am at my XP machine I will test Google Drive on a clean profile but with the most recent Chrome XP API Adapter. Without this updated adapter, Thorium does not run well and would overtax my patience. Maybe then, I'll finally get the long-awaited crash. Ok. On a clean profile without any further flags but with the most recent Chrome XP API Adapter, I finally get the long-awaited crash. So, you are absolutely right, the Thorium version SSE2 122.0.6261.169 WINXP 32-bit was not fixed in terms of the Google Drive bug.

Ok. The next time when I am at my XP machine I will test Google Drive on a clean profile but with the most recent Chrome XP API Adapter. Without this updated adapter, Thorium does not run well and would overtax my patience. Maybe then, I'll finally get the long-awaited crash.

No. On my fully configured profile with tons of flags. I have disabled many features I do not need and to run Thorium more smoothly. Without these configurations, Thorium does not run smoothly on my ancient machine. The main problem on my computer is the page loading behaviour of Thorium which is now bearable and ok for me after all these endless configurations.

https://github.com/Alex313031/thorium-legacy/issues/62 The issue was closed, but it wasn't solved in legacy build. As I already mentioned, I am running the Thorium version SSE2 122.0.6261.169 WINXP 32-bit. If this legacy build was not fixed, why does Google Drive work in my installation then? When I tested it, I could log into my account and access my files without any crashes.

oh yeah I do have KEx in my 98SE, tried disabling it/setting to 98/2000/XP doesn't help and it shows mozilla suite UI with some javascript errors, looks like some APIs are failing. EDIT: tried on a 95 RTM, and its debug output shows something goes wrong in pref loading, while WinAPI is fine. EDIT2: hmm, some files are missed in the list? maybe the loop filtered it out? EDIT3: case matters! EDIT4: yeah, fixed! https://github.com/roytam1/classilla/commit/548fe35db04444e6c90fe7dffb5f4cf62811347d

Sorry to hear that. Back in the day was advised against laptops, notebooks and so on 'cause they're difficult to repair. Never had anything like that, though today's mobile phones are almost there. I must admit everything small, thin and mobile makes me suspicious. I feel that they're designed so we can't detach from the device. I already sound like a conspiracy theorist.

For me, the Google Drive website works in my Thorium installation but @UCyborg reported crashes with this website. Maybe, using some Chrome flags might help you. As we both already stated, trial and error is the game. And you can report this problem in Thorium's issues on GitHub to inform the developer.

Today, the Chrome XP API Adapter has been updated to version 1.2.0.5059. I installed it and did not add the two flags in terms of hardware acceleration. That works for my old machine.

The new version of that "Modern Kyber Cipher" is broken, again. https://msfn.org/board/topic/186243-beware-new-quic-kyber768-quantum-resistant-mechanism-is-broken-workaround-to-disable-it-in-chrome-124

"Kyber (Quantum-Resistant Mechanism) in Chrome 124 Leads to Web Connection Problems" by Luke Jones "Impact on Connectivity and Responses The introduction of the Kyber768 quantum-resistant key agreement algorithm, intended for TLS 1.3 and QUIC connections, has inadvertently caused connectivity issues. System administrators have reported on Reddit and other platforms that web applications, firewalls, and servers are dropping connections following the ClientHello TLS handshake." "To address these connectivity problems, Google has provided a temporary workaround. Users experiencing issues can disable the TLS 1.3 hybridized Kyber support in Chrome by adjusting the browser's flags. Similarly, administrators have the option to disable the PostQuantumKeyAgreementEnabled policy." Source: https://winbuzzer.com/2024/05/02/google-chrome-124-launches-with-quantum-resistant-encryption-causes-connectivity-issues-xcxwbn/

OK! Thank you for your time.

That's not applicable to this precise case when @AstroSkipper is going to download that WHQL driver directly from Microsoft website to check if it helps with the browser, and it had been written and explained in the previous replies. Are you trying to imply it can be tampered on by the evil hackers on-the-fly, during the download?

I don't know, either. Trial and error is the only method to gain clarity. But I assume it won't do anything in terms of hardware acceleration in Thorium when it comes to my acient NVIDIA Geforce 6200.

And what I meant is, if a driver is WHQL, it can't be unofficial, esp. since Microsoft gives that stamp. With WHQL you can be sure it wasn't tampered. I don't know how much it will help with browser acceleration on that old card though.

trice

Thanks again for your assessment! What I actually meant was the fact that NVIDIA does not offer the driver version 307.90 but 307.83 as the latest version for the Geforce series 6. Generally, I am very careful when it comes to updating graphics card drivers in my very old system, as I have had some very unpleasant experiences in the past. But I will create a current image of my system and then test the version 307.90 offered by Microsoft.

Just a small note. Due to the circumstance that the hardware acceleration does not work properly on my old machine, I have reverted my Chrome XP API Adapter from version 1.2.0.5058 to version 1.2.0.5057 which now runs smoothly again on my machine.

You're welcome! Glad it finally works for you. TBH, your hardware is much more recent and powerful than mine. Therefore, I couldn't imagine that Thorium does not run on your system at all, but does on my ancient box from 2000. The manual execution of the command I posted for you is actually just a test whether the Thorium browser can be started in your system at all or not. I observed in my installation that from time to time the execution of the batch file didn't do anything for whatever reason. Thus, I modified the code of this batch starter file and compiled it to an EXE file which now runs reliably without any problems. BTW, I brought your comment here as a deeper discussion would have been off-topic in @roytam1's browser thread. This thread here is a better place to get help in terms of Thorium related stuff and discuss its issues.

Seeing pure white 255 means your brightness is at max. You need to look at other colours, like you successfully did with grey. Compare black levels.

You already did, it broke WebGL for you (and me). I get million errors in chrome://gpu, Google Street View is useless as nothing renders at all. Old dev build of Chromium 39 is fine, at least old WebGL games work and are playable, HexGL, QuakeJS etc. Forgot to try forcing OpenGL, doesn't work in old Chromium here and I guess it's a long shot with these hacks as well, but OpenGL is the only way to access full potential of DX 10.1+ GPUs on XP, at least in theory. There is improvement in CSS animations, eg. the ones on this site on people's profiles, where you can click the big picture and it expands, it was very choppy before, now they're smooth. YouTube is better, at least you can tell 720p@60FPS from 720p@30FPS, still some frame drops, maybe it's just due to overhead as XP lacks desktop composition. NVIDIA drivers for XP never inspired confidence in my experience, so who knows much they are or aren't a factor.

But the fonts aren't sharp. They are smudged.

There's a documented difference with grey colour and its shades at github and by you here (thanks!). For me, the problem is with colours being too light, like on that first screenshot. I run Vista without exkernel.

Thank you, very helpful! members must take example from you!

Trine

tride

Cruck (British Hooch) "The English midlands boast the best examples of these ancient structures (Brown, R. J, 1986, p67)." https://edwinwestwell.wixsite.com/timberconstruction/cruck-frame-construction#:~:text=Cruck buildings would need at least

Busted, you're lost, you need to pick up from the last word. Names used in English countries are valid words.

track

You'll notice when/if SAB reimplements taskbar.

Have you tried with istilldontcareaboutcookies-1.1.1? They are community run, and (they say) answer to requests. It works better (more comprehensively) than the old idontcareaboutcookies. Cheers @Sampei.Nihira, and thanks for continuing to share your knowledge with us, retired and all. Don't mind them digital flies.

There is a red arrow pointing to where the quotes mentioned are being used. Try to be more reasonable on the forum. We make everyone post in English and people from other countries may not be 100% accurate and clear when they post, so it is to be expected that sometimes things can get mixed up. You have the ability to figure out what a person is trying to say, there is no reason to try to catch people in a grammar trap.