joshuaavalon

5 ms·

1.
by joshuaavalon 4y ago
The difference between JWT and session is where the state is stored. For session, you need a centralized backend to access the data stored in the session. For JWT, you only need to verify the signature of the token to trust the data stored
2.
by joshuaavalon 4y ago
Things do break in production does not mean you don't take any measures to reduce the chance of happenings. Following your logic, why should we test our code before deployment? Everyone should push to master and deploy to production. T
3.
by joshuaavalon 4y ago
Most of the services provide backup codes when you enable 2FA. I don't think that's a huge problem.
4.
by joshuaavalon 5y ago
GitHub issues have labels. You can add "Resolved", "Won’t Resolve", "Paused" as you like. Many large repositories use labels to show the state of the issue. You do not need to rely on open or closed.
5.
by joshuaavalon 5y ago
There is a setting in URL of the password called "Match Detection"[1]. You can change it to "Host" if don't want it to match subdomain. [1]: https://bitwarden.com/help/article/uri-match-det
6.
by joshuaavalon 5y ago
I heard MKBHD said it only alert you alert you went home or workplace. Otherwise, it will keep alerting everyone on public transport.
7.
by joshuaavalon 5y ago
If you want central authority, isn't it the job of CI? Use CI to verify the commits fits the styles and review the commits before merging.
8.
by joshuaavalon 6y ago
The problem for me is other people not using it. When I call another library, there is no type hint and the documentation is poor. You can only read the code and guess the type yourself.