Claude Opus 5.5 Adds method (XRPC NSID), userAgent, origin and iat (token issue time) to the entryway session auth_verifier_request log, to identify which clients use entryway session tokens. iat i...

Google's latest thing is starting to use @container in several places including search results. We don't have support for it yet. Because of course they would try to continue to push for their latest extensions in their core service. Maybe it's time for another site-specific useragent override? * * *

Pull request (MERGED) · PR #5889 bsky: log client info for entryway sessions · @rafaeleyng Claude Opus 5.5 Adds method (XRPC NSID), userAgent , origin and iat (token issue time) to the entryway session auth_verifier_request log, to identify which clients use entryway session tokens. iat is read from the token claims, so on failure it is unverified. Ouvrir sur GitHub →

Site owners trusting user-agent headers can't spot impostors, and Google signs only some Google-Agent requests. Could a bot reputation system close that gap?

Site owners trusting user-agent headers can't spot impostors, and Google signs only some Google-Agent requests. Could a bot reputation system close that gap?

Oh, so all I had to do was add new string preferences. It works perfectly. Thank you. about:config general.oscpu.override = Windows NT 10.0; Win64; x64 network.http.useragent.global_override = Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:158.0) Gecko/20100101 Firefox/158.0 * * *

Hello, I am using the Basilisk browser on Windows 7 due to certain circumstances. However, I would like to modify some of the OS-specific information exposed by the browser, particularly to hide the fact that I am using Windows 7. Specifically, I would like to override the following values: **Navigator Object — userAgent** `Mozilla/5.0 (Windows NT 6.1; rv:140.0) Gecko/20100101 Goanna/6.9 Firefox/140.0 Basilisk/20260922` **oscpu** `Windows NT 6.1` Is there any way to override or spoof these values in Basilisk? In Firefox 115 ESR, I can modify these values using preferences such as `general.oscpu.override`, but I have not been able to find a way to do the same in Basilisk. I would greatly appreciate any advice or guidance you could provide. Thank you in advance for your time and assistance. * * *

I believe this has been discussed many times here - did you use the forum search function to search for something like "global user agent override"? For example, https://forum.palemoon.org/viewtopic.ph ... 0cb172719d and https://forum.palemoon.org/viewtopic.ph ... 9&start=20 are two discussion threads that have covered this ground. * * *

> An alternative approach also does exist. > > For different browsers Google returns Search results pages of different designs. And its choice depends on a "useragent" request header. For example, Iceape by default uses general.useragent.override.google.com = Mozilla/5.0 (%OS_SLICE% rv:71.0) Gecko/20100101 Firefox/71.0 Basilisk/52.9.20260924, and in this case Google returns pages with links that contain plain text URLs ... I don't think it will be long before Google will have finished implementing "goto" URLs everywhere, without exception: > Google has confirmed it is rolling out new “technical measures” to protect against abuse of its search results and protect its services. Google is rolling out the addition of goto URL parameter redirects to the links in its search results. > > What Google said. A Google spokesperson told us: > > “We have a long history of deploying technical measures against evolving forms of abuse, and we regularly take steps to protect our services and users.” https://searchengineland.com/google-confirms-deploying-goto-url-redirects-to-search-results-links-485926 > Rollout timeline > > The change built up over roughly four months instead of appearing all at once. Early reports were inconsistent. Some testers saw goto links right away while others couldn't reproduce them on the same day. That pattern usually points to a staged rollout, split by IP type or account signals, rather than a single global switch. > > • June 23, 2026: Alex Greenland posts the first public sighting of the goto link format on X. > • July 2, 2026: Brodie Clark documents the pattern across organic and paid listings on SERP Alert, and notes Ahrefs picking up the same pattern in its own tracking. > • Early August 2026: The pattern becomes widely visible across search results, according to Nozzle. > • August 26, 2026: Derek Perkins reports near full rollout across residential IP providers, and Google confirms the change to Search Engine Roundtable. > > Through most of the test window, the share of affected pages stayed low enough for tools like Nozzle to simply discard goto-only pages and refetch them. By August 26, that workaround stopped working, because most pages coming back were goto pages. https://decodo.com/blog/google-goto-redirect-links * * *

> For different browsers Google returns Search results pages of different designs. And its choice depends on a "useragent" request header. For example, Iceape by default uses general.useragent.override.google.com = Mozilla/5.0 (%OS_SLICE% rv:71.0) Gecko/20100101 Firefox/71.0 Basilisk/52.9.20260924, and in this case Google returns pages with links that contain plain text URLs: I tried this extension when it was first released, but PM gave me the plain URL (via q=); went to try it in a new Basilisk profile, but I was getting direct links; few days later they're now giving goto URLs. Tried the above agent in the new Basilisk profile, but still got encrypted links (not goto, but still url=CAES...). Rather than the extension, I use a userscript to convert them automatically. CODE: // ==UserScript==// @name Direct Google// @namespace http://userscripts.org/users/92143// @version 3.1// @description Follows Google goto URLs.// @include /^https?\:\/\/(www|news|maps|docs|cse|encrypted)\.google\./// @author zanetu, adoxa// @license GPL version 2 or any later version; http://www.gnu.org/licenses/gpl-2.0.txt// @grant none// @run-at document-end// ==/UserScript==// 2026-08-27: The original script stopped working, this is basically a rewrite.// 2206-09-09: Didn't last long, URLs have been removed.// 2026-09-20: Remove jQuery (wanted to follow goto URLs, but doesn't look possible without really following it).// 2026-09-29: Fetch "data-sb", which has the URL without redirecting (thanks to tellu-white).function modifyGoogle() {document.querySelectorAll('a[data-sb]').forEach(async function(a) {let url = a.getAttribute('data-sb')// Removing this prevents a listener modifying it.a.removeAttribute('data-sb')if (url.includes("uoh=2")) {let response = await fetch(url)if (response.ok) {let body = await response.text()let redirectUrl = /Url=('.*?')/.exec(body)if (redirectUrl) {a.href = eval(redirectUrl[1]) }}}})}var observer = new window.MutationObserver(function(mutations) {modifyGoogle()})//tiny delay needed for firefoxsetTimeout(function() {observer.observe(document.body, {childList: true, subtree: true})modifyGoogle()}, 100) (Initially the original URLs were still included within JSON data, that's what didn't last long.) * * *

> Considering everything mentioned above, I made an add-on that replaces all the "goto" URLs on the page with the actual URLs. To achieve this, an additional "request" is required for each "goto" URL on the Google Search results page. An alternative approach also does exist. For different browsers Google returns Search results pages of different designs. And its choice depends on a "useragent" request header. For example, Iceape by default uses general.useragent.override.google.com = Mozilla/5.0 (%OS_SLICE% rv:71.0) Gecko/20100101 Firefox/71.0 Basilisk/52.9.20260924, and in this case Google returns pages with links that contain plain text URLs: So **Redirect Bypasser** (and a lot of similar extensions) easily extracts real URLs without sending any requests: The only drawback is absence of reverse image search button on the page. (But perhaps Google will provide it for some other user agent string - still with plain text URLs.) * * *