...

Inspired by the Live Web series of white papers, particularly Forever and , Personal Channels, and Making Everything "Smart", we set up a game at OpenWest 2018. We invited conference attendees to participate, competing for daily prizes. Each participant was given an owner pico and a QR Code which, when scanned, would produce a connection between the person scanning and the person owning the pico. Each such connection counted as one point for each of them. The contest was to see who could make the most connections from their owner pico to other owner picos.

...

where the particular ECI shown here is one belonging to the game pico used during OpenWest.

Conclusions

We had a lot of fun running the game, and had many conversations about picos. Putting the code together required the use of many techniques, most of which are documented in the KRL Cookbook section of the documentation.

Innovations

...

1. Account management and owner picos, including the programmatic creation of a new owner pico
2. a collection pico, based on a provided collection ruleset (itself based on the provided subscription ruleset)
3. synchronizing across the members of a collection (sync_members rule)
4. using two kinds of subscriptions in the same application, and displaying them in the UI with different colors and line thicknesses
5. our first big live system (on the new node pico engine) with dozens of participants from outside of Pico Labs
6. identifying endpoints by having these devices (not controlled by us) store a cookie
7. using "scaffolding picos" to build a structure of picos which lives past the removal of the scaffolding
8. using a QR Code for newly-minted owner picos, encoding an ECI for each
9. an application involving picos running on more than a single engine
10. using subscription-based cryptographic signing of messages between picos
11. chaining multiple rules for a single event, implementing the authorize-then-use pattern
12. chaining an event through a series of picos (initials and tag-line from game pico to collection pico to owner pico)
13. using a cookie to store pending connections
14. rolling over from one contest day to the next without losing any peer to peer connections

Owner picos, the very idea

Several people wondered just what we meant by something said to many, "When you participate in this game, we are giving you an owner pico."

For this ownership to be meaningful, and secure, we at Pico Labs either need to be serious about hosting picos, or we need to encourage people to set up their own engines and move their owner pico from our provisional engine to their own.

Future work

DID login

Hardening

...