[sup-talk] on sup

[William Morgan]

Excerpts from Magnus Therning's message of Wed Sep 05 00:48:03 -0700 2007:
> After thinking a little about this I think it's the receiving of
> encrypted/signed emails that's cumbersome to deal with at the moment.
> If I'm not completely daft it seems like sending is infinitely
> flexible through the hooks system.

The hooks would be an option, but I'm actually planning to stick it in
the code directly. What I'm thinking is that decoding will just hide the
attachment and display a little message at the top of the message saying
"signature verified", or a big nasty message if not. For encoding, I
would like to have some nice way of choosing sign/sign&encrypt/nothing
on a per-message basis, but I'm not sure what the best UI for that is. I
was originally thinking something like the reply-mode options, but then
how would the two interact? I could also make each option correspond to
various keyboard combinations, but that seems a little obtuse. I don't
really like the mutt-style prompt at the bottom on the screen (the
"minibuffer", as I style it).

> One more question, is there anything "site specific" in the state data
> sup maintains?  Would I run into problem if I use rsync/unison to
> synchronise sup's state to several machines?

Sup uses sources.yaml to map between integer source ids (which are
stored in the index) and the source URIs, which for mbox files are
absolute pathnames. So if you're using local mbox files and the paths
differ between machines, you'll have to tweak sources.yaml to reflect
that. If the source URIs are the same, then as long as sources.yaml is
synchronized along with the ferret/ directory, you should be fine.

Beyond that, Sup uses Ferret to store all state, so if the different
sites have different architecture, it's going to be up to Ferret as to
whether the indexes are portable. I'm not sure of the answer on this
one.

-- 
William <wmorgan-sup at masanjin.net>