@matigo Users get so annoyed by dropped features though. If they were really evil, they’d just change the supported time intervals to centuries, millennia, and geological epochs. 😈
/@axodys
@matigo To be fair, Microsoft very clearly have been telling everyone to stop ramming password rotation and composition requirements down their employees’ and users’ throats for some time now. Eg https://docs.microsoft.com/en-us/microsoft-365/admin/misc/password-policy-recommendations:
Don't require mandatory periodic password resets for user accounts
/@axodys
@matigo Yeah. I wish it was easier to wire up https://danger.systems for a project than it currently is.
/@phoneboy
@matigo You’re right. Human reward systems just don’t change that fast, I guess. 😂
/@sumudu
@matigo What you’re suggesting sounds to me like fundamental rather than superficial gamification. Which is great: I think of the heart of gameplay design as building learning feedback loops. Probably in large part greatly influenced by https://lostgarden.home.blog/2012/04/30/loops-and-arcs/. This unsurprisingly applies well to product design too eg https://learning.oreilly.com/library/view/badass-making-users/9781491919057/.
/@sumudu
@streakmachine I generally just wrap with electrical tape and keep on using it. >.>
@nitinkhanna Checked out their site. They also point to fewer deps (handy for slimming containers), a nice CLI (“what if python -mSimpleHttpServer was production ready?”), and a simpler config language. Probably easier to hack on the codebase than Nginx or Apache’s, as well, if you need to tweak things.
ETA: Oh and baked-in k8s support of some sort.
@matigo It’s also a reverse proxy. So I expect the runtime config is there for the same reason AWS API Gateway is runtime configurable rather than statically deployed.
/@nitinkhanna