From kopete-devel  Tue Sep 29 11:41:39 2009
From: Michael Zanetti <michael_zanetti () gmx ! net>
Date: Tue, 29 Sep 2009 11:41:39 +0000
To: kopete-devel
Subject: Re: [kopete-devel] Enable OTR plugin by default?
Message-Id: <200909291341.42603.michael_zanetti () gmx ! net>
X-MARC-Message: https://marc.info/?l=kopete-devel&m=125422462923938
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============1246925831=="

--===============1246925831==
Content-Type: multipart/signed;
  boundary="nextPart2946740.kACWL6ztQm";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2946740.kACWL6ztQm
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Tuesday 29 September 2009 13:33:11 Markus wrote:
> Am Dienstag, 29. September 2009 11:07:42 schrieb Michael Zanetti:
> > I do not really understand what it's the problem with manually
> > ending/refreshing the otr session. It's 2 clicks once in a while.
>=20
> May I clarify the issue:
> While indeed just 2 clicks away, those two clicks are anything but obviou=
s.
> IIRC the printed message just says: "OTR session closed. You should close
>  it as well."
> I'm hardly a novice user, but after I read that message for the first tim=
e,
>  I actually thought that means close the window.
> Then I tried to figure out where to close the OTR session and it took me a
> while to find it.
>=20

OK. I agree that could take some seconds on the first time.

> IMHO there are two approaches how to make it more easy -- one probably
>  easier to implement way and one IMHO more elegant way:
>=20
> Easy way: A dialog window that pops up after my peer ended the OTR chat a=
nd
>  I close the chat window that asks me to end the OTR session as well.
>  Similarly, a dialog window could pop up to ask for renewing a session.
>=20

Popups... No way! However, the overall idea is quite good...

> Elegant way: Dialog windows are evil, usability-wise. I once saw an insta=
nt
> messenger (forgot which one it was) that displayed buttons inside the
> conversation area. That was pretty neat. Those buttons were in that IM's
>  case only used for file transfer requests, but the idea can be used for
>  OTR as well (behold my horrible ascii art skills):
>=20
>
> _____________________________________________________
>=20
> | Buddy: Hey, I need to go off now. Bye!
> |
> | Me: Alright, cya.
> |
> | "Buddy" ended the encrypted chat session.
> | You should end it as well...._____________
> |........................................ | End Session | <-- This is a
> | button _______________________----------------------- ________________|
> | [ Text input area ]
> |____________________________________________________|
> |____________________________________________| Send |__|
>=20
> I don't know if that's currently even possible without too much trouble,
>  but I think that could be a good approach without compromising security
>  (by doing things automatically that shouldn't be done automatically) and
>  easy discoverable security measures.
>=20
>=20

Very nice proposal! Kopete also uses buttons in the chat-window for file=20
transfers. I think it souldn't be too hard to adapt that for the OTR plugin=
=2E=20
I'll check that out in detail and come to you.

Thanks,
Michael


--nextPart2946740.kACWL6ztQm
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAkrB8nMACgkQXJwWsxE5x7jmUACfbo0CInNkJgXcS5CjhpSEG+pW
mAsAnRFeLgS/0SajijSq14S4ZCkUbqUJ
=LuZk
-----END PGP SIGNATURE-----

--nextPart2946740.kACWL6ztQm--

--===============1246925831==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel

--===============1246925831==--