DESIGN.md: > Each rule below is enforced mechanically by the skill, not left to vibes. > R1. Repo docs are the memory; not in HANDOFF.md = didn't happen SKILL.md: > Not in docs/HANDOFF.md = didn't happen. Refuse to…
I'm not up-to-speed with the current state of sandboxing in browsers, but in principle it's (on modern operating systems) not especially hard for them to sandbox the decoding into a separate process with basically no…
> can't all the banks just agree to enforce 3DS They could, but it's one of those things that really only work if everybody joins. Because 3DS is rarely used right now, a portion of merchants don't even support it, so…
Account Updater functionality isn't necessarily even involved there. In the end whether to accept a transaction is up to the issuer, and quite often they'll keep accepting recurring transactions on otherwise outdated…
Indeed, I suspect that's what went on here. I don't think there even exist 99 providers of what's customary called a digital wallet (e.g. Apple/Google Pay), and there's no definitely no single person that uses 99 of…
> merchants can’t select what level of security they want from the credit card processor That really depends on the processor; many processors do allow merchants specify your acceptance rules in quite deep detail.…
> but things like this are a matter of negotiation between the card issuers and the merchants. Not necessarily, the EU has mandated strong customer authentication by law (PSD2), and as a result has practically universal…
The situation with e.g. BlueHammer is fundamentally different: there, the only party that could act on it (Microsoft) ignored them. In this case, the parties that could act on it weren't notified at all. I'm also not…
> I don't know what exactly can load this module Well, for one thing, opening an AF_ALG socket, as the exploit does.
In my world, responsibility is not just checking a box of following industry practice. Responsibility, as Wikipedia puts it on their social responsibility page, is working together with others for the benefit of the…
None of the distros were.
Two things can be true simultaneously: the Linux kernel ecosystem should have done better at communicating this to their downstreams, and publicly sharing the exploit was irresponsible. It is not the responsibility of…
There's no contradiction, the point is that Bob is able to produce valid output using LLMs, but only while he himself is being supervised; and that he doesn't develop the skills to supervise independently himself in the…
> That's why it went beyond web, and why all modern native UI frameworks have a similar model these days. It's more the other way around, this model started on desktop (eg WPF) and then React popularized it on the web.
> It would be infinitely simpler if one could simply 'cross-compile' down to older symbol versions, but the tooling does not make this easy at all. It's definitely not easy, but it's possible: using the `.symver`…
The same's true for the radio on a Raspberry Pi, though.
So yes, in theory you can always deploys sets of compatible services, but it's not really workable in practice: you either need to deploy the world on every change, or you need to have complicated logic to determine…
Some smartphones are locked down by their vendors. There's plenty of options to get full root access on something that's for all intents and purposes a smartphone, especially if you don't particularly care about…
https://github.com/jj-vcs/jj
Blue/green might allow you to do (approximately) atomic deploys for one service, but it doesn't allow you to do an atomic deploy of the clients of that service as well.
> Good luck getting 100+ devs to all use the same logical commit style The Linux kernel manages to do it for 1000+ devs.
If my change is small enough that it can be treated as one logical unit, that will be reviewed, merged and (hopefully not) reverted as one unit, all these followup commits will be amends into the original commit.…
Squashing only results in a cleaner commit history if you're making a mess of the history on your branches. If you're structuring the commit history on your branches logically, squashing just throws information away.
The article is from 2019, things might also simply have changed since then.
GPS gets its time from NIST (though during this incident they failed over to another NIST site, so it wasn't impacted).
DESIGN.md: > Each rule below is enforced mechanically by the skill, not left to vibes. > R1. Repo docs are the memory; not in HANDOFF.md = didn't happen SKILL.md: > Not in docs/HANDOFF.md = didn't happen. Refuse to…
I'm not up-to-speed with the current state of sandboxing in browsers, but in principle it's (on modern operating systems) not especially hard for them to sandbox the decoding into a separate process with basically no…
> can't all the banks just agree to enforce 3DS They could, but it's one of those things that really only work if everybody joins. Because 3DS is rarely used right now, a portion of merchants don't even support it, so…
Account Updater functionality isn't necessarily even involved there. In the end whether to accept a transaction is up to the issuer, and quite often they'll keep accepting recurring transactions on otherwise outdated…
Indeed, I suspect that's what went on here. I don't think there even exist 99 providers of what's customary called a digital wallet (e.g. Apple/Google Pay), and there's no definitely no single person that uses 99 of…
> merchants can’t select what level of security they want from the credit card processor That really depends on the processor; many processors do allow merchants specify your acceptance rules in quite deep detail.…
> but things like this are a matter of negotiation between the card issuers and the merchants. Not necessarily, the EU has mandated strong customer authentication by law (PSD2), and as a result has practically universal…
The situation with e.g. BlueHammer is fundamentally different: there, the only party that could act on it (Microsoft) ignored them. In this case, the parties that could act on it weren't notified at all. I'm also not…
> I don't know what exactly can load this module Well, for one thing, opening an AF_ALG socket, as the exploit does.
In my world, responsibility is not just checking a box of following industry practice. Responsibility, as Wikipedia puts it on their social responsibility page, is working together with others for the benefit of the…
None of the distros were.
Two things can be true simultaneously: the Linux kernel ecosystem should have done better at communicating this to their downstreams, and publicly sharing the exploit was irresponsible. It is not the responsibility of…
There's no contradiction, the point is that Bob is able to produce valid output using LLMs, but only while he himself is being supervised; and that he doesn't develop the skills to supervise independently himself in the…
> That's why it went beyond web, and why all modern native UI frameworks have a similar model these days. It's more the other way around, this model started on desktop (eg WPF) and then React popularized it on the web.
> It would be infinitely simpler if one could simply 'cross-compile' down to older symbol versions, but the tooling does not make this easy at all. It's definitely not easy, but it's possible: using the `.symver`…
The same's true for the radio on a Raspberry Pi, though.
So yes, in theory you can always deploys sets of compatible services, but it's not really workable in practice: you either need to deploy the world on every change, or you need to have complicated logic to determine…
Some smartphones are locked down by their vendors. There's plenty of options to get full root access on something that's for all intents and purposes a smartphone, especially if you don't particularly care about…
https://github.com/jj-vcs/jj
Blue/green might allow you to do (approximately) atomic deploys for one service, but it doesn't allow you to do an atomic deploy of the clients of that service as well.
> Good luck getting 100+ devs to all use the same logical commit style The Linux kernel manages to do it for 1000+ devs.
If my change is small enough that it can be treated as one logical unit, that will be reviewed, merged and (hopefully not) reverted as one unit, all these followup commits will be amends into the original commit.…
Squashing only results in a cleaner commit history if you're making a mess of the history on your branches. If you're structuring the commit history on your branches logically, squashing just throws information away.
The article is from 2019, things might also simply have changed since then.
GPS gets its time from NIST (though during this incident they failed over to another NIST site, so it wasn't impacted).