Re: [kde-community] possible foss alternative to telegram/slack

Il giorno Tue, 17 May 2016 20:18:37 +0200 Thomas Pfeiffer ha scritto: > Good point! I think we should use it internally extensively before > switching any public communication over to it. More food for thought: another alternative may be Matrix[1] a FOSS, federated

Re: [kde-community] KDE Mission - let's do this!

On Monday 16 May 2016 23:37:17 Thomas Pfeiffer wrote: > On Montag, 16. Mai 2016 22:59:59 CEST you wrote: > > Hi Thomas, > > > > On Tuesday 10 May 2016 22:48:01 Alexander Neundorf wrote: > > > On Tuesday, May 10, 2016 17:18:39 Thomas Pfeiffer wrote: > > ... > > > > > > Both positions are

Re: [kde-community] possible foss alternative to telegram/slack

2016-05-17 5:55 GMT-03:00 Marco Martin : > Hi all, > Right now many groups are using Telegram as their primary communication medium > due to some limitations in IRC (mainly due to the ease of pasting images > inline the channel and the lack of fancy mobile clients for IRC),

Re: [kde-community] possible foss alternative to telegram/slack

I'm interested too, if for no other reason than self-hosting an instance means we aren't tied to the fate of a 3rd-party. Several people who were not on board with issues on the Telegram openness would probably be willing to use this as well. One thing I'd like to mention is that we should firmly

[kde-community] possible foss alternative to telegram/slack

Hi all, Right now many groups are using Telegram as their primary communication medium due to some limitations in IRC (mainly due to the ease of pasting images inline the channel and the lack of fancy mobile clients for IRC), there may be other valid reasons i'm not aware of today i randomly