<div dir="ltr"><div>Hi Dev<br><br>I understand th concerns are no hosting , easy for Public participation & chat history preservation <br><br></div><div>The option I like to suggest testing is <a href="http://matrix.org">matrix.org</a> and its clients like Riot<br><br><div class="et_pb_row">
<div class="et_pb_column et_pb_column_4_4">
<div class="et_pb_text et_pb_bg_layout_light et_pb_text_align_center gmail-banner">
Matrix is an open standard for decentralised communication, providing
simple HTTP APIs and open source reference implementations for securely
distributing and persisting JSON over an open federation of servers.
<p>You can use Matrix for…</p><ul><li>Decentralised Group Chat - Fully distributed persistent chatrooms with no single points of control or failure<br></li></ul><ul><li>WebRTC SignallingWeb -friendly signalling transport for interoperable VoIP and video calling<br></li></ul><ul><li> Internet of Things - Exchanging and persisting data between devices and services<br></li></ul><p>and anywhere else you need a common data fabric to link together fragmented silos of communication.<br></p><p>In our Organization , we use IRC public rooms in freenode , but primarily connected using Riot clients for web , Android and Ios.<br></p><p><a href="http://matrix.org/docs/projects/try-matrix-now.html">http://matrix.org/docs/projects/try-matrix-now.html</a></p><p>This opens up participation room in a big way, and bring convenience on top of IRC <br></p><p></p><p>any simple logging bot can log communication history. as in old days. <br></p><p>There is no server involved . <br></p><p>Anivar <br></p><p><a href="https://anivar.net">https://anivar.net</a> </p><p><a href="https://twitter.com/anivar">https://twitter.com/anivar</a><br></p></div></div></div></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div><div><div>Anivar Aravind<br></div>Executive Director<br></div>Indic Project<br></div><a href="http://indicproject.org" target="_blank">http://indicproject.org</a><br></div><a href="http://twitter.com/indicproject" target="_blank">http://twitter.com/indicproject</a><br></div></div></div>
<br><div class="gmail_quote">On Tue, Mar 14, 2017 at 6:16 AM, Raitme Citterio <span dir="ltr"><<a href="mailto:rcitterio@gmail.com" target="_blank">rcitterio@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div dir="auto">Greetings Dev</div><div dir="auto"><br></div><div dir="auto">I fully share the pros and cons of employing an opensource application because of the potential risks involved.</div><div dir="auto"><br></div><div dir="auto">However the mattermost option seems basic and limited compared to slack.</div><div dir="auto"><br></div><div dir="auto">By the way, I would like to participate if possible in the slack group.</div><div dir="auto"><br></div><div dir="auto">A suggestion as a test could be the next test to broadcast the session on Wednesday via streaming periscope using the following tool</div><div dir="auto"><br></div><div dir="auto"><a href="https://restream.io" target="_blank">https://restream.io</a></div><div dir="auto"><br></div><div dir="auto">In combination with the following broadcast tool (OBS <a href="https://obsproject.com" target="_blank">https://obsproject.com</a>)</div><div dir="auto"><br></div><div dir="auto">I think it would be an alternative to increase participation and open more work sessions within ICANN to the community.</div><div dir="auto"><br></div><div dir="auto">If you need additional help for this experiment you can count on me.</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">El 13 mar. 2017 4:02 PM, "Dev Anand Teelucksingh" <<a href="mailto:devtee@gmail.com" target="_blank">devtee@gmail.com</a>> escribió:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Its very unlikely that ICANN will offer support (server resources,<br>
tech support) in the short term to deploy a self hosted solution like<br>
mattermost or Rocket.chat for ICANN At-Large Community. ICANN may be<br>
considering group chat solutions but given Slack export capabilities,<br>
it can be quite likely that conversations in Slack can be exported and<br>
imported into another group chat tool<br>
<br>
My copy and paste missed the last part of the text ...<br>
<br>
Dev Anand<br>
<br>
<br>
On Mon, Mar 13, 2017 at 12:53 PM, Dev Anand Teelucksingh<br>
<<a href="mailto:devtee@gmail.com" target="_blank">devtee@gmail.com</a>> wrote:<br>
> Dear All,<br>
><br>
> I've been thinking (and tinkering) about group chat.<br>
><br>
> I'm suggesting that the At-Large Community use the free tier Slack<br>
> version that we have at <a href="https://icannatlarge.slack.com/" rel="noreferrer" target="_blank">https://icannatlarge.slack.com<wbr>/</a><br>
><br>
> Key reasons why:<br>
><br>
> - Its very unlikely that ICANN will offer support (server resources,<br>
> tech support) in the short term to deploy a self hosted solution like<br>
> mattermost or Rocket.chat for ICANN At-Large Community. ICANN may be<br>
> considering group chat solutions but given Slack export capabilities,<br>
> it can be quite likely that<br>
> - The challenge of a volunteer to deploy an open source solution for a<br>
> large number of users using their resources without payment and<br>
> support it to configure or fix things is too much and runs the risk of<br>
> a volunteer unable to fulfil such a task after valiantly starting and<br>
> the self hosted version goes down.<br>
> - from an end user perspective, Slack works. It has the key features<br>
> we want in group chat - threaded conversations, mobile apps, ability<br>
> to create public channels, private rooms, and direct messages, search<br>
> across channels.<br>
> - the free tier offers 10 integrations - I've integrated Twitter,<br>
> Skype, a translation tool, and an archive tool bot and was able to do<br>
> this using the browser. Just like any other cloud service.<br>
><br>
> here's a screenshot of the Slack channels<br>
> <a href="https://www.dropbox.com/s/xgka1gpxnhpwv24/ttf-icann58-slack-channels.png" rel="noreferrer" target="_blank">https://www.dropbox.com/s/xgka<wbr>1gpxnhpwv24/ttf-icann58-slack-<wbr>channels.png</a><br>
><br>
> The approach I've done is to create channels for interests and wgs<br>
> that didn't neatly fit the interests - I've used the Key Policy<br>
> issues of the At-Large Community<br>
> <a href="https://www.dropbox.com/s/f1f81kugty0hulh/Policy-Issues-of-Interest-to-ICANN-At-Large.png" rel="noreferrer" target="_blank">https://www.dropbox.com/s/f1f8<wbr>1kugty0hulh/Policy-Issues-of-<wbr>Interest-to-ICANN-At-Large.png</a><br>
> (this screenshot was from the O&E Community Onboarding presentations<br>
> <a href="https://community.icann.org/display/atlarge/At-Large+Community+Onboarding" rel="noreferrer" target="_blank">https://community.icann.org/di<wbr>splay/atlarge/At-Large+Communi<wbr>ty+Onboarding</a>)<br>
><br>
> - Slack content can be exported on a regular basis as a backup and<br>
> also for importing in any future group chat solution that could be<br>
> deployed/supported by ICANN<br>
> - I've also installed and configured this service which creates a<br>
> public archive of the Slack room -<br>
> <a href="http://icannatlarge.slackarchive.io/" rel="noreferrer" target="_blank">http://icannatlarge.slackarchi<wbr>ve.io/</a> so we can make our conversations<br>
> public facing<br>
> We can link to the conversations in a channel, for eg<br>
> <a href="http://icannatlarge.slackarchive.io/technologytaskforce" rel="noreferrer" target="_blank">http://icannatlarge.slackarchi<wbr>ve.io/technologytaskforce</a> or<br>
> <a href="http://icannatlarge.slackarchive.io/idn/page-1" rel="noreferrer" target="_blank">http://icannatlarge.slackarchi<wbr>ve.io/idn/page-1</a> to a specific message.<br>
> And in theory, I think it means that the search limit can be overcome.<br>
><br>
> Thoughts? The TTF session is Wednesday<br>
><br>
> Dev Anand<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> On Fri, Mar 10, 2017 at 2:59 AM, Chris Gift <<a href="mailto:chris.gift@icann.org" target="_blank">chris.gift@icann.org</a>> wrote:<br>
>> Dev<br>
>><br>
>> Thanks for this. It’s great stuff. I would also look at visibility, archiving, and data access – all core to our transparency and accountability mandates.<br>
>><br>
>> Chris Gift<br>
>><br>
>> On 3/9/17, 6:45 AM, "<a href="mailto:ttf-bounces@atlarge-lists.icann.org" target="_blank">ttf-bounces@atlarge-lists.ica<wbr>nn.org</a> on behalf of Dev Anand Teelucksingh" <<a href="mailto:ttf-bounces@atlarge-lists.icann.org" target="_blank">ttf-bounces@atlarge-lists.ica<wbr>nn.org</a> on behalf of <a href="mailto:devtee@gmail.com" target="_blank">devtee@gmail.com</a>> wrote:<br>
>><br>
>> ;-) which is what happens when I try to have too many drafts onscreen.<br>
>><br>
>> As I was saying, I do need feedback on what this group wants regarding<br>
>> group chat applications<br>
>><br>
>> Some of my thoughts<br>
>><br>
>> - we use Skype for At-Large chat<br>
>> However there are disadvantages of using Skype<br>
>> - chat history is not preserved - a lot of At-Large discussions over<br>
>> the years have already been lost as persons upgrade their machines<br>
>> - conversations on various topics happens in one group so as multiple<br>
>> persons chime in at different times, potential conversations/insights<br>
>> on a particular topic/issue are lost in the one stream.<br>
>> - no ability to search messages across all skype groups - one has to<br>
>> remember what skype group a potential message was in to find it<br>
>><br>
>> QUESTION : Any other disadvantages to note?<br>
>><br>
>> - there are a myriad of group chat applications - Slack, Hipchat,<br>
>> Rocket.chat, Mattermost<br>
>><br>
>> - all share common features<br>
>> - creating public rooms or channels for groups and/or topics<br>
>> - creating private groups not visible to persons outside of such groups<br>
>> - mobile apps to get push notifications and to respond to<br>
>> messages via mobile more effectively<br>
>> - ability to search across all channels and rooms<br>
>> - can be administered by staff to create/archive/delete rooms/channels<br>
>> - staff/admins have more control to add/remove/invite persons<br>
>> - allows for extensions/integrations so that different services<br>
>> can be integrated (eg Twitter notifications to a channel, email to a<br>
>> channel)<br>
>><br>
>> QUESTION: Any other core features to note?<br>
>><br>
>> Based on these core features, Group chat offers significant benefits than Skype<br>
>> - potential for At-large community members to be added by Staff and<br>
>> added to channels of their interest<br>
>> - potential to reduce email overload<br>
>> - ability to find messages and conversations when they have time and<br>
>> new found interest to learn/participate more<br>
>><br>
>> QUESTION: Any other core benefits?<br>
>><br>
>> QUESTION - Are there any specific feature that makes a specific group<br>
>> chat stand out in terms of which one should be picked?<br>
>><br>
>> QUESTION - What do we want to recommend for ALAC/ICANN as next steps?<br>
>><br>
>> Looking forward to comments<br>
>><br>
>> Dev Anand<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> On Thu, Mar 9, 2017 at 10:02 AM, Dev Anand Teelucksingh<br>
>> <<a href="mailto:devtee@gmail.com" target="_blank">devtee@gmail.com</a>> wrote:<br>
>> > Dear All,<br>
>> ><br>
>> > Here's the slides for the TTF session at ICANN58<br>
>> > <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_presentation_d_1uAxM-5Fi9hUBV2ZtqsGe3nKk8C0CDkJDDrtUfLV8XjOwE_edit-3Fusp-3Dsharing&d=DwICAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=zS0x8pK8z0FnanGSXbXvoRVfpJzE1Xmo0ZZP9Gl3-rw&m=gFod0ez7zYcG_fvtwhex4-dIzXSyKaKPlrG2TPx7ij8&s=L3HxyXbLbVub6rdDAJkf8TTemqvxJRv8GSSluEytMYE&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.<wbr>com/v2/url?u=https-3A__docs.go<wbr>ogle.com_presentation_d_1uAxM-<wbr>5Fi9hUBV2ZtqsGe3nKk8C0CDkJDDrt<wbr>UfLV8XjOwE_edit-3Fusp-3Dsharin<wbr>g&d=DwICAg&c=FmY1u3PJp6wrcrwll<wbr>3mSVzgfkbPSS6sJms7xcl4I5cM&r=z<wbr>S0x8pK8z0FnanGSXbXvoRVfpJzE1Xm<wbr>o0ZZP9Gl3-rw&m=gFod0ez7zYcG_fv<wbr>twhex4-dIzXSyKaKPlrG2TPx7ij8&<wbr>s=L3HxyXbLbVub6rdDAJkf8TTemqvx<wbr>JRv8GSSluEytMYE&e=</a><br>
>> > (editing link, no Google login required)<br>
>> ><br>
>> > Still have work on Policy tracking and how At-Large should use group<br>
>> > chat applications<br>
>> ><br>
>> > Whilst I put together the policy tracking slides, I do need feedback<br>
>> > on what this group wants<br>
>> > regarding group chat applications<br>
>> ><br>
>> > Some of my thoughts<br>
>> ><br>
>> > - there are a myriad of group chat applications - Slack, Hipchat,<br>
>> > Rocket.chat, Mattermost<br>
>> > - all share common features<br>
>> > - creating public rooms or channels for groups and/or topics<br>
>> > - creating private groups not visible to persons outside of such groups<br>
>> > -<br>
>> ><br>
>> ><br>
>> > - Group chat applications have signf<br>
>> ><br>
>> > Re: Group chat applications,<br>
>> _____________________________<wbr>__________________<br>
>> ttf mailing list<br>
>> <a href="mailto:ttf@atlarge-lists.icann.org" target="_blank">ttf@atlarge-lists.icann.org</a><br>
>> <a href="https://mm.icann.org/mailman/listinfo/ttf" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/ttf</a><br>
>><br>
>><br>
______________________________<wbr>_________________<br>
ttf mailing list<br>
<a href="mailto:ttf@atlarge-lists.icann.org" target="_blank">ttf@atlarge-lists.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ttf" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/ttf</a><br>
</blockquote></div></div>
</div></div><br>______________________________<wbr>_________________<br>
ttf mailing list<br>
<a href="mailto:ttf@atlarge-lists.icann.org">ttf@atlarge-lists.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ttf" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/ttf</a><br>
<br></blockquote></div><br></div>