[defrost]

I'm not seeing anything related to security and 2FA.

The last thing the world needs is Pear of Anguish ransomware.

[sgtnoodle]

Being a UART protocol, it seems like physical access is assumed.

It's interesting as an asynchronous variant of g-code. Given the inherent safety implications, I think an improved protocol would benefit from some sort of checksum and feedback mechanism. Also, it seems perhaps a bit confusing to overload both position and velocity control using the same "l" code.

[thot_experiment]

That's because it's completely irrelevant at this level, not everything needs security baked in.

[qikInNdOutReply]

But imagine its a intruder who gets you off, not your significant bother. Imagine the implications, if adam gets with eve.. thats almost original sin.

[CoastalCoder]

> significant bother

Fabulous.

[Uncheck42]

The security should be baked into the relay aka. whatever you use to translate the data from a IP based protocol to serial data.

T-Code is designed to be simple to understand, implement and decode by micro controllers over a wired connection and those micro controllers often lack the processing power to do cryptographic security. This relies more on physical security.

[fulafel]

Most small microcontrollers can do cryptographic security even in pure software - a c64 6502 can too.

[imhoguy]

It is Rust so must be safe.

[Uncheck42]

T-Code itself is just a protocol and has no particular programming language.

Buttplug.io which is part of the same project is written in Rust, but that's another story.

[GuB-42]

https://www.theverge.com/2020/10/6/21504019/internet-enabled...

[iudqnolq]

Amusingly a significant subgroup finds the idea of vulnerabilities exciting.

[poulpy123]

that makes the things spiciers