1. 11

    Other extensions that recently got ported to WebExtensions which may be of interest to power users are:

    1. 24

      Bring back IRC I say

      No need to bring it back, it’s always been there. The problem is convincing everyone else to use it.

      1. 33

        IRC has a fair share of problems which are often circumvented by layering additional services like bouncers on top of it. I like it for its ubiquity, but let’s not pretend it doesn’t show age everywhere.

        1. 19

          I think matrix could very well be the successor to IRC. Open, federated, secure, multi-device sync and good support for bridges to other protocols.

          1. 13

            I can’t bring myself to like a communications protocol that’s based on HTTP+JSON, with the reference client written as an Electron app. It just all feels so… inefficient :(

            1. 4

              The very core of matrix is just the graph behind it all. JSON is just one representation of the information and HTTP is just one transport. Those are the only reference implementations right now, but others are possible, if I’ve understood correctly. But someone more knowledgeable should probably weigh in.

              1. 2

                Those are the only reference implementations right now

                The problem with reference implementations is that, by inertia, they end up being the only implementation.

                1. 1

                  Would you rather there wasn’t an implementation? But, in this case, there are several other implementations. There’s the next generation reference home server dendrite (in golang instead of python like synapse) and ruma (in rust). And there are lots of clients. I think only riot supports e2e crypto, but I hope others will start supporting it as it stabilises.

              2. 4

                To be fair, Riot can run perfectly happy standalone. In fact, I have it running right now on my OpenBSD box. Also, there are many other clients!

                1. 5

                  HTTP+JSON isn’t all that inefficient, just a bit of extra headers, whatever.

                  Matrix is actually fundamentally inefficient in a different way — it’s not ephemeral message passing like IRC or XMPP, it’s a replicated database — and it’s worth it.

                2. 6

                  I stopped using IRC and my bouncer 2 weeks ago for Matrix/Riot on my own server with my own IRC bridges and couldn’t be more pleased. Works incredibly well.

                  edit: was an irssi+irssi-proxy user for over 15 years. Tried every other bouncer. Hated them all. Had a perl script to send my phone a pushover notification for mentions. It worked, but it sucked trying to open up IRC app and find the conversation with no scrollback and respond.

                  Now I have: consistent chat client on every device, always have scrollback, all my logs are stored in Postgres, logs are searchable in every client and the search is handled server-side, and I can do E2E encryption with my friends on Matrix. I will never experience Slack bloat because the federation means I only need one server connection and account.

                  1. 4

                    The Riot web app can also serve as a nice IRC client (+bouncer, email notification, etc) if you only need the networks they bridge to.

                    1. 3

                      I haven’t been impressed with the quality of tooling or clients yet. Their Debian package documentation is incorrect and commands tell you to… run the same command you just ran. I haven’t seen a client I’ve been terribly impressed by either; Riot is your typical Electron fare.

                      1. 3

                        Riot is your typical Electron fare

                        The electron wrapper is completely optional, why do so many people say such things, that’s unfair :( I just use it as a pinned tab in Firefox.

                        1. 3

                          Even without the performance concerns of Electron or running in the browser, there’s still the fact these overgrown web apps feel alien in UX on every platform.

                          1. 2

                            I’ve found it to be very unperformant and laggy.

                        2. 1

                          Didn’t know about this. Thanks for the tip.

                        3. 10

                          The IRCv3 working group is attempting to standardise a lot of interesting extensions to the old IRC protocol in a backwards-compatible manner. Amongst other things, they seem to be working on history, standardised registration/authentication, and metadata such as user avatars.

                          1. [Comment removed by author]

                            1. 1

                              It’s really too bad IRC v3 is moving along slowly

                              It is, isn’t it? I am watching their repo on GitHub and get excited every time I get a notification, hoping that it’s about something major like a good history extension. If I had more time I would love to contribute. Wish they had a Patreon account, or something similar.

                            2. 2

                              One aspect of Slack I’d be interested to hear any progress on is the fact that it combines chat and fileshare for groups.

                            3. 1

                              Is Twitch still running this way?

                            4. 5

                              Maybe if it was written in JavaScript, used a million npm packages, invented some new Json/Jose derived protocol,.. then you might have a hope.

                              In all seriousness, I ask myself that question all along. At work we use lync and skype for business and those still feel like a step backwards compared to old Skype, man, icq, and irc. In fact we had logging turned on for a while but the fat xml logs are up our entire email box so it was turned off company wide.

                              1. 5

                                Additionally, Slack supports IRC. I just use tmux + issi to connect to Slack and other IRC networks.

                                1. 6

                                  Slack’s gateway is highly lossy though.

                                  1. 2

                                    What do you mean? I haven’t had a single issue.

                                    1. 12

                                      You lose formatting, inline replies (so you will see out of context messages), that kind of thing.

                                      1. 1

                                        Ah, gotcha. Thanks for the clarification.

                                2. 4

                                  I’m confident that if a company made an open-source IRC client with the bells and whistles of Slack’s UI, and sold a managed IRC server that was not marketed as IRC, they could eat Slack’s lunch. Instant messaging is a commodity and it makes no sense for proprietary software to dominate the field.

                                  1. 14

                                    IRCcloud comes pretty close to that.

                                    1. 3

                                      IRCcloud has a couple of interesting issues when using it in a business setup. For example, for simplicities sake, they load twitters, facebooks and stripes JS libraries into their webapp, giving third parties access to that data. We talked to them about this and they said they were looking into it, but never ended up doing something.

                                      It’s nice otherwise, but I prefer to only use it as a bouncer. Finally, it costs ~5$, so it’s not a feasible chat for many people outside of companies.

                                    2. 6

                                      It’s been done (minus the open source). Used to be called Convore, then changed names to Grove: https://grove.io/

                                      In fact, they conceded defeat to Slack: https://grove.io/blog/closing-shop

                                      1. 3

                                        Grove is better than mIRC, but it’s no Slack. Slack is winning because of UX and polish, not for any technical reason. A competitor would need a native client, with Windows or OS X integration instead of Electron, if you ask me.

                                        1. 5

                                          Those are really hard to iterate on without a lot of people. You’d have a hard time keeping up with Slack’s fire and motion around you.

                                          Possible though. Particularly if you used their IRC gateway to counter their network effect advantage (until they close it).

                                          1. 2

                                            You just want a native slack client?

                                            1. 2

                                              Yes, with an interoperable service provider as well.

                                        2. 6

                                          I think Jabber would make more sense as a modern communication platform than IRC. There’s not much that IRC provides that Jabber conference rooms don’t, but Jabber provides a lot more extensibility than IRC (especially without add-on services like Chanserv, Nickserv, etc.). In which case there are already commercial packages like Cisco Jabber and Openfire that are quite popular.

                                          1. 1

                                            I liked PSYC back when I was comparing them directly since Jabber seemed too complicated:

                                            http://about.psyc.eu/Jabber

                                            http://about.psyc.eu/PSYC

                                            Whatever we use needs to be really simple and efficient at the core. Then, layers or plug-ins for more complex stuff from there. Preferably, super-easy for library users to add or remove. What’s closest any of you know to that which has a decent chance of being converted into a Slack competitor? Other than IRC.

                                            1. 2

                                              There aren’t many that are federated like IRC. I can only think of Jabber/XMPP and Matrix. But if you look at slack, which doesn’t seem to be federated, you have lots of options, like mattermost, rocketchat, hipchat, …

                                          2. 5

                                            You can’t offer Slack’s UI on top of the standard IRC protocol (it lacks links, images, replies, authentication, history…). Proposals to extend the IRC protocol have not been welcomed by the IRC userbase or by established networks. You could tunnel a custom protocol over IRC with magic strings etc. but this would be inherently clunky and the user experience from any other client would be very similar to using Slack’s IRC gateway. You could publish your custom protocol but what would you gain from that? What’s the value proposition where this idea improves over what Slack offers?

                                            1. 2

                                              Extend IRC all you want as long as the extensions are public. You develop the client and sell the server; established networks don’t matter.

                                              1. 3

                                                Why would this “eat Slack’s lunch”? Theoretically an open protocol would make it easier for others to integrate with you, but Slack attracted plenty of integrations (which now act as a competitive advantage precisely because their protocol isn’t open). Other than that, what’s the advantage of making the protocol public?

                                                1. 1

                                                  Well, you’re saying “other than the advantage, what is the advantage?” Another advantage is that it could be cheaper.

                                                  1. 1

                                                    Well I explained that that particular issue doesn’t seem to have been a disadvantage for slack, quite the opposite.

                                                    Building a protocol as an extension of IRC is inherently going to be more expensive than building it without regard to compatibility with IRC, not cheaper.

                                                    1. 1

                                                      I don’t believe that, but I haven’t quantified it, so we’ll need to agree to disagree. Slack extensions are not interoperable. IRC bots have been written for decades.

                                                      1. 1

                                                        Slack extensions are not interoperable. IRC bots have been written for decades.

                                                        All true. And yet for so many services one might use when developing (e.g. CI), it’s so much easier to find a good Slack integration than a good IRC integration.

                                              2. 2

                                                Proposals to extend the IRC protocol have not been welcomed by the IRC userbase or by established networks

                                                Not sure whether you’re talking about some specific extensions, but from what I can see there are multiple IRCv3 extensions that are implemented by common servers.

                                          1. 1

                                            Great concept! Wish you could do more than just walk around though. Some ideas:

                                            • listen to play the audio clips for pages that have them;
                                            • read the other parts of the article, with a text-based way of navigating the TOC
                                            • walk through a stargate and end up in the parallel universe of e.g. French Wikipedia, for articles that link to their French equivalent :)
                                            1. 2
                                              • Export the sequence of lat/lng from your journey, and draw them on a map.
                                            1. 9

                                              The two big things for me are:

                                              1. the expressiveness of the language, which allows me to translate my ideas into code almost directly
                                              2. the powerful tooling, which keeps me from having to deal with boring tasks such as dependency management, so I can spend my time more productively.

                                              I do think emphasizing those two aspects more heavily would make for a better pitch.