johnp_

> URL-safe-base64

And make sure to specify what exactly you mean by that. base64url-encoding is incompatible with base64+urlencoding in ~3% of cases, which is easily missed during development, but will surely happen in production.

Looks like Mozilla is currently working on implementing `sendmmsg` and `recvmmsg` use in neqo (Mozilla's QUIC implementation) [1].

[1] https://github.com/mozilla/neqo/issues/1693

Here's the code, for those interested in finding the bug: https://github.com/mozilla-mobile/firefox-ios/tree/main/Brow...

It says in the article

> Seabed 2030 is a long-term mapping project attempting to fully chart the seafloor and reveal all features 100 meters or larger by 2030.

There is an area of interest, "Area 3: Indian Ocean: Ninetyeast Ridge" around 30S 87E, which specifically mentions MH370:

https://seabed2030.org/wp-content/uploads/2023/06/AtlanticIn...

Though that is quite a bit (~830 km / ~1250 km from the center of the square around 30S 87E) off to the (north)west of the most recent search proposal from mh370search.com:

https://www.mh370search.com/2024/03/16/mh370-a-new-hope/

edit: Got the distance wrong. Corrected.

Oh, indeed, that's quite surprising. A TLSv1.3 Client Hello always contains the supported_versions extension, which should allow wireshark to label it correctly, regardless of whether or not the handshake actually finishes. Though, tbf, it does say TLSv1 and not TLSv1.0. I wonder how it would look had TLSv1.3 been named TLSv2.0 after all...

edit: Ah, that GitLab link lead me to https://gitlab.com/wireshark/wireshark/-/issues/19515 which is a recent discussion around this topic and https://gitlab.com/wireshark/wireshark/-/merge_requests/1377... already dealt with it :)

Certainly weird that wireshark shows TLSv1 while curl shows TLSv1.3. That shouldn't happen unless something interfered with the Client Hello. (or the wireshark version is outdated)

linux-firmware does not carry any microcode update for Renoir (yet). Or what do you mean by "TFA"?

The fixed Renoir microcode should have revision >= 0x0860010b as per the kernel: https://github.com/torvalds/linux/commit/522b1d69219d8f08317...

> and if

Do you mean the obvious `sudo snap set system refresh.hold="$(date --date=+100years +%Y-%m-%dT%H:%M:%S%:z)"`? (no error)

edit: Ah, that silently stops working after 60 days, nvm.

That's why there's OCSP stapling and OCSP must staple. Ever seen an nginx server fail HTTPS connection exactly once after rotating the certificate? That's nginx lazily fetching the OCSP response from upstream for stapling purposes.

Here's the spec:

https://html.spec.whatwg.org/multipage/input.html#attr-input...

> Authors are encouraged to specify both any MIME types and any corresponding extensions when looking for data in a specific format.

> User agents should prevent the user from selecting files that are not accepted by one (or more) of these tokens.

Besides all the points other people already made, the money saved by being able to switch to deploying the Starlink constellation via SuperHeavy/Starship (very likely to be cheaper in $ per satellite-to-orbit) instead of F9 earlier makes taking risks and iterating faster even more appealing.

It even seems to break inline links, like in the "split-horizon" section:

> System administrators can find relevant documentation here.

I'm pretty sure "here" should be a link, but of course that doesn't work when the marketing department uses a PNG instead of HTML.

I'm also surprised that Mozilla / the CDN don't optimize the PNG. `zopflipng` reduces the size from 285K to 153K.

And of course it's named "Final-DNS-over-HTTPS-05-1.png".

    fd -e py

Also neatly bypasses the glob issue.

You could try inputting your name as [Latin Small Letter E][Combining Acute Accent]:

e◌́ => é

Which should keep the `e` intact, while the combining acute accent (0xCC 0x81) may "only" get converted to a `Ì` which may be stripped. 0x81 is undefined in Windows-1252, so I have no idea what would happen to that, but probably be stripped as well, keeping just Leon.

Likely `dom.event.clipboardevents.enabled`:

https://developer.mozilla.org/en-US/docs/Mozilla/Preferences...

If someone else is in the habit of randomly selecting text and they're using linux, they may want to disable at least `clipboard.autocopy` if they don't use it. No reason to simply tell websites every selection you do, IMHO.

As long as `chrome://global/content/config.xul` still exists, you can use it. I certainly do, since the new interface is horrible and Mozilla constantly dismisses the obvious usability issues.

Sadly it doesn't work in Firefox after setting `privacy.resistFingerprinting` and Mozilla refuses to allow an override :(

Possibly also the IPv6 ULAs:

https://en.wikipedia.org/wiki/Unique_local_address

Not sure if those can be expressed in uMatrix as a prefix rule.

`privacy.resistFingerprinting.letterboxing` is currently a separate setting since it's still rough around the edges. Not sure if it works on Release, I have it set on Nightly.

It seems Mozilla is in the process[0] of moving the signature scheme to COSE, which allows timestamping[1]. A code comment[2] says that the current package format doesn't allow it.

[0] https://bugzilla.mozilla.org/show_bug.cgi?id=1545836

[1] https://tools.ietf.org/html/rfc8152#section-4.5

[2] https://searchfox.org/mozilla-central/rev/b9da45f63cb5672449...

The video is gone (censored?), does someone have a backup copy?

> more security around the data that is used for fingerprinting, such as [...] screen size, window size

Available in Nightly under a hidden boolean preference `privacy.resistFingerprinting.letterboxing`.

~~No, really. He's talking about the earths surface, the xkcd is about the earths volume.~~

Ok, the xkcd is about nanobots with a volume of "a few cubic microns"[1], whereas atoms are much smaller.

[1] https://www.explainxkcd.com/wiki/index.php/865:_Nanobots

If you want to test this in Firefox you can set these prefs:

security.insecure_connection_icon.enabled

security.insecure_connection_text.enabled

How about osd-level=0 with no-osc? In my (quick) testing this works.

> Women who asked obtained a raise 15% of the time, while men obtained a pay increase 20% of the time.

> Asking does not mean getting — at least if you are a female.

Rather: Asking does not mean getting, more so for women than for men.

Implicit TLS is already favored for Email submission and access per RFC8314: https://tools.ietf.org/html/rfc8314

The problem is partly because we don't have an assigned port for MTA2MTA implicit TLS. Otoh DANE also already provides a way to have mandatory TLS for MTA2MTA traffic.

Proceed seems to be the wrong verb here, as that dialog looks like it appeared after clicking a cancel button, and if I don't want to cancel I "return" to the previous screen where my data still is and don't "proceed" to somewhere.

It is supported by AMD, the OEMs just have to support it on the motherboard site too: https://forums.anandtech.com/threads/amd-ama-starts-at-12pm-...

All Raven Ridge processors have ECC support[1], but it additionally requires motherboard support. Would be great if some laptop manufacturer would undercut prices of current ECC laptops by >1k$ by pairing Raven Ridge with ECC or we get at least a µATX or ITX board.

[1] https://forums.anandtech.com/threads/amd-ama-starts-at-12pm-...

edit: As AMD is already throttling DRAM speed dynamically for Ryzen Mobile to conserve power, it would be an interesting experiment to see if they could throttle ECC DRAM even lower, so that it consumes less power than normal DRAM.