It looks like a nice little library; but oh boy must this be so limiting for the product teams that are forced to use. Everything looks like it's straight out of the 1990s.
Yeah, but it just feels so ridiculous the other way too! The reason people use Word et al instead markup languages is because of the UI, right? Why does that matter here? After you generate a final PDF, no one needs to know how you made it?
Shortly after the Online Safety Act went into operation, there was politically charged/sensitive/opinionated content on X mysteriously disappearing for UK users but nobody else in the world.
JWT inside of a cookie is fine. This gist is unnecessarily pedantic and seems oblivious to the fact that 99% of JWT impls are indeed just stuffing it inside a cookie.
But yes, short life times with frequent renewals is necessary; that's obvious though. And same applies to any other auth tech.
Ml-family languages (and frankly, all natively functional languages) are just incredibly terse and information-dense second only to stuff like APL. And yet when written idiomatically and with good object and type naming they are surprisingly readable and writeable.
'Twas a bad idea to train LLMs on the corpus of leaky, verbose C and C++ first instead of on these strict, strongly-typed, highly structural languages.
