dnachips VS libu8ident

Github here - https://github.com/koeng101/dnachips

It is a bit dead when it comes to a git, since I am trying to get the first machine needed, which is a DNA synthesizer (asked about that here https://groups.google.com/g/diybio/c/V3OYVBxaH04 for example).

The idea is that with a traditional DNA synthesizer I can have positive controls of the chemistry, and develop a chip that can fit inside the flow cell of the existing synthesizer. In biotech, everything goes wrong a bit more often than in computer science, so the focus lately has been getting my hands on a working synthesizer. This is a tried and true method of getting chip synthesis working.

If that works, I'd like to provide the chip at cost for integrators, as well as develop a functioning full product for integration with some bots I'm building for my official work.

Personal website is here - http://keonigandall.com

In programming languages it's much worse. Identifiers can either be unidentifiable, and if so everybody has a different opinion what "identifiable" means. Even the standard on identifiers, UTF-39, is buggy and has too many interpretations, leading to a complete disaster. https://github.com/rurban/libu8ident/blob/master/doc/c11.md

In punycode domain names it's quite simple still.

With other names, it's even worse. No-one cares. Linkers do not, username and filesystem drivers do not. The Apple HFS+ did care a bit one day, until someone in the higher ranks decided that no-one needs unicode security anymore and switched the new APFS to unsafe again.

No, it's definitely not safe to use unrestricted Unicode in a compiler. See https://github.com/rurban/libu8ident/ for identifier rules, and http://www.unicode.org/reports/tr55/ for much worse problems.

That's why unicode published the security guidelines and mechanisms to avoid such attacks. In 2004 already.

The problem is that nobody cared. Browsers invented punycode instead of following tr39, email ditto. But ok, at least something. Java did it, cperl did, rust did it.

Everybody else is vulnerable. Esp. most other programming languages, filesystems and login systems. https://github.com/rurban/libu8ident/blob/master/doc/c11.md

I'm maintaining such a library.

coreutils, diff, grep, patch, sed and friends all cannot find Unicode strings, they have no string support. They can only mimic filesystems, finding binary garbage. Strings are so rthi g different than pure ASCII or BINARY garbage. Strings have an encoding and are Unicode.

Filesystems are even worse because they need to treat filenames as identifiers, but do not. Nobody cares about TR31, TR39, TR36 and so on.

Here is an overview of the sad state of Unicode unsafeties in programming languages: https://github.com/rurban/libu8ident/blob/master/c11.md