Echo JS 0.11.0

The only thing I really hate about all of them, is they are huge monolithic libraries and upwards of a meg of JS because you can't pluck out just enough for say a pie chart with overlays.

Given the audience, a link to the github repo would be more appropriate (GPL3 license) [1].  It's an interesting idea.

Also worth noting the backend does seem to be Java based.

[1] https://github.com/bastillion-io/Bastillion

The only implementations of JWT I've actually seen in the wild, or would actually support are using asynchronous RSA public/private key signing.  This allows you to have a trusted signing authority, which is imho better than a shared secret between two systems.

Also, only use trusted authorities where the actual public key is side-loaded from an internalized resource.  Do *NOT* trust/use the header portion of JWT for this part.

The article itself is a bit too shallow and doesn't really discuss how this can work in access infrastructure, which becomes more common in a corporate or larger social interaction.  There's also how to develop/design services to consider.

Beyond this are considerations for token duration, refresh and revocation.

NOTE: currently working on an access/identity management system centered around JWT tokens for multiple applications.

Interesting concept... though probably limited use in proximity.

Could be especially cool for chats for live streams.

NOTE: No unit or integration tests.

Would love to see a comparison of strapi vs. GraphQL options.

Not seeing much of a real benefit over just aliasing some React.createElement options...

Most of this advice is not just for Angular development.  It's also a bit thin...

Suggested reading from Steve Souders, some of this is a bit older, but most still applies. Some of the DOM quirky issues are significantly different, but general optimizations and suggestions around actually testing for performance metrics apply.

High Performance Web Sites: https://www.amazon.com/gp/product/0596529309

Even Faster Web Sites: https://www.amazon.com/Even-Faster-Web-Sites-Performance/dp/0596522304

Steve Souders' Blog: https://www.stevesouders.com/blog/

Beyond this, there's also the issues of perceived performance, you can actually be too fast, when people expect a spinner or loading screen, they may not believe something is actually done.

There are a lot of counter-examples for performance in design.  It's a matter of actually developing for some optimal paths without investing too much time before you need to.

NOTE: make sure to encrypt your app keys for anything public facing, or limit their visibility to only CI/CD platforms.  For travis, on open repos, definitely don't accidentally commit this in the open.

It looks like a homegrown CI/CD type agent and not a bad idea.

Auth error on demo site like: OAuth Forbidden - You are not a sandbox user of this account...