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