With old-pan, one could save-status by switching groups, so in a crash, the maximum read-tracking loss was since the last group-change.  If 0.1xx crashes, it'll return several groups to the read-status at the beginning of the session.  One has to shut down and restart pan in ordered to be sure group read state is saved.

Given that neither pan itself, nor xorg 7.2 running EXA/Composite rendering, is entirely stable at this point, even tracking text-groups only, and shutting down fairly regularly, I can lose tracking of hundreds of posts over several groups.  I don't consider this acceptable for what's headed for a stable 1.0 release.

At minimum, we need status saved at change-group once again.  Preferably, there should also be either a read-post counter or a timer, that will check-point the status periodically, say every 50 posts or every 10 minutes, maybe whichever comes first if it's not too hard to track both.  That could reduce frustration levels substantially in the case of a crash.