Tech companies and their executives have, broadly, moved to align
themselves with investors and adopted a posture of, often, disdain or outright hostility towards their users and employees. If tech
companies don't value you, why provide value to them? If they back
political positions hostile to your interests, why not return that
hostility?
On 2026-10-18, Ben Collver <[email protected]> wrote:
Tech companies and their executives have, broadly, moved to align
themselves with investors and adopted a posture of, often, disdain or
outright hostility towards their users and employees. If tech
companies don't value you, why provide value to them? If they back
political positions hostile to your interests, why not return that
hostility?
I like this. The list is missing one additional one: tax the rich.
Become Worthless (To Tech Companies)
====================================
Phone number? 321 is a valid area code. Throw it and seven other
digits in.
Don't need the account long term? Delete it.
What I propose is: "Eat the rich."
In line with the OP's thought...
Google has for a long time constructed URLs that it returns in response
to web search queries such that the organic URL of the response is
proxied back through Google with the organic URL as data. There have
been various work-arounds for those who don't want to have their clicks tracked.
Some of those work-arounds were imparied when Google compelled use of javascript in the browser to submit a search request.
Now search results are still similarly constructed, proxying clicks
back through Google. But now the organic URL appears to be encrypted.
Does anyone have any info on decrypting or unpacking the organic URL
that Google now includes as data in a search result?
Example of proxy reply from Google, line-broken to clarify the
encrypted URL:
https://www.google.ca/url?esrc=s&opi=89978449&q=&rct=j&sa=U&uoh=3&
url=CAESnQEB6zswFTVHLEl_-9MfBAUFxVDh7vBblfrqajsDFqzRmBxg9KmzK2dtjP_vwqmvNoQLo9TMHp9417vOUBjwoPP6TTqOeCLB-u07AwLAWheT2dAArNWjPHeGuXWxwYdnqwcBCuoLrk7lNyrD82tYgnAN7wa2Z1dmhwdjxL3DW-rTDQzz5ZkzbSPMXO3yP5FN8728kFG5qKr4GW0kUuVi
&ved=2ahUKEwj13-um8seXAxVwNoYAHbuRGTsQFnoECBgQAg&usg=AOvVaw2vcoO0YKYuaoWx3jYRnSLy
On 2026-10-20, Mike Spencer wrote:
In line with the OP's thought...
Google has for a long time constructed URLs that it returns in response
to web search queries such that the organic URL of the response is
proxied back through Google with the organic URL as data. There have
been various work-arounds for those who don't want to have their clicks
tracked.
Some of those work-arounds were imparied when Google compelled use of
javascript in the browser to submit a search request.
Now search results are still similarly constructed, proxying clicks
back through Google. But now the organic URL appears to be encrypted.
Does anyone have any info on decrypting or unpacking the organic URL
that Google now includes as data in a search result?
Example of proxy reply from Google, line-broken to clarify the
encrypted URL:
https://www.google.ca/url?esrc=s&opi=89978449&q=&rct=j&sa=U&uoh=3&
url=CAESnQEB6zswFTVHLEl_-9MfBAUFxVDh7vBblfrqajsDFqzRmBxg9KmzK2dtjP_vwqmvNoQLo9TMHp9417vOUBjwoPP6TTqOeCLB-u07AwLAWheT2dAArNWjPHeGuXWxwYdnqwcBCuoLrk7lNyrD82tYgnAN7wa2Z1dmhwdjxL3DW-rTDQzz5ZkzbSPMXO3yP5FN8728kFG5qKr4GW0kUuVi
&ved=2ahUKEwj13-um8seXAxVwNoYAHbuRGTsQFnoECBgQAg&usg=AOvVaw2vcoO0YKYuaoWx3jYRnSLy
I have no helpful answer to this, but there's one relevant observation:
it's not just the URL that is being encoded, if it even is being encoded
at all (it might be server-side this time?). Reloading a search page generates a *different* URL parameter for the same target.
*Sigh*. NoScript used to come with a surrogate for Google Web Search to handle this, but yeah, it'd have to be decodable client-side. But maybe
it actually is, and this is just some additional timing or request-based information that's being included there...
Mike Spencer might want to investigate did the Surfraw persons produce something which he wants.
"Surfraw provides a fast unix command line interface to a variety of pop‐
ular WWW search engines and other artifacts of power. It reclaims
google, altavista, dejanews, [. . .] and
many others from the false‐prophet, pox‐infested heathen lands of html‐
forms, placing these wonders where they belong, deep in unix heartland,
as god loving extensions to the shell."
says
info surfraw
(S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
Nuno Silva <[email protected]d> writes:
On 2026-10-20, Mike Spencer wrote:
In line with the OP's thought...
Google has for a long time constructed URLs that it returns in response
to web search queries such that the organic URL of the response is
proxied back through Google with the organic URL as data. There have
been various work-arounds for those who don't want to have their clicks
tracked.
Some of those work-arounds were imparied when Google compelled use of
javascript in the browser to submit a search request.
Now search results are still similarly constructed, proxying clicks
back through Google. But now the organic URL appears to be encrypted.
Does anyone have any info on decrypting or unpacking the organic URL
that Google now includes as data in a search result?
Example of proxy reply from Google, line-broken to clarify the
encrypted URL:
https://www.google.ca/url?esrc=s&opi=89978449&q=&rct=j&sa=U&uoh=3&
url=CAESnQEB6zswFTVHLEl_-9MfBAUFxVDh7vBblfrqajsDFqzRmBxg9KmzK2dtjP_vwqmvNoQLo9TMHp9417vOUBjwoPP6TTqOeCLB-u07AwLAWheT2dAArNWjPHeGuXWxwYdnqwcBCuoLrk7lNyrD82tYgnAN7wa2Z1dmhwdjxL3DW-rTDQzz5ZkzbSPMXO3yP5FN8728kFG5qKr4GW0kUuVi
&ved=2ahUKEwj13-um8seXAxVwNoYAHbuRGTsQFnoECBgQAg&usg=AOvVaw2vcoO0YKYuaoWx3jYRnSLy
I have no helpful answer to this, but there's one relevant observation:
it's not just the URL that is being encoded, if it even is being encoded
at all (it might be server-side this time?). Reloading a search page
generates a *different* URL parameter for the same target.
I hadn't got as far as nticing that. I suppose it would be too much
to hope that one of the other data objects in the full URL (ved=...,
opi=... etc) is a one-time key.
*Sigh*. NoScript used to come with a surrogate for Google Web Search to
handle this, but yeah, it'd have to be decodable client-side. But maybe
it actually is, and this is just some additional timing or request-based
information that's being included there...
Thanks for the reply. Where an I go to look for adversarial gwgle
hackers? Google has morphed from friend to adversary.
I never use Surfraw. Its manpage makes it sound as if it is written by persons who could dislike Google but who insist on using Google (!),
so maybe a new version of Surfraw or a new project by the same persons
might be an alternative to simply not using a Google search engine
(which, frankly is an obvious choice if one does not like a Google
search engine). It seems that many persons use Google. Cf. e.g. HTTP://Gloucester.Insomnia247.NL/claran_de_fhrithealaiche-lin/deanta_air_an_2026-10-12/dar_le_rmagic/reports/REFSITE.html
(S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,142 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 94:08:04 |
| Calls: | 14,704 |
| Calls today: | 2 |
| Files: | 186,497 |
| D/L today: |
2,661 files (886M bytes) |
| Messages: | 2,551,683 |