Re: creating new Hub account from the accounts dialog

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0727836071==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig8344EC6AA18E31D13E0C4290"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig8344EC6AA18E31D13E0C4290
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Brian Moseley wrote:
> On Dec 13, 2007 5:26 PM, Heikki Toivonen <[email protected]> wro=
te:
>> I am being serious here. I don't know much about Cosmo or our Hub
>> installation. Why exactly do we need to communicate with Hub users ove=
r
>> email? Legal reasons? Service update announcements?
>=20
> these things, plus validating requests for account removal, notifying
> users if we discover corrupt data that we can't fix, etc. i'm sure
> both Jared and Todd can give you plenty of stories where they've
> needed to communicate with users over email.

All good reasons to communicate, sure.

However, do we ever validate the users' email addresses after the
account creation? If not, why should we validate the first time? Also,
how do you deal with users whose email addresses have become invalid
(changing ISPs, forgetting email password, .,..)? What about users whose
email address is no longer valid, and who also forget their Cosmo passwor=
d?

You will also have to keep in mind that Chandler desktop client does not
show normal emails to the user. Despite all the warnings we may throw
their way, some users may try to set up a Hub account using an email
address they use only in Chandler desktop client. Does all our
communication to Hub users go out with some special headers that informs
Chandler that it should display the email? (Actually, I am not even sure
if there are any such headers that the desktop client honors at the momen=
t.)

--=20
  Heikki Toivonen



--------------enig8344EC6AA18E31D13E0C4290
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHYecNb8x8KoP+JuwRAps4AKCKnVNIdktT++yLXc8bmeKq8o7DFgCguc9E
JF5Vcog14AWtQWM6KKB5jJM=
=kEeH
-----END PGP SIGNATURE-----

--------------enig8344EC6AA18E31D13E0C4290--

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

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design

--===============0727836071==--