olliej

18 ms·

181.
by olliej 2y ago
So 45% do not, and that’s ok? Or the huge percentage of that 55% where their coverage is high deductible, so it’s functionally just a “you won’t be instantly bankrupted if you have a heart attack” not basic healthcare? The bizarrely antisoc
182.
by olliej 2y ago
Flash had numerous issues. The processing power available (especially on a PSP) is more than enough to be “good”, the problem with flash _performance_ is the power usage while achieving that perf. Even on laptops flash was a significant bat
183.
by olliej 2y ago
In the C abstract machine there is no restriction on the stack size, and the nature of the stack (or that pointers are involved in it) is opaque, so within the definition of the language the call stack is infinitely sized. So if we want to
184.
by olliej 2y ago
The literal definition of Turing completeness means that if you can use an environment to implement a Turing machine, the environment is necessarily Turing complete.
185.
by olliej 2y ago
The definition being used is pretty much useless, it’s literally “c cannot have infinite state”, which applies to literally anything that actually exists.
186.
by olliej 2y ago
I think the post is just a pedant/gotcha argument that is correct only in the “technically correct” sense, but is otherwise useless, as the same argument applies to literally any “Turing complete” system.
187.
by olliej 2y ago
Yeah the whole post is stupid, but it’s also just wrong: c is not bound by pointer size. A Turing machine that you implement in C as “the tape is a single array in address space” would be, but that’s not what is required for Turing complete
188.
by olliej 2y ago
Run infinitely with infinite memory, so yes we the “is it Turing complete” argument is “no because finite {X}” then a Turing machine is not Turing complete because it’s impossible to actually make an infinite Turing machine.
189.
by olliej 2y ago
The point is not "this time there's no risk", the point is basic PKI safety means you need to be able to handle certificate revocation immediately. If you can't handle it today when there's "no risk", you
190.
by olliej 2y ago
I don’t use twitter, so I - and anyone else who does not use twitter - only see a link to ars. It’s literally just a link to a link. If there’s more information, that information should be on a public site (maybe the grapheneos website?)
191.
by olliej 2y ago
Actual link: https://arstechnica.com/gadgets/2024/07/loss-of-popular-2fa-...
192.
by olliej 2y ago
I didn't want to go into implementation details as they'd complicate matters :D What you're seeing here is the big difference between specification language and implementation - the major JS engines perform free variable anal
193.
by olliej 2y ago
No, you can fork, what you can’t do is “fork and then try to keep running after the fork”. That’s never really been a supported model on Darwin, and in recent years with more threading occurring it fails faster than it did in the past. On D
194.
by olliej 2y ago
I would agree, if you’re wanting to run your server software on windows, your software should be designed to work well with windows. That goes for any OS though - if you’re running a high volume server then you shouldn’t be throwing away pe
195.
by olliej 2y ago
One of the impacted companies filed a restraining order, because they believe their incompetence is more important than basic functionality of the PKI. Can't wait to hear how they expect to respond if they ever have encounter a cert co
196.
by olliej 2y ago
Alegeus Technologies LLC: https://www.courtlistener.com/docket/68995396/alegeus-techno... It looks like a healthcare provider, so exactly the kind of company you would want to have shitty IT and security infrastru
197.
by olliej 2y ago
One thing to consider, if you're filing bugs on webkit (e.g engine issues vs. the safari app) is reporting them to bugs.webkit.org, which if nothing else results in more accessible info for you. The also used to be a fairly active irc
198.
by olliej 2y ago
Ok, so there have been a lot of comments on what causes this, which are not correct, and a few that are pretty close. Here is the actual explanation of what is happening and what is causing the leak. For context, I used to be on TC39 (the e
199.
by olliej 2y ago
[later edit: I re-read the example code, and the issue is a double capture and the author not really understanding the semantics of capture in JS, I've given a more technical breakdown and explanation at https://news.ycombin
200.
by olliej 2y ago
Old protocols truly are the gift that keeps on giving (see the numerous protocol and cipher downgrades over the years as well)
201.
by olliej 2y ago
… so you reported bugs and they were fixed?
202.
by olliej 2y ago
But they got a free coffee and everything!
203.
by olliej 2y ago
There's no actual information about the browser, but given a quick scan shows that it pulls in PyQt I assume its just a wrapper around a qtwebview? [edit: looked at the actual sources and yes it is just a qtwebview]
204.
by olliej 2y ago
haha, oh ASI - I was very confused by your example as I read this as if it was > const foo1 = function(a, b) { return a + b; } (2, 3) > console.log(foo1) // prints 5 > const foo2 = (a, b) => { return a + b;
205.
by olliej 2y ago
Yeah I came to say that these are not semantically equivalent (I guess you _could_ verify equivalence if you ensured it did not use this or eval)
206.
by olliej 2y ago
You’re missing the issue being resolved. This does not impact anything in code that has no errors, because that’s not the point. The goal of annotations like this is to 1: make it harder to make the mistakes in the first place (by making it
207.
by olliej 2y ago
Note that when Google made a blog post telling people to migrate from goo.gl to the also now deprecated Firebase Dynamic Links, the post states explicitly[1]: "While most features of goo.gl will eventually sunset, [bold]all existing li
208.
by olliej 2y ago
oh boo, it wasn't part of a soviet probe :( :D
209.
by olliej 2y ago
We can argue all we want about CI infrastructure, manual testing, test nets/deployment, staged deployment. All of that is secondary: they wrote and shipped code that blindly loaded and tried to parse content from the network, and crash
210.
by olliej 2y ago
> And yet, Apple still use NSCopyObject themselves to this very day Of course they do. The existing behavior involves NSCopyObject (for decades at this point) and user code written against those existing APIs, therefore depends on that b

More ›