[UbuntuWomen] Telegram group

[Mikaela Suomalainen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

At the meeting
<http://ubottu.com/meetingology/logs/ubuntu-women-project/2016/ubuntu-women-project.2016-05-10-18.00.moin.txt>
it was decided that Makaela would write here more about Telegram group
plans, but as Makaela is lazy and won't do it and I have no idea what
the plans are, I will try to write something here.

```
=== open session ===
The discussion about "open session" started at 18:32.

  * ''ACTION:'' Makaela to post to Community Team ML on Telegram Group
    Plans
```

What was said:

```
 18:39 <Mikaela> would it make any sense to also start Telegram group
which could be bridged to IRC? Antergos has attracted some new people
to real time support that way and Ubuntu LGBT* also has a group. It has
lesser learning curve than IRC and doesn't need bouncers/terminal
multiplexers or anything else than phone number (not shown to anyone)
and supported platform (FOSS client and I don't know any platform

 18:39 <Mikaela> that didn't have some kind of client).

 18:41 <amani_glugcal> sure

 18:41 <amani_glugcal> I do know lot of lgbt people who are not that
 competent with s/w

 18:42 <amani_glugcal> so how do you plan to go about it?

 18:43 <Mikaela> I run bot for Antergos/Antergos ops/personal channel
 and if needed could run one for UW, but I won't do it without more
 people giving permission

 18:44 <amani_glugcal> yes, that makes sense... the community team
 should look into this

 18:44 <amani_glugcal> post to community team mailing list

 18:44 <amani_glugcal> OK?

 18:45 <Mikaela> I am scared of mailing lists and I cannot until
 tomorrow :(

 18:46 <amani_glugcal> Be brave Mikaela... there are few people on the
 list ...it is not a dark lonely place :)

 18:48 <amani_glugcal> #action Makaela to post to Community Team ML on
 Telegram Group Plans

 18:48 * meetingology Makaela to post to Community Team ML on Telegram
 Group Plans

 18:48 <MarkDude> +1 for Telegram to IRC (/me would like to know some
 details on it later if possible.)

 18:50 <Mikaela> MarkDude: #teleirc is the software making that
 possible and you find it from freenode as one running example
```

I don't know what else to say, but I could add some notes:

* While SailfishOS and Ubuntu Touch have native clients, they are
  missing support for Supergroups (include banning and have common
  history that people see when they join and removed line gets removed
  from everyone. Current status is that the libraries they use are
  getting rewritten if I have understood correctly.
* Founder of the group is above all others and is the only one who can
  promote admins. If their account is removed or they leave the group,
  the group just disappears.
* If you are on bigger public groups on Telegram and have feminine name
  and profile photo, you will get a lot of spam, but you can report it
  to Telegram by using "report spam" immediately and if enough many
  people report that person, they cannot message other people than
  mutual contacts. See also: https://telegram.org/faq_spam
* It would probably be more open version of Slack (by not requiring
  invite email to join group) and having FOSS-side client code even if
  the server-side code is closed. However in case of multiple related
  groups something like Mattermost could be better, but it requires
  hosting. http://www.mattermost.org/
* Telegram is not secure thinking about privacy. Telegram has plain
  text accessible to them and the secret chats are insecure, but
  Telegram doesn't care replying just with their Math PhDs.
  http://security.stackexchange.com/a/49802

- -- 
Mikaela Suomalainen
https://mikaela.info/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Website: https://mikaela.info/
Comment: Fingerprint = 2910 4A46 C561 5BF9 78A0 83F2 0C20 7F07 B2F3 2B67

iQIcBAEBCgAGBQJXMvbjAAoJEAwgfwey8ytnT2YP/2vvNEJaeq/riFEfCP2iyj2b
JNFWtmGLzALJOw4FmBRJXy7cgl/f2EieSc2MOGZBeGFfi/URn3chU+HOE/FHnR73
JazR3sw49xWRRxxpR0vcu65wWOewuVIh7Vzso23OaE/Cuw/5zyjvxikJwtCduwss
VzEwrIF2mSBlU8cy9sOiqNZaGYeWyqA8wlFq5flLosmHfgDCNtjL5xxFj41Nu95y
uV8lTKWKvP1TsZfzpRRPzQKWze3JI4DmHH5ry70WuLRUiPRfi/GHtcWeaietgHMH
6L4gimntE6K1s3Mls0Q1ame6errYtehwBSQi3kPajwfIwM5t8NbMKEs9tXzbfEgP
QrDmzjMNS2L4mXRnocd/c6TL4rBBkLIItvFlMw8NquxMVNHZiFONDRQne8tM4uM+
c4rQOgQpTOB0tLUxA0AKvBjJzeSoVibbFifhJ7Rd2GD6de7QJ9bI2/GQE8OuwwQD
YyBRp6wMb6Z+9fchVc9qMG1/HXFZTqRkoydZ1zZlQGXBzGj3InG8/Q4SN1x+uRqQ
L51q9p1soB51x7jQ2Hnhuf7lNmdvzsgFiG79DGD1J3CqMVNTSjszud5ZhXhjrdG3
jArEf9/wLKlgEElciXHSZv7XM6xifYVJAk9fxjBVXXdd6TSH0nM6j5Ba1lruHJI/
HusEVVI1g9P2fSADa8ap
=dqE/
-----END PGP SIGNATURE-----