Release v1.6.0 · voidauth/voidauth
github.com
What's Changed Features 🚀 Reduce Image Size and Memory Usage by @notquitenothing Better support for Public OIDC Clients by @notquitenothing Allow Native OIDC Clients Non-Reversed-Domain Schemes by...

In honor of the great RAM price gouging shortage of 2025-2026, this release cuts the memory usage of VoidAuth in half! I noticed that my own instance was pretty thicc at nearly 300MB of memory usage after stabilizing and not doing anything, so decided to do some trimming and optimization.

(Un)Scientific Results:

  • RAM Usage: 280MB -> 150MB
  • Image Size: 660MB -> 360MB

This release also brings better support for public OIDC Clients, but more testing is likely needed to catch edge cases so if something isn’t working let me know. Thank you everyone for your engagement and support, I am feeling the love as this project crosses past 1000 stars 🥳. If you are interested, please try it out!

Here are the Release Notes:

What’s Changed

Features 🚀

  • Reduce Image Size and Memory Usage
  • Better support for Public OIDC Clients
  • Allow Native OIDC Clients Non-Reversed-Domain Schemes

Fixes 🔧

  • Fixed Issue That Could Cause Stuck Loading Spinner While Prompting to Create Passkey

Docs 📖

  • Docs: add Memos SSO configuration instructions in OIDC guides and fix a typo by @FrostWalk

And a bonus meme:

alien overlord meme with RAM looking down over CPU and RENT

  • irmadlad@lemmy.worldEnglish
    2·
    1 day ago

    So in your case you could have a blanket rule covering your entire domain and gradually add more specific paths as needed.

    Ok well that’s helpful. Thanks for the input. I have seen a lot of people recommend VoidAuth so there has to be something to it. LOL