Francois Marier

@bridiver I assume the test plan is something like this? 1. `mkdir src/brave/third_party/new_stuff` 2. `touch src/brave/third_party/new_stuff/file.cc` 3. `npm run build`

> There's also #248 which we could address now I think (although I'm not familiar with the details). Yeah, I'm not too sure exactly where that should be addressed in...

> If I understand the proposal correctly, this would have the effect of disabling meaningful access controls for resources that .onion pages wish to access. That's a good point. It...

I'm happy to file implementation bugs and work on the tests, but before that, I'd like to know whether that's a change that Chrome and Firefox (others?) would be willing...

> making sure this would be on track to become a part of the interoperable web Yes and trying to see whether there's agreement on the correct way to handle...

> whether this should be optional somehow or conditional upon .onion support On this specific point, I would suggest the answer is no, it should be always ON because there's...

I have no idea where GNOME Software Center pulls that data from, but if this is something that can be fixed in the Debian package (which I maintain), let me...

I tried to fix this in the Debian package by [fixing up the metadata](https://salsa.debian.org/debian/workrave/-/blob/master/debian/patches/appdata-fixes.patch) and [moving it to the right package](https://salsa.debian.org/debian/workrave/-/commit/57d7155b395ccb2c33a4cc2d25eaf098cf9565ff), but it looks like GNOME Software is pulling the...

That's no longer possible with WebExtensions, unless a new API specifically for this is added to Firefox.

Here's the output on my machine: ``` $ ./ssl-cert-check -v tls1_1 -s fmarier.org -p 443 Host Status Expires Days ----------------------------------------------- ------------ ------------ ---- ERROR: The file named /var/tmp/cert.tp0w2W is unreadable...