I’ll preface with IANACL, but you seem to be making a moral argument yourself about A), that it is not reasonable.
You have, I assume, a licensed copy of Harry Potter. That license restricts you from doing certain activities, like making (distributing? Lets go with distributing) derived works. Your models are derived works. Thus when you distribute your models, you’re violating the licence terms you “agreed” to when you acquired your copy of Harry Potter.
This is no judgement by me about whether that’s reasonable or not, just my understanding of the mechanics.
“Nightmare” is too strong, but it looks from the simple example that generators are managed by jumping between coroutines, and one of the coroutines is the renderer? (Sorry, I’m on my phone and probably not conveying my point very well)
I’d be interested in seeing this hooked up to Xstate.
What are peoples thoughts on using TLS client certificates for authentication?
Given we're talking about APIs, we avoid many of the UX problems, but it feels like taking on a different set of problems than just using a bearer token. It does provide baked in solutions for things like revocation and expiry though.
You have, I assume, a licensed copy of Harry Potter. That license restricts you from doing certain activities, like making (distributing? Lets go with distributing) derived works. Your models are derived works. Thus when you distribute your models, you’re violating the licence terms you “agreed” to when you acquired your copy of Harry Potter.
This is no judgement by me about whether that’s reasonable or not, just my understanding of the mechanics.