• 0 Posts
  • 220 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle
  • Aluminium antiperspirant stains are actually pretty easy to remove if you soak your shirts in something acidic - I use sulphamic acid (commonly sold as the main ingredient in coffee machine descaler, so pretty safe, and not as smelly as vinegar) and just leave things for a day, then any residue that’s left just comes out in the wash. The reason it stains is that long-acting antiperspirant seals the aluminium salts in tiny wax beads which break open over the course of the day to keep releasing more, and wax needs a lot of exposure to soapy water to dissolve, but it’s protected by the aluminium salts jellifying when wet, and they in turn are protected from rinsing away by the surrounding wax. Acids can attack both.








  • The exact quote is:

    And this was a debug session from hell, enormously helped by an AI doing much of the grunt-work.

    I’d like to call it my tireless helper, but the AI several times stated flat out that this was impossible and unsolvable and that we should just write a report about it.

    I suspect those things have been trained by people who may not be quite as stubborn as I am.

    But while the AI was ready to give up several times, it did keep adding debug code and analyzing it faithfully when I pushed. So credit where credit is due and I let the AI write the commit message above.

    This is basically a one-liner fixing a bogus “round_up()” to a “round_down()”, but there were 24 patches adding more and more debug information to this, and 18 kernel boot to finally narrow it down to this. - Linus

    That’s a long way short of finding the bug and pointing it out, and instead is just the tedious work of adding checks and then deciding where to add more checks when you have the result of the previous checks. I suspect if we’d spent a trillion dollars on a tool for that, we could have come up with something much more efficient than an LLM.







  • No, don’t use CLAMP, use CLAMP_TO_EDGE. CLAMP is a dumb mode for niche applications that all switched to using shaders around the turn of the millennium. No GPUs have direct hardware support for CLAMP and so they have to emulate it instead. You are throwing performance away for no reason.

    (also, technically, the image is using CLAMP_TO_EDGE as CLAMP is a 50% mix of the border colour and the edge pixel colour, so it would be greyer if the border colour is grey like the first image suggests.)




  • In the UK, it’s because it’s the defence’s job to notice this kind of thing, but paying for a good lawyer is life-ruiningly expensive, and public defenders via legal aid are paid hourly, but have a cap on the number of hours that’s never enough to deal with anything properly, so are either rushing everything and miss things, or are massively overworked and earning well below minimum wage when their unpaid work is included.

    I don’t know if the same problems extend to Canada, but it’s fairly likely, as the adversarial approach just inherently means the defence has to do loads of things that would be someone else’s job or not need doing at all under alternative systems, so you have to have a trained professional doing lots of work, and that’s inherently expensive, but taxpayers don’t like spending money on defending people who probably did crimes.


  • And face/id scanning aren’t as good as the solution that works in the real world for alcohol because they can be tricked by a video game face or a photo of someone else’s real ID. Any solution that works online can either be trivially bypassed or adds an unacceptable level of hassle and risk (e.g. leaks being used for blackmail) for legitimate users.

    The solution for alcohol works really well because very few children have the ability to get a fake ID or convince people it’s real and theirs until they’re close enough to legal age that it doesn’t really matter much if they drink, and parents have the ability to override it on a per-drink basis if they’re okay with children drinking under their supervision, while non-parents can only operate on a very small scale before they risk getting caught. Once people are old enough that they’re obviously adults, they don’t get asked for ID anymore, so it’s only a small fraction of the population that have to deal with any hassle, and a shopkeeper can’t memorise every single ID card they’ve ever seen and then suffer a cyberattack and reveal what alcohol specific people have bought to someone who’ll threaten all of them in case some of them are willing to pay to have it kept secret.

    Preserving privacy means tokens become trivial to share, and then there’s nothing stopping a ten year old watching huge amounts of extreme porn except for things that would have worked without having any system, like having their parent stand behind them. If the new system doesn’t improve things compared to having no system, then there’s no point making it.


  • It’s not as good as the solution for alcohol as one bottle of beer making it to a child gets used up after only giving one child one drink. Once a token leaks, it can be shared again and again and used by arbitrarily many children arbitrarily many times until someone notices that it’s leaked and revokes it (which then means that websites need to actively update a list of revoked tokens instead of just relying on public key cryptography to confirm it was signed by one of a few authorities, or all tokens will need to expire automatically after a short time).