I think chrome is intentionally providing shitty user experience for the blocking of HTTP downloads on HTTPS pages, in order to push developers to fix it faster.

you click a HTTP download link on an HTTPS page and what happens? NOTHING. No error page, no pop-up saying "BLOCKED BECAUSE SECURITY", the browser is just like "did you click? I didn't notice"
it just sticks an error in the JS console.

which I'm sure everyone notices
BTW, this is probably going to get fixed soon, but as of Version 87.0.4280.141 (which seems to be latest) there's a bug which lets you bypass the block, most of the time.

Incognito mode.
Basically chrome won't let you download it because it has the context of you clicking it from a HTTPS page.
But it loses the context if you use the "open link in incognito window" option.
The only reason this wouldn't work is if you're in incognito mode already.
Annoyingly there's only one incognito mode, you can't have incognito mode from other incognito modes.
I demand internal security between my browser windows. none of them should know about each other!
anyway it turns out this trick isn't needed after all.
You can do "save link as", it'll let you select where to save it, then it'll fail.
but it fails in a bypassable way
so you should probably do it this way, as it's less likely to be patched out soon by an angry google dev
I understand that google wants to build a more secure web but a side effect of the everything they're doing is that the web is bitrotting faster
dev1: if we change X to Y, the web will be 2% more secure
dev2: won't that break pages not made in the last 2 years?
dev1: yes. legacy pages will stop working
dev2: how will we support the old pages?
dev1: let me say this as clearly as I can
*puts mouth on the mic* FUCK THEM
chrome.exe

More from foone

More from Tech

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.

You May Also Like

Tip from the Monkey
Pangolins, September 2019 and PLA are the key to this mystery
Stay Tuned!


1. Yang


2. A jacobin capuchin dangling a flagellin pangolin on a javelin while playing a mandolin and strangling a mannequin on a paladin's palanquin, said Saladin
More to come tomorrow!


3. Yigang Tong
https://t.co/CYtqYorhzH
Archived: https://t.co/ncz5ruwE2W


4. YT Interview
Some bats & pangolins carry viruses related with SARS-CoV-2, found in SE Asia and in Yunnan, & the pangolins carrying SARS-CoV-2 related viruses were smuggled from SE Asia, so there is a possibility that SARS-CoV-2 were coming from