Closed b1conrad closed 3 years ago
We should be able to do this with the tag server of our Manifold instance
Have an initial commit which has an example for which the QR Code would look like this:
Remaining step is to incorporate the shortcut and its QR Code into the workflow. The challenge is that the invitation is currently produced with a query, and registering the URL and its shortcut requires an event.
A recent commit fixes this, by adding a new ruleset named (for conciseness) simply s
.
If used, the shortener ruleset MUST be installed in a pico before the io.picolabs.aca.connections
ruleset, because it is used as the latter ruleset is being installed.
The changes surrounding this issue still need to be fixed for the v1 engine in the NEXT
folder.
How do you think that could be enforced or made simple?
Our connections invitation URLs are much too long. The generated QR Code is too large to be readable by some scanners (in particular the trinsic phone app).