Stream gets faster fixes in general, but yeah for embargoed security fixes it goes the other way around

Even if you are Meta. The only trick we use is something anyone can do - hotfix it in Hyperscale, or download the Stream fix as soon as a signed build is available without waiting for it to be fully released

Right. But it does not matter in this case - Meta rolls out its own kernel (we employ a lot of kernel engineers, and PSA our Linux teams are hiring software engineers!) and we maintain our systemd backports and some other packages in the CentOS Hyperscale SIG

> That is: on 64-bit x86, you have with frame pointers twice as many available registers as 32-bit x86 has without frame pointers

Indeed.

> I don't think getting rid of frame pointer omission would be viable if Fedora still supported 32-bit x86

Fedora still supports it (e.g. packages are still built for i686, and you can install them on x86_64) though it has dropped 32-bit ARM. But the change to reenable frame pointers will not be applied to 32-bit x86 builds.

Big Tech firm - acknowledged it with a day of learning but no day off, which is not fun especially for parents whose kids' schools do close on Monday

yeah, I wonder when the Facebook container will make it to mobile - it's one of their own after all so there should be no safety issue.

Freenode's IRC servers were down which was unexpected for me. I was expecting old-school communication networks to not have a dependency on Cloudflare.

I've had no connection interruptions to the three IRC networks I'm connected to. Freenode, EFnet and Hackint.

I loathe Discord, and I can barely contain myself with schadenfreude at this news.

I also had no issues connecting to a few different networks, including Freenode and EFnet.

Ironically, the best phones to do that are Google's own Pixels - to give credit where it's due, at least the phones have unlockable bootloaders (unless you buy the Verizon variants).

eg GrapheneOS currently only supports Pixel 2, 3 and 3a:

https://grapheneos.org/releases

Roku and Amazon Fire TV works fine with captive portals though (Roku elegantly asks you to connect to a custom WiFi AP that just forwards the captive portal to your phone). So this is another case of Google making assumptions that limit their devices' usability.

It's been awesome. The one feature I'm still missing from LastPass is being able to mark some entries as more secure and reprompting auth on those.

Which desktop client did you try? The official Mac client, at least, has secret chat just like the mobile clients (I just used it yesterday)

Note that Telegram secret chats are end to end encrypted (default chats are not) but you're still dealing with the Telegram server (not peer to peer)

I tried arch linux one.

I have just installed the Mac client and it allows to create new secret chat but it does not show the secret chats created before on your phone. At least that is what happened to me.