3 ms·
> Eventually, after tweaking my request, it gave me the IBAN in isolation. Lazy? Yes. Efficient? Absolutely. ... I mean, not very efficient. You could just've
by rsynnott 2y ago
> Eventually, after tweaking my request, it gave me the IBAN in isolation. Lazy? Yes. Efficient? Absolutely.
... I mean, not very efficient. You could just've used actual OCR; if the phone was an iPhone this is built right in, would take two seconds to select the IBAN, and should be pretty reliable. I think modern Android has something similar, though couldn't swear to it. LLM-y things _sometimes get OCR of numbers wrong_, like, a lot more than actual OCR software, which is now close to perfect on printed text.
Now, with it being an IBAN the practical risk here would be low; IBANs have two checksum digits, so at worst you have a 1 in 100 chance of an incorrectly-OCR'd IBAN being accepted (in practice, it's lower than that; some checksum-passing bad IBANs will have non-existent country codes, and likely be immediately rejected, or non-existent bank codes or account codes, and will be rejected at some point, though potentially not immediately. This would be _really_ risky with, say, US ACH, where the routing numbers are not checksummed and are only eight digits.