Improvements
We recognise that the 2-hour expiration window for code viewer tokens was not ideal for all use cases.
So starting today, users can now opt to change this to any of the following: 2 hours, 8 hours, 24 hours, 3 days, 7 days, 14 days, 30 days.
This should give much greater flexibility to teams that frequently use the code viewer.
You can modify your token expiration in your profile page (link also provided when authorizing the code viewer).
A note on security: the code viewer is completely safe to use. Revocation, expiration and auth-separation is built because we believe in "minimum permission by default". We have seen competitors get hacked and source code potentially exposed, so this feels like a necessary step to limit risk.
We regularly update our changelog in an effort to improve transparency into the development process. If you have any questions or feedback, please don't hesitate to contact us.
If you are a user of OtterWise already, or have been reading our blog, you might already know that we take privacy extremely serious, even when it comes to protecting your code as if it was sensitive personal information, this goes for everything we do, which is why we publish changelogs for even smaller updates, rather than just major releases.
Our weekly digest for OtterWise users also includes our changelog in the bottom (see related changelog), to keep you up-to-date with the latest changes.
