exploraz
This Month in Ladybird – September 2026
Discord Status – Session Unavailability
New API endpoint provides privacy-safe star history data
Now, on desktop Firefox (private browsing mode, logged out), I see that it always links to the opaque goto URLs, instead of only overwriting on interaction.
Using Google Search while logged in on Chrome Android still presents the older non-opaque /url?... links though.
It's unfortunate that we cannot immediately inspect what the link will lead to, whether the link is the intended (and safe/expected) destination or not.
This Month in Ladybird – August 2026
It never got overwritten back to the original destination URL with the same browsing environment (see my other comment).
Tell HN: Google Search to begin using opaque redirect URLs on search results
Recently, for a couple of months, I noticed that Google Search began to replace its /url?q=<encoded url> links into a more opaque one (/goto?url=<internal identifier>) randomly (indication of A/B testing) on my logged-out private browsing sessions.The old one (intermediate link with /url?sa=...q=...) will either be presented immediately after loading the page, or after the mouse has...
Disregard. Now it's archived again
- VPN/Proxy/Datacenter IP/Tor usage
- Censorship bypass tools triggering destination server's firewall (suspicious TLS fingerprint or connection characteristics, or bad proxy IP)
- Bad ISP (e.g. one ISP IP address or range of addresses shared by so many users that could create collateral damage if one or more user gone rogue)
- Actual botnet/hidden residential proxy exit node on the same IP/local network (e.g. TV boxes or SDKs embedded inside apps that users are not aware of)
- Strict privacy settings (unlikely to cause 403 straight away), or obscure browsers (also unlikely, but can trigger firewall because of connection fingerprint/characteristics)
- Actual bad behavior (scraping, etc)
From Firefox 148 release notes for developers:[1]
> The overflow, overflow-x, and overflow-y CSS properties can now be used on replaced elements such as images, in the same way that they are used with other elements. Prior to this, replaced elements were always clipped to their bounding container. (Firefox bug 1999100).
[0]: https://news.ycombinator.com/item?id=49272986 [1]: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Rel...
LocalSend v1.18.0 and v1.18.1 Released
This Month in Ladybird – July 2026
Registration of new accounts to the Arch AUR reopened with hardened requirements
7-Zip XZ Decompression Heap-Based Buffer Overflow RCE Vulnerability
[1]: https://codeberg.org/comaps/comaps/releases/tag/v2026.07.16-...
Feature request tracking: https://codeberg.org/comaps/comaps/issues/556