@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.
Top-level
@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. 4 comments
@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. @everyplace I mean I am hoping that people can build stuff like that on top of this! I just was gobsmacked that the basic data wasn't even out there really. Also the schema data has already proven useful in standards discussions @darius I can only imagine re: informing the standards. Also, just had the worst idea. Of course the fediSchemaTransforms should be a federated post themselves… |
@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.