A MoinMoin bookmark allows you to set a stable marker to identify when you last paid attention to the changes made on the Wiki. When you decide that you've caught up as much as you want to be, you reset the bookmark to the current date/time. This way, the Changes list is much shorter, and easier to deal with.

-- TWikiGuest - 14 Mar 2001

Changing this item to a Brainstorming topic. Sounds interesting, kind of a preference setting used to judge what's new and not. I like the concept. UpdateInfoPlugin is about using markers on new links. This fits in well.

-- GrantBow - 16 Jan 2003

This sounds like an excellent idea! I can see some usefulness to being able to do that on a per web basis as well as a global (TWiki site) basis, so if someone implements this, I hope they will consider providing both options.

Without knowing how MoinMoin does it, maybe the bookmarks could / should be stored as data or metadata on each user's home page, perhaps as a table with a row for each web?

-- RandyKramer - 16 Jan 2003

If you were to set the "bookmark" timestamp on a sitewide basis, this could probably be implemented with just a "newer-than" search option and a Set LASTVISIT setting in the user's topic. Per-Web timestamps would be a bit more complex to implement.

-- WalterMundt - 16 Jan 2003

Can SEARCH find pages modified after certain date? If not, adding date functionality to SEARCH and some LASTVISIT plugin just to record last time I clicked on it might greatly simplify this kind of reporting, IMHO.

New SEARCH by date feature might be useful in other ways: Ie. find pages with NEW icon which did not changed in last 3 months (and aren't new any more).

-- PeterMasiar - 17 Jan 2003

Walter, you're right, but I take "bit" literally -- to do this on a per web basis we'd need a LASTVISIT variable per web, which could still be stored on the user's home page.

-- RandyKramer - 18 Jan 2003

Well, that'd be kind of hackish because you'd have to same them something different each time, like LASTVISIT_<webname>. This is because (AFAIK) there's no way to specify in a set statement on your homepage that you only want the setting to apply to a specific Web. A better solution would be to allow you to do that somehow. Then you could have things like:

• Set Codev.SKIN = foo
• Set Main.SKIN = bar

and have each web in a different skin. Then the LASTVISIT variable could just use that if you wanted, or be site-wideif you didn't.

-- WalterMundt - 19 Jan 2003

Walter, Thanks, you're absolutely right. (Well, I knew what I meant, but I didn't say it very well -- yes, you'd need some way to distinguish the LASTVISIT variable for each web.)

Ignore: I don't know if it's more "Perlesque" to use something like a hash (?) and naming convention like LASTVISIT.Codev, LASTVISIT.Support (or LASTVISIT(Codev)) -- but I guess I'm confusing something -- that might be the way you address things in the program, but that's not how you'd store them on the user's home page. And, I'm just screwing around -- the person that implements this will find a good way to do it.

-- RandyKramer - 19 Jan 2003