Invitation to join the C++ chat community!
All: Hi there. I would like to personally invite all of the Boost authors, participants on the mailing list, and interested parties to join the most popular C++ Slack workspace, where many lively technical discussions related to C++ and its ecosystem take place. There are channels for everyone, especially the #boost channel, but also channels for WG21 committee discussions such as #future_standard and #wg21. There's even an #sg14 ! You can learn more and request a free invitation here: http://slack.cpp.al This workspace is sponsored by the C++ Alliance, a non-profit organization which promotes and advances the C++ language and provides educational resources. Find out more about the Alliance here: http://cpp.al Regards
On Wed, 17 Oct 2018 07:03:09 -0700
Vinnie Falco via Boost
You can learn more and request a free invitation here:
You should consider bridging those communities to other services using something like https://github.com/42wim/matterbridge Not everyone would care to install slack. I for one already am overwhelmed with irc/discord/gitter/email/matrix. Soon IM and chat apps will eat all RAM. All of it.
On Tue, 23 Oct 2018 at 10:37, Sergey Popov via Boost
On Wed, 17 Oct 2018 07:03:09 -0700 Vinnie Falco via Boost
wrote: You can learn more and request a free invitation here:
Not everyone would care to install slack. I for one already am overwhelmed with irc/discord/gitter/email/matrix. Soon IM and chat apps will eat all RAM. All of it.
I understand this may be of little if no help, but you can use multi-service clients. For instance, I get all you mentioned covered with Rambox. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
On Tue, 23 Oct 2018 10:38:59 +0200
Mateusz Loskot via Boost
I understand this may be of little if no help, but you can use multi-service clients. For instance, I get all you mentioned covered with Rambox.
It looks nifty but still a server-side solution will be more convenient for everyone, including people using a service's native client. Even with multi-protocol client rooms are not merged and conversations between people across services are not possible thus fragmenting communities since some people will stick to single service, or not use a multi-protocol client.
On Tue, 23 Oct 2018 at 12:50, Sergey Popov via Boost
On Tue, 23 Oct 2018 10:38:59 +0200 Mateusz Loskot via Boost
wrote: I understand this may be of little if no help, but you can use multi-service clients. For instance, I get all you mentioned covered with Rambox.
It looks nifty but still a server-side solution will be more convenient for everyone, including people using a service's native client. Even with multi-protocol client rooms are not merged and conversations between people across services are not possible thus fragmenting communities since some people will stick to single service, or not use a multi-protocol client.
I'll quote myself from one discussion on, well, #meta_slack channel on the Slack: """ Matrix idea is great, seems like a perfect match for open source oriented community, but its application is not free from hurdles. Who should run the server? Who will host our data? Who will be responsible and liable? If there is a C++ Foundation then we could employ the body to work things out, even with voluntary efforts to implement it. (edited) It just seems easier organizationally to pay Slack """ Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
On Tue, 23 Oct 2018 12:55:25 +0200
Mateusz Loskot via Boost
participants (3)
-
Mateusz Loskot
-
Sergey Popov
-
Vinnie Falco