Boris van Hoytema

These should be fixed as a part of the 0.2.0 release process, **and not before**. Otherwise the links for editing pages will break between the published standard and the edit...

@Ainali how are your experiences with that? Good enough to flat out replace Grammarly with it?

This is an interesting question. The goal here was perhaps to give guidance as part of the requirement because the guidance is so crucial to making the point. That was...

I think framing it as 'within the fullest extend of the law the law' and exempting 'fraud detection' should cover this. I think 'law enforcement' and 'national security' make it...

Perhaps something like: > All source code [...], wherever permitted by the law, MUST be published and publicly accessible with the exception of source code used for fraud detection.

Fraud detection code and algorithms are a case where knowing the algorithm can defeat it's purpose, so it is generally exempt from these kinds of rules without a legislative foundation....

I think you are right. Those changes will always need to happen concurring with a major version bump, including an upgrading procedure. I'd say we should go try this once...

Both of these have to do with the parsing of long links. The CSS engine is pretty difficult in this regard, perhaps we can spend some time at the next...

This is absolutely right, and comes for now mainly from trying to keep the technical system simple to use. We should definetely update this to make it more usable.

@bertspaan there is now a schema.json in the master, can you perhaps take a look at that?