Um, sure if you want to rewrite that part of xoops.
Okay, so have a holding tank datebase table for these session time out anon posts. They would be put into the holding tank DB table tagged with your IP to associate it. Though that brings its problems, though if you login again during the same network connection session your IP shouldn't change. Unless it's like AOL and then you have rotating IP on every network connection. Then it would be impossible to associate the post with the correct account.
The problem is, with not being logged in, the only identifier for a post is the writer's IP address. Cross checking with the last x logged out/session timeout user's IPs. Unfortinatly, I don't know that Xoops stores such data.
One of the problems with what you suggest, is it opens up posting to people who would spoof their IP address, thus end up posting as someone else. Depending on how common this posting situation is, it could cause the use of significant server resources.
It would be like trying to authenticate a letter with only knowing the sending address, not knowing who sent it, and not being able to go to the address to ask who sent it.
