SECCOMP_RET_USER_NOTIF appears to switch between the tracee and tracer processes for each syscall. Using SECCOMP_RET_TRAP to trigger a SIGSYS for every syscall in IO intensive apps introduces 5% overhead (and avoids a separate tracer).
I wonder if there's any mechanism that works for intercepting static ELF's like Go programs and such.
Taking down "bad" Google reviews is an entire industry these days [1].
And of course there are scammers on all sides - not just legitimately bad stores trying to whitewash their online presence, but also entire scammer rackets that extort legitimately good stores by flooding them with BS reviews [2].
I hope Photoshop runs in the Linux VM introduced with Android 16, so I can stop carrying a laptop to edit photos and bring just a 0.5kg monitor instead.
It's not sweets and it's not an addiction, not everything on TV is for mindless consumption. The viewer is not who's at fault here. The right mindset is not "accept their terms or give up", it's "make your voice heard and try to make the manufacturers change their practices".
I have no idea, but I do have a PC/AT keyboard with similarly-shaped keys. They have the usual "square horseshoe" / "anti-roll bar for Matchbox cars" arrangement underneath so they don't rock when you press the end.
I believe you're right. From my limited memory of that period, it was a mechanical constraint.
Keycaps tended to be molded with a hollow cylinder or stalk on their base, which fitted through a snug round aperture on the keyboard base and pressed against a spring or other restraint. Pressing the key down against the spring actuated a pcb-mounted push-switch (or bridged a pair of adjacent connectors on the pcb) that provided the keypress signal. Pressing a wide key off-centre would cause the plastic stalk to bind against the enclosing aperture. Forcing the user to press direcly above the stalk mitigates this - hence the raised part of the keycap.
There is a stack exchange question about this at [1].
As to why the shift keys were wider to begin with, I'm not sure. Perhaps a consequence of the lack of the mechanical constraints that forced typewriter keyboards into a strict grid due to the interleaving of the lever arms. Some keyboards, notably the Commodore PET, didn't use wide shift keys [2] though.
It is worth noting that keyboards in that era were machine-specific, and often hard-wired to the main system box. Afaik standardisation and interoperability didn't happen until RS232 and, later, ps2 keyboards were introduced.
The keyboard on the Apricot uses round capacitive foam pads under the keys. This means the keys had to be square, or they needed a mechanical thing like the space button on the photo here: https://www.baffo71.com/details.php?id_img=7
So, I think it is a mechanical/electrical limitation.
He was paid by Google with money made through Google’s shady practices.
It’s like saying that it’s cool because you worked on some non-evil parts of a terrible company.
I don’t think it’s right to work for an unethical company and then complain about others being unethical. I mean, of course you can, but words are hollow.
I wonder if there's any mechanism that works for intercepting static ELF's like Go programs and such.
reply