zulvkr

Storing state in JWT is easy way to share state, such as user permission, between different server.

But state in JWT can be outdated due to permission changes and you it's not possible to just expire it as it's stored in client.

To solve the problem, more complex auth setup is needed such as using short lived JWT, refresh token, which feels more like a bandaid to make JWT sufficiently secure

A few hours ago, I tried to setup trpc using recommended boilerplate, I also tried fresh default T3 after that.

Both got error, which seems to be due to next/next auth dependency breaking. So it's not that painless I guess.. I found this situation quite often with nextjs example template

T3 author is very responsive though, so my issue resolved quickly

The golden rule indeed.

My previous job as pharmacist in pharma company has a lot of grunt job that I tried to automate using only word and excel sheets. It possibly saves a lot of man hour.

Why only excel and word? Pretty much because I almost can't install anything in company laptop. excel Macros also prohibited. I was thinking to create a simple js automation app in browser if it gets attention.

I showed my little automation tools to my superior but it failed to get appreciation nor support.

In the end my colleagues asks for help to run the automation but they refuse to learn how to use it themselves. Bah.