Felix Palmen :freebsd: :c64:<p>I now decided I'll at least aim for some middle grounds: Rework <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>swad</span></a> so it only needs a (server-side) <a href="https://mastodon.bsd.cafe/tags/session" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>session</span></a> once a user is <a href="https://mastodon.bsd.cafe/tags/authenticated" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>authenticated</span></a>!</p><p>This does have some implications, e.g. passing a redirect argument to the authentication endpoint won't work any more. But experimentation shows a workaround would be to use an "internal redirect" to the login endpoint in <a href="https://mastodon.bsd.cafe/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nginx</span></a>.</p><p>We'll see where I end up. Having sessions only for authenticated users should reduce the need for server-side RAM significantly, so I hope 😉</p>