Gregory's Server
@f4grx No yeah, I understand, and in a perfect world, clients would be able to negotiate that but in reality it's a lot more complicated than that.
For example, clients have to parse the software to know what APIs they are dealing with, and such a complex feature like Comment Controls would need to be implemented carefully so as to not break existing APIs, while gracefully handling clients that can
Now throw in forks like glitch, it's not so easy to determine the API schema and thus, this feat
@dansup yeah, devil in the details as usual. If that compatibility rule is not baked it from inception it's hard to do later.
I work with smart carts, with long develop/deploy cycles, so we usually think about the future much more than in a web app. Yet this "careful" design is possible everywhere. It's probably also more annoying to design. I understand.