Language Selection

English French German Italian Portuguese Spanish

Rejecting Proprietary Slack

Filed under
  • Say No to Slack, Say Yes to Matrix

    Of all proprietary chatting systems, Slack has always seemed one of the worst to me. Not only it’s a closed proprietary system with no sane clients, open source or not, but it not just one walled garden, as Facebook or WhatsApp are, but a constellation of walled gardens, isolated from each other. To be able to participate in multiple Slack communities, the user has to create multiple accounts and keep multiple chat windows open all the time. Federation? Self-hosting? Owning your data? All of those are not a thing in Slack. Until recently, it was possible to at least keep the logs of all conversations locally by connecting to the chat using IRC or XMPP if the gateway was enabled.

    Now, with Slack shutting down gateways not only you cannot keep the logs on your computer, you also cannot use a client of your choice to connect to Slack. They also began changing the bots API which was likely the reason the Matrix-to-Slack gateway didn’t work properly at times. The issue has since resolved itself, but Slack doesn’t give any guarantees the gateway will continue working, and obviously they aren’t really interested in keeping it working.

  • On the demise of Slack's IRC / XMPP gateways

    I have grudgingly joined three Slack workspaces , due to me being part of proejects that use it as a communications center for their participants. Why grudgingly? Because there is very little that it adds to well-established communications standards that we have had for long years decades.

    On this topic, I must refer you to the talk and article presented by Megan Squire, one of the clear highlights of my participation last year at the 13th International Conference on Open Source Systems (OSS2017): «Considering the Use of Walled Gardens for FLOSS Project Communication». Please do have a good read of this article.

More on this from DD

  • Biboumi - A XMPP - IRC Gateway

    IRC is a communication mode (technically a communication protocol) used by many Free Software projects for communication and collaboration. It is serving these projects well even 30 years after its inception. Though I'm pretty much okay with IRC I had a problem of not able to use IRC from the mobile phones. Main problem is the inconsistent network connection, where IRC needs always to be connected. This is where I came across Biboumi.

    Biboumi by itself does not have anything to do with mobile phones, its just a gateway which will allow you to connect with IRC channel as if it is a XMPP MUC room from any XMPP client. Benefit of this is it allows to enjoy some of XMPP feature in your IRC channel (not all but those which can be mapped).

    I run Biboumi with my ejabbered instance and there by now I can connect to some of the Debian IRC channel directly from my phone using Conversations XMPP client for Android.

    Biboumi is packaged for Debian, though I'm co-maintainer of the package most hardwork is done by Jonas Smedegaard in keeping the package in shape. It is also available for stretch-backports (though slightly outdated as its not packaged by us for backports).

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Linux Foundation: Microsoft Openwashing,, OCP, Kernel Commits Statistics

  • More Tips for Managing a Fast-Growing Open Source Project [Ed: Microsoft has infiltrated the Linux Foundation so deeply and severely that the Foundation now regularly issues openwashing pieces for the company that attacks Linux]
  • improves Kubernetes networking in sixth software release, one of Linux Foundation’s open source projects, has introduced its 18.01 software release with a focus on improving Kubernetes Networking, Istio and cloud native NFV.
  • Bolsters Kubernetes, NFV, and Istio Support With Latest Release
    The Fast Data Project ( released its sixth update since its inception within the Linux Foundation two years ago. While the update list is extensive, most are focused on Kubernetes networking, cloud native network functions virtualization (NFV), and Istio.
  • Linux Foundation, OCP collaborate on open sourcing hardware and software
    The virtualization of network functions has resulted in a disaggregation of hardware and software, increasing interest in open source projects for both layers in return. To feed this interest, the Linux Foundation and Open Compute Project (OCP) recently announced a joint initiative to advance the development of software and hardware-based open source networking. Both organizations have something to offer the other through the collaboration. The Linux Foundation’s OPNFV project integrates OCP as well as other open source software projects into relevant network functions virtualization (NFV) reference architectures. At the same time, OCP offers an open source option for the hardware layer.
  • Kernel Commits with "Fixes" tag
    Over the past 5 years there has been a steady increase in the number of kernel bug fix commits that use the "Fixes" tag.  Kernel developers use this annotation on a commit to reference an older commit that originally introduced the bug, which is obviously very useful for bug tracking purposes. What is interesting is that there has been a steady take-up of developers using this annotation:

today's howtos

Positive Red Hat Results Expected Next Week

Fedora: Fedora 28 Beta Delay, Mindshare Monthly Report and More

  • Fedora 28 release dates and schedule
    With the release of Fedora 27, the Fedora 28 release schedule is falling into place. As of now, the current Fedora 28 release schedule is as follows.
  • Fedora 28 Beta Has Been Delayed
    It's time for the Fedora 28 release dance and to place your bets if F28 will be released on time or is another Fedora release challenged by release delays. Fedora 28 Beta had been due for release next week but has now been set by its first delay. Fortunately, a buffer was already built into the release schedule so for now is not impacting the final release of Fedora 28 due out in May.
  • Fedora 28 Beta status is NO-GO
    Release status of the Fedora 28 Beta is NO-GO. Due to missing RC for the F28 Beta release and presence of blocker bugs, the decision is “No Go”. The Beta release slips for one week to “Target #1” date (April 3rd). We are not going to slip the Final GA yet.
  • Mindshare Monthly Report – FAD and First Actions
  • Digitizing VHS with Fedora
    I have a dozen or so movies on VHS that we still watch. To be honest, I'm not that concerned about the commercial movies; those are easy enough to replace. But what about our home movies? My high school cross country team videos and my wife's marching band videos, among others—you won't find those on Netflix anytime soon. So I decided it was time to get serious about something I'd been meaning to do for a long time: Digitize my VHS tapes. In this article, I'll describe how I set up my Fedora desktop to convert my VHS tapes into 1s and 0s. Previously, Don Watkins described a different setup for VHS conversion.
  • Fedora 27 : The LibreOffice the 6.0.2 and versions.