Dne Čt 16. září 2010 Luiz Romário Santana Rios napsal(a): > I know, handling all of your accounts at once is the whole point of KDE. > But what are identities for, if not for letting many different users use > the same account? I mean, if one user needs only one Identity, what's > their use anyway?
Well, I personally have two identities in Kopete - one for private purposes (chatting with friends) and one for work (corporate Jabber). The former one contains a nickname and some private information, while the latter needs to be formal with only my real name, work position & e-mail and stuff like that. Almost every Kopete user I know has some kind of similar setup. > > And what does "login quickly into an account" mean exactly? As far as I > > know > > KWallet already lets you do exactly that. > > Logging in without registering an account, as a guest, let's say. Now that's some interesting functionality, indeed. However, I don't know whether it's worth the hassle... > > That gets us back from the all-integrated multiprotocol multi-identity > > client > > we have now to seven different icons in the systray and users having to > > carefully pick which one to use, each and every time. > > I think you're getting my idea wrong. I'm not willing to separate different > accounts, but rather, different identities. And that's useful if two people > are using Kopete at the same time, IMO. How do two people end up using Kopete at the same time? A dual-monitor dual- keyboard system? > > And as far as multiple users go, there's no need to reinvent the wheel > > here. > > Every modern OS (including Linux) allows you to have many users on the > > same machine, with full separation (including IM ;-)). > > 1 - Many people use the same computer at the same time. It's not very cool > to switch to another session when a message arrives and, then, switching > back to the previous session. And what about three users at the same time? > 2 - Whole new Linux, X and KDE sessions just for Kopete? Switching a X session takes a second, tops. It's certainly not a lot slower than switching a window. And if you really need to run several Kopete instances for different users within one KDE session, nothing is easier than su user2 -c kopete (or KDEsu, or making a desktop/menu icon to run Kopete as that user). > > > > > > Having more than one identify for one instance has its use, so > > > > > > has using different passwords for each identify (if configured to > > > > > > do so). I think that is what you want, right? > > > > > > > > > > Kind of. Not only that, but, as I already said, a separate > > > > contactlist > > > > > > > and conversation window(s). > > > > > > > > Separated contact history too, although I think separated history > > > > would be automatic by using separated contactlist, I am just not > > > > sure of > > > > that. > > > > > Yes, it would be included. The idea is: separate each identity > > > > environment, > > > > > so they can't interfere each other unless both users want to. > > > > Then just go ahead and run two kopete processes with different config > > dirs > > > > :-) > > I think that that's not very straightforward. oK, true, but it's just a matter of creating a simple wrapper script/desktop file. > Well, take this mail into consideration. If you still don't feel convinced, > maybe I could do some other stuff (or a fork :p). Of course, this all is just my opinion and that doesn't matter much (and I'm not the maintainer). Let's see what other people think, too. 2T
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
