@kissane please tell me that some of those shards also disappeared into your mouth, because then that’s the best kid memory ever.

Also yes, I remember being in the (afaik) unsupervised childcare area in Pittsburgh as a toddler? Coops for kids are the best.

@kissane I LOVE the idea of PSFC-style collective volunteering except applied to time-based knowledge work to support a platform. Not the open source contributor. Not the volunteer knowledge expert in a forum. Actual on-the-clock work. 2h 45m shifts for:
- customer support
- editing
- documentation
- testing
- monitoring
- etc

What is the coveted “cheese cutter” shift? The morning cleaning crew that no one wants but gives 2x the credits? Child care?

@darius Maybe there are already projects that do this, and discovery is enough of a catalyst? Maybe everyone just falls back to a basic `note`? Forgive my ignorance, I’m basically just rehashing things I’ve had to work through previously.

@darius you start to get at version interop at the end of the video, and separately you mentioned in another comment asking “what would opt-in look like?” Any gluing of these two together, as in a registration of schema transformations from one to another? So far it seems like thenproject is saying “ok, now you as a fedidev can target the right schemas for your community that will deliver value,” but it leaves the outliers as just that.

@darius Your stance on semi-anonymized data, the idea of using relay traffic exclusively, the (forthcoming) web presence of being able to browse this information: wonderful.

@darius I LOVE the idea of a schema observatory. I’ve done quite a few projects in the past that involve schema registries, and they can be so helpful to a community who cares. This idea of effectively reverse-engineering the current utility of supporting existing federated schemas is awesome.