<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Dear all</p>
<p>We discussed yesterday the IVOA twitter account that would be
good to have asap so we can start using it during this meeting.</p>
<p>I found an "IVOA interop" twitter account
(<a class="moz-txt-link-freetext" href="https://twitter.com/ivoainterop">https://twitter.com/ivoainterop</a>) which was only used in 2009-2010
for some IVOA interoperability meetings.</p>
<p>So the questions are :</p>
<ul>
<li>do any of you still have the credentials of this IVOA interop
twitter account?</li>
<ul>
<li>if so, should we use this one as the official IVOA twitter
account and transfer it to media group ?</li>
</ul>
<li>or should we create a new one as proposed by the media group ?</li>
<ul>
<li>if so, which nickname should we pick ? <br>
</li>
<ul>
<li>IVOAastro would be my preferred choice, but that's
personal <span class="moz-smiley-s3"><span>;-)</span></span><br>
</li>
</ul>
</ul>
</ul>
<pre class="moz-signature" cols="72">--
Thanks in advance
Cheers
Christophe
-------------------------------------------------------------------
Christophe ARVISET <a class="moz-txt-link-abbreviated" href="mailto:Christophe.Arviset@esa.int">Christophe.Arviset@esa.int</a>
Head of the Data and Engineering Division
Operations Department, Directorate of Science
European Space Astronomy Centre (ESAC)
European Space Agency (ESA)
Camino Bajo del Castillo s/n
Urb. Villafranca del Castillo
28692 Villanueva de la Canada - Madrid Tel: +34 91 813 12 78
SPAIN Mob: +34 655 03 43 03
------------------------------------------------------------------- </pre>
<PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE></body>
</html>