æʃliŋ, loaf of autismo @aescling@cat.family

@coriander there's an old cwebber (i think?) blog post that says this better than i can but i think it’s strictly fine that eugen wanted something diffurent from what the commewnity ended up wanting but in retrospect the purroject should purrobably have just been forked so somebody/people who actually cared about the safety features that were popular would be the one(s) in charge of implementing them

@coriander he always wanted to make Twitter 2 so i’m not exactly shocked it happened eventually; the major features that were popular early on were things he never actually even wanted to implement and to my understanding was quietly frustrated about feeling forced to do

why does pass(1) as packaged by homebrew have a hard dependency on unbound

@coriander it’s vital research

@Lady @coriander even websites which were on the latest PHP were still advised to go offline until actual patches were made available

@coriander remote code execution vulnerability on an extremely wide number of versions

mornyawn btw . also @clock, what time is it

ÆSCLING ACTIVATES the TF MACHINE!

ÆSCLING TRANSFURMS from GLACEON to EEVEE!

ÆSCLING SWISCHES its big fluffy $$$$-ing TAIL!

—

@coriander unrelated disaster

https://www.youtube.com/watch?v=Mz_Rn7jAKCc banger set

@vaporeon_ @amy @The_T apparently so that mozilla can control the certificates being used in the browser

@vaporeon_ @amy @The_T i mean, "not receiving push updates from a proprietary service run by mozilla" sounds like decision librewolf would make to me

@amy sounds like a great plan im sure there will be zero negative consequences here c:

@vaporeon_ @The_T lol

@amy @vaporeon_ @The_T mozilla have had a service to push certificate store updates without requiring updating firefox itself because of the severity of the issue. since 2015, apparently. so yeah they were quick on it