KDE-Soc Telegram group

[Shantanu Tushar]

On Thu, Mar 3, 2016 at 6:37 PM, Nicolás Alvarez <nicolas.alvarez at gmail.com>
wrote:

>
> > El 3 mar 2016, a las 04:45, Alexander Semke <alexander.semke at web.de>
> escribió:
> >
> > Am Samstag, 20. Februar 2016, 02:20:00 schrieb Valorie Zimmerman:
> >> Hi folks, during GCi I noticed how much the Wikitolearn team and
> >> students enjoyed and used their Telegram channels.
> > Just out of pure interest, why Telegram and not Slack? I think Slack is
> also
> > quite popular nowadays...
>
> As far as I know there is nothing open about Slack.
>
> The Telegram protocol is public, every official Telegram client is free
> software, there are no features limited to paying users...
>
> In more practical matters, using Slack would mean KDE has to create a
> "team" (would a free account even work for our needs?), then everyone has
> to get *invited* to the team and create a team-specific account with a
> username and password. Using Telegram means people sign up with their phone
> number, and can join eg. the SoC group by clicking a public link, and don't
> need to sign up separately to use Telegram for non-KDE purposes.
>
> Besides, many KDE people are *already* using Telegram and are *already* in
> KDE groups, so there better be a damn good reason to add or switch to yet
> another communication system.
>
> I use Slack (I'm inconveniently in two teams), and honestly I don't
> understand *why* it's popular. Must be people who were forced to use it at
> work and then outside work want to use what they know...
>

Well, its mostly because there is no setup effort involved. For teams who
don't really care about what happens to the data etc its quite perfect.


>
> --
> Nicolás
> _______________________________________________
> Kde-soc-mentor mailing list
> Kde-soc-mentor at kde.org
> https://mail.kde.org/mailman/listinfo/kde-soc-mentor
>



-- 
Shantanu Tushar    (UTC +0530)
shantanu.io
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-soc/attachments/20160311/c21c5654/attachment.html>