I have read about the changes to the cookie timeouts in .net 2.0 and that this has caused the change in how long DNN will remember that you are logged in.

I have also heard that there is a workaround.  Specifically:

"Somewhere around line 107 in web.config is:
forms name=".DOTNETNUKE" protection="All" timeout="60" cookieless="UseCookies"
I have mine set to 10080 which is one week."

What I would like to know is why this hasn't been implemented on almost any sites including dotnetnuke.com.
Forcing people to login everytime they turn around is incredibly annoying.
Are there issues with this solution? 

If not can we please give everyone at least a few days.  And can we please increase the default for on the standard install.

Then I guess my question is, is there another solution?

Is this being looked into.  It is a royal pain.

Especially when you look at things community wide.

Many of us frequent a number of DNN sites.  Being required to reenter passwords over and over and over again.

There is also a greater risk if a hacker hijacks your cookie. So I guess the short answer is that it is not really safe for a website to "remember" you, if the cookie is not protected.  Although I guess if a hacker was going to steal your cookie then they would easily be able to look at the expiration date to make sure they didn't waste their efforts.

One other thing that you may not know is that the timeout setting is a sliding expiration.  If it is set at one day, and you visit every day then it will not expire. 
If it is set at one week and you come back 6 days later it'll be reset to expire in another 7 days.