[kazinator]

> Unfortunately, and unlike a QR code, the data is not encoded in the drawing itself.

Obviously, there is data in the drawing. Just that data is a symbol which is resolved through some proprietary app, which maintains the association in a private database where it is subject to expiry and such.

Just some third party has to develop an independent app to open up access to the data in the drawing and use it outside of the original system.

There might not be enough data in the drawing for it to satsify the same use cases as QR codes.

For private labeling, it could be good enough.

For private labeling, though, I'd prefer something that just scans alphanumeric labels, and not some silly triangles. I don't want to rack my brain inventing a triangle code for my Lady Diana collectible #153 that is different from those which I tacked onto 1 through 152. :)

[gbl08ma]

> Obviously, there is data in the drawing.

I know this, and one can think of it as the numbers encoded in a plain old EAN-13 barcode. But as with these barcodes, the numbers by themselves don't usually have any meaning, they are just the key of a key-value pair. In this case the key-value database is in the Meshtag servers.

Like you said, the "raw numbers" can still be useful for small-scale labeling, but once you are at the point where you're just using the drawing to record a simple ID, it may be just easier to write the ID alphanumerically and have the computer OCR it or even just type it by hand (with a checksum digit, this can be more practical and effective than having to deal with camera scanners - "oh where is that app again/where did I leave my phone again...").

[ytdht]

there could be much more data if you did a scribble, and it could translate to some specific data that could be useful (to stop by a third party number or code that doesn't mean anything by itself. is only useful to promote the cloud or to represent large amounts of data)