Where answers come from

Some pages can ask a language model questions. Set this up once; your choice is remembered in this browser for the whole site.

Model source
Use another source instead

Smallest-to-largest weight downloads. Qwen3.5 0.8B is our starting choice for page Q&A. GPU estimates are not total RAM: leave room for the browser, context and temporary buffers. Hardware changes speed and capacity; answers still need checking.

Session-only loading avoids saving model weights, uses extra RAM and downloads again after unloading. Turn it off to save downloads. Delete-data-on-exit or private browsing may impose a much smaller storage limit than the displayed estimate.

You sign in on OpenRouter; it gives this page a key for your account.

A free account does not make every model free. Choose a model with a listed :free variant; merely adding that suffix does not create one. Check free-model availability and pricing.

Chat

AI assistant, not Shawn Hartsock. It does not speak for him.

Inspect the page excerpt

Up to 4,800 characters, not the whole site. Recent conversation turns are retained within the model’s context limit.

Ask about this page, or just say hello.

Ready when you are.

Not saved or uploaded automatically. Closing keeps this conversation in this tab; changing pages starts a new one. Model replies can be wrong.

Audit Logging Plugin version 0.3: who did what when

Originally published .

When I posted my Audit Logging plug-in I had no idea how to get at the user name of the person using the session. I posted a question on the Grails Dev forum. And the answer supplied by pftravis lead me this…


    static String actorKey = 'userPrincipal.name'

    static String sessionAttribute = null

    def getActor() {

        def attr = org.springframework.web.context.request.RequestContextHolder.getRequestAttributes()

        def actor = null

        if(sessionAttribute) {

            actor = attr?.session?.getAttribute(sessionAttribute)

        }

        else {

            actor = resolve(attr,actorKey)

        }

        return actor

    }

… if there is no configuration the default will read the ‘userPrincipal.name’ from the context. In my set up of the listener I read in the Config.groovy from the grails project and if there is a configuration like this…


auditLog {

   actorKey = "session.user.name"

}

…then I’ll use a clever little groovy trick to resolve the session, user, and name out of the attributes. If instead the configuration looks like…


auditLog {

   actorKey = "userPrincipal.id"

}

… the same trick will read the id of the authenticated user. But, if you are using CAS then you can do this…


auditLog {

  username = "${edu.yale.its.tp.cas.client.filter.CASFilter.CAS_FILTER_USER}"

}

… and you get the CAS authenticated user name.

So long story short all you have to know is if your security system uses userPrincipal and if it does whether “userPrincipal.name” or “userPrincipal.id” is right. If you have a home brew security system all you have to know is what part of the authenticated user you want to identify the user by… and specify “session.user.name” or “session.login” depending on how your security system works. And for systems like CAS you can use an attribute key of any kind.

Nice and generic. Check out the latest Grails Audit Logging Plugin. As always any feedback or criticism will be welcome… and my goal in all of this is to contribute and learn.

Explore the map · Browse by topic and date